Re:Show HN: See the impact on your cloud costs as you code
by rumno0 on Wednesday August 14, 2024 @10:33AM
(#41246547)
To a certain extent I agree - I've worked on projects where a resource amounts to a rounding error in the overall cloud bill; for many organizations, cost is an important NFR for a project.
Going off the other threads of this post, how much engineers should know or care about billing seems to be open for debate; I think an engineer needs to appreciate that often cost is one of the many trade-offs that need to be accounted for
That said, I've never personally seen any cloud project where there wasn't a business case review that didn't include a review of architectural plans/assumptions and expected cloud service consumption profiling. I think what's different here is that you can help engineers close a feedback loop that is often left open between when a project is planned & scoped and when 1) the landing zone (or data pipelines) is created, and 2) when the app/system is moved from test/QA into production. This could be helpful for the project/product manager, especially, because anything that looks out of whack with the forecast should be escalated promptly.