Enhance your developers, don't replace them
The loudest promise in AI tooling right now is replacement: fewer engineers, same output. It makes a good headline and it’s the wrong goal — and if you lead a team, chasing it is how you end up with worse software and no one left who understands it.
I build AI tooling for a living. I’ve watched what it does to a team. The version that works isn’t the one that removes engineers. It’s the one that makes the engineers you have noticeably better at the thing they were already good at.
Flow is the asset
A developer’s most valuable state is flow — the stretch where the problem is fully loaded into their head and the code is coming out faster than they can second-guess it. It’s also fragile. Most of what we call “productivity tooling” actually shatters it: the context switch to look something up, the ceremony, the tool that needs babysitting more than it helps.
So that’s where I point the tooling. Not at replacing the engineer’s judgement — at removing the things that drag them out of flow. The boilerplate they shouldn’t be hand-writing. The lookup that breaks concentration. The review toil that eats a senior’s afternoon. Clear that away and the human stays in the part that actually needs a human: the decisions.
Enhanced beats replaced
An engineer paired with good tooling out-ships the one you tried to automate away — and, just as importantly, they stay. They keep the context in their head. They keep getting better. You’re compounding a person, not renting an output.
Replacement does the opposite. It hollows out the people who hold the system in their heads and leaves you with software no one can confidently change. That’s not a productivity win. That’s debt with a better marketing department.
What that means for how I lead
It changes the questions I ask. Not “what can we automate away?” but “what is pulling my best people out of flow, and can a tool absorb it?” Not “how do we ship without them?” but “how do we make them faster without taking the wheel out of their hands?”
The engineers can feel the difference immediately — between a tool that’s there to replace them and one that’s there to make their day better. The second kind, they adopt on their own. The first kind, they quietly route around.
My job isn’t to engineer people out of the loop. It’s to make the loop a better place to be — and to let good tooling carry everything that was never the point of the work in the first place.