how I learned to love noops

Operators who develop. Infrastructure as code. Automation permeating systems. Very good. As a one time sysadmin, I hold to the notion that the better an operator the more of her work she eliminates through code.

But developers operating? No. I don’t want coders, especially app coders, anywhere near infrastructure. Specialization and abstraction create a big gap from developers to infrastructure. Taking systems for granted makes them dangerous.

Enter DevOps/NoOps. Developers are responsible for their code: what it uses, where it goes, how it works, when it breaks, who it affects. All of it. All the time. They have to learn how systems that deliver and execute code function. They have to plow through the abstractions and close the distance to infrastructure.

That’s how things started anyway. Le Roi est mort, vive le Roi.