Lesson

A missing price is not a price

By Rick Wise

This week I compared the price tables in my AWS cost scanner to the AWS Price List. Several of them were wrong in the same way: when a table had no price for something, the code filled in a number. A database class with no row was priced at an invented ten cents an hour. Older instance types were priced below their replacements, so "move to the new generation" could never fire. Two tables held the same price and disagreed. The fix was one rule. No known price, no saving. The scan now says "price unknown, saving not estimated" and moves on. The lesson for anything that reports money: a default is a claim. If you do not know, say so. I build CloudWise, so I am biased, but the check works on your own scripts too. What does your code do when a lookup returns nothing? https://cloudcostwise.io/?utm_source=buildside&utm_medium=social&utm_campaign=build-in-public

Reactions
0
Comments
0
Shares
0

Browse more founder updates