There is also so much more to the 'cloud' then just CPU usage. If your focus is devs are using the CPU inefficiently, I see this problem independent from the cl

There is also so much more to the 'cloud' then just CPU usage. If your focus is devs are using the CPU inefficiently, I see this problem independent from the cloud. People with on-prem servers are just as guilty of building beefier servers when code optimizations are possible. The way I see it, there is a kind of equation for this: cost of a hiring someone who can manage servers vs 'cloud markup'. Lets say it would cost 60k to hire this person, that is a lot of inefficiencies you can get away with. What you get 'for free' is your services automatically running on multiple availability zones and really great uptimes with minimum effort. My company would gladly piss away lots of cash than have an hour of downtime. Devs and Business people really have different perspectives on these things. This is why we migrated from Hetzner to Azure, even though Azure is wayyy more expensive. Got bitten once by Hetzer downtime and never came back. The second half of their rant is directed at auto-scaling solutions (k8?). I have my own share of problems with k8, but I guess the problem I have with these kind of abstract rants, is they don't really offer any interesting insight or solutions.