You are pointing the fingers at the wrong people. Cloud providers pushed this idea onto executives via their marketing and conferencing channels.

Not disimilar to how AI naratives are pushed on executives these last two years.

But alongside the marketing blitz they also offer certifications for people who are supposed to execute these projects. Even the most foundational certification exam -- which simply tests your recall on what AWS service is for compute versus networking -- teaches and tests you about "Shared Responsibility Model" that draws the line at what the customer is still responsible for when they use cloud bases IaaS / PaaS / SaaS services.

If businesses are going to cloud but without engaging / listening to competent people who know these basics -- then the blame needs to be somewhat pointed back at those very business leaders I feel.

This is not obscure magical knowledge either that is tightly controlled. Any cloud vendor will freely teach you that. Or even a google search would.

Who is a CEO going to believe? Amazon, Microsoft and the entire IT infra division or that lone SRE who disagrees with them?

I mean, every time cloud comes up on HN we see legions of techies posting strowman arguments about why you should offload everything onto AWS, GCP, Azure, etc.

Aws cto is basically opening every presentation with a everything breaks all the time slide, idk where you get that idea they oversell the cloud resilience

They could offer controlled "failure of service" service where they randomly take stuff offline and you have to pay to get it back if you don't have a backup/recovery strategy.

AWS Fault Injection Service

https://aws.amazon.com/fis/

https://docs.aws.amazon.com/fis/latest/userguide/what-is.htm...

The customer CEO never watched that presentation.

You just have to take a look at the Rube Goldberg-esque abomination that is the AWS web interface for a few minutes to realize that it's not that simple. Granted, most executives won't do that...

Or encounter their CLI and it's lovecraftian combination of positional arguments, named arguments, piping, json documents, etc, distributed largely by random lot, as far as I can tell.

No. If you're the leader you should know what you're leading. It's literally the job.

But the problem is right there: "non-technical" leaders. Never work for one if you can avoid it.

All Tesla employees reading this are fervently agreeing, between their tears.

"We should build vacuum delivery tubes for passengers!"

And for a time, it even seems true as long as the natural disasters that impact various customer offices happen to not impact that one particular data center…

I mean, can't cloud kinda solve all of those if you just use the right things?