[jdoss]

The major problem is the lack of individual domain knowledge on the underlying server techs that run simple to complex workloads. We have abstracted away a lot of that with APIs and YAMLs so developers don't need to know the inner-workings of Linux, Networking, and Storage. This is a huge negative when things go wrong and there are hundreds of tools that we have access to which makes things insanely complicated if not used correctly.

A lot of developers will throw compute resources at problems rather than solving within their code. I get it, that is the faster route in almost every case. They won't get hired or promoted if they don't use the current "new hottness" in our industry. This leads to insane cloud spend and super complex deployment setups.

Businesses and VC have been trying to obsolete the sysadmin role on the team for over 15 years now. They shove this responsibility onto developers and expect them to get paid to effectively two jobs for the price of one. We are simply overloaded with work and not having to deal with getting your code into production is something that some developers don't want to own and want an easy button to press to do this job. This is what is driving the want for a "Platform Experience". All of us in the tech community are paying the price with more work responsibilities and higher expectations from the C suite to deliver features faster.

I am all for making Ops more easier for everyone on the engineering team to consume but, not at the complexity price we are currently paying.