A Developer Is Not Someone Who Writes Code

There's a comforting idea going around: AI won't take the developer's job, it'll just make it broader. Now one engineer carries QA, DevOps, analytics, and a slice of project management. Sounds like a promotion. It's actually an epitaph for four neighboring roles.

"Broader," seen from the developer's side, means "fewer people" seen from the org chart. AI didn't take the developer's job — it took the separate tester, the separate DevOps engineer, the separate analyst. The layoff isn't phrased as "we don't need developers," but as "one is enough where there used to be five."

And the work doesn't just grow — it shifts. The bottleneck moved from production to verification. It used to be hard to make something: write the function, stand up the pipeline. Now it's hard to check it and stitch it together. You type less and decide more — deciding whether what got generated is actually right. And the moment the AI's depth beneath you turns shallow, you're formally accountable for something you can no longer verify yourself. That's not more volume. That's a new class of risk.

A developer was never the person who writes code. It's just that code used to be the only way to prove you were accountable for the result. Now that proof has dropped to zero cost — the machine writes the code. What's left is what was the essence all along: someone has to say "this works, I vouch for it," and understand enough for those words to mean something.

So no, AI didn't make the job broader. It stripped off the disguise. Under "writing code," "being responsible for the system" had been hiding the whole time. The visible part disappeared — the real one was laid bare.