> "Directed to reduce" Cloud spending. That feels like it should be 100%. An engineer should be as aware of their $ costs as they are their CPU load, filesystem I/O, or memory usage. An engineer should know how many instances they scaled to, and when they're going to scale down. In fact, the $ cost should be calculable (to a reasonable indicative amount by napkin math - precision not necessary) according to the facto…
Never once has a dev asked about storage costs, of the differences in storing a file in a filesystem vs a blob in a database,
Never once ask about mem optimization could reduce infrastructure costs
never once