For the past 250 years, new machines have replaced old ways of working to make us more productive. But each new machine is more complicated than the last, requi

For the past 250 years, new machines have replaced old ways of working to make us more productive. But each new machine is more complicated than the last, requiring more technical jobs to address the new complexity in the machine. Kubernetes is just a new machine, and because so many businesses now want to run that machine, they need more maintenance crews that are trained on said machine. In order to have fewer people, we'd need to leverage economies of scale and specialization so that companies don't need these new big complex machines. Even then, the appearance of fewer workers might just be jobs moved offshore where labor is cheaper. It's true that moving away from mutable state is a sea change that is (very) slowly engulfing the industry. But the tide is still very far out. The cloud is a pile of mutable state, leading to the same system instability and maintenance headaches that existed before the cloud, requiring new skills and workers to deal with. Redesigning the cloud to be immutable will take decades of re-engineering by vendors, and even when it's done, we'll still need economies of scale to reduce headcount.