I like maintainers. I’ve spent years reading their mailing lists, filing their bugs and depending on code they wrote at night for nothing, and I run a few small projects myself. So I’m the last person who wants to argue that the human at the centre of an open source project matters less than we say. My claim is narrower than that. It’s about what happens on the days that person isn’t there.

Cloud coding agents start each task on a fresh machine. Before the agent can run a single test, something has to install the right runtime and start the database, and every platform wants those instructions in its own file. Copilot runs a setup workflow; Cursor builds a Dockerfile. A team that uses two or three agents writes the same setup two or three times, and a mistake usually shows up later as an agent session that goes nowhere.

Every few months the same headline resurfaces: DevOps is dead. In 2026, the claim has more surface credibility than before — job boards are brutal, the title is disappearing from org charts, and AI is eating the work that once defined the role. None of that means the function is gone. It means the floor dropped out and the ceiling went up.

The mechanics are straightforward. AI systems built into cloud platforms now handle what junior and mid-level DevOps engineers spent most of their time on — infrastructure provisioning, pipeline configuration, alert triage, rollback decisions. That work isn’t being done by fewer people out of choice. It’s being done by machines out of necessity, because the scale modern systems operate at makes human-in-the-loop intervention a bottleneck. Netflix deployed 4,000 times daily last quarter. Amazon pushes a change every 11.7 seconds across global infrastructure. No headcount solves that. Automation does.