I Stopped Hiring Developers
I stopped hiring developers.
Not because I don't need people who understand software - because the job isn't writing code anymore.
The job is deciding what should exist, watching AI build it, and governing the result. That's a different skill set. That's stewardship.
And the people who get that? They're thriving.
This isn't new for me. I used to say "I want engineers, not developers." Same instinct - systems thinking over syntax. But AI changed the altitude. It handles the systems now too. What's left is the judgment. And that needed a new word.
What Changed
AI writes code now. A lot of it. But here's what AI doesn't do: it doesn't know your domain. It doesn't understand why you made the architectural decision you made last quarter. It doesn't know that the function it just generated violates a constraint your team agreed on six months ago.
AI generates. Humans govern. That's the inversion.
The World Economic Forum says 65% of developers expect their role to be redefined this year. They're right - but "redefined" understates it. The role is being revealed. The judgment, the taste, the pattern recognition that senior engineers always brought? That used to be buried under the typing. Now it's the whole job.
GitHub's own research found that advanced AI users have shifted from "code producers" to what they call "creative directors of code." Not a loss of craft - a reinvention of it. Copado's CEO predicts that by mid-2026, teams will spend 60% of their time on verification and quality gates - up from 20% on traditional coding. The job literally inverted.
"Companies are no longer screening for syntax fluency; they're screening for judgement."
- Vikas Aditya, CEO of HackerEarth
The New Job
So what does a steward actually do all day?
There's a loop: the system observes your environment, comprehends the context, and proposes a change. You govern - approve, reject, or adjust. The system executes and verifies.
Six steps. You own one of them. But it's the one that matters.
Your judgment is the irreplaceable part. That's not less work. It's the right work.
What We're Looking For
Two people. Same Claude subscription. Same models. Wildly different results. The difference isn't the tool - it's the steward. We've written about why your base matters more than the AI. Here's what that base is made of:
Judgment over syntax. Can you read AI output critically? Can you spot when it's heading down the wrong path - not because the code won't compile, but because it shouldn't exist?
Context over speed. AI is fast. You provide context. "This function looks right, but it assumes X, and our system doesn't work that way." That's organizational knowledge. You can't prompt for it.
Taste over volume. The best stewards don't produce more - they produce right. They know when AI is generating elegant solutions and when it's generating massive overkill. That's taste. It compounds.
Creation over configuration. We don't need people who configure existing systems. We need people who build new things - and whose judgment ensures those new things are worth building.
The developers who thrive in this world bring something AI can't: the ability to decide what should exist. Not just what can.
The Invitation
You're already a steward. You just haven't named it yet.
Every time you review AI output and catch something wrong - that's stewardship. Every time you approve a pattern and it runs automatically next session - that's compounding. Every time you reject a suggestion because you know your domain better than any model - that's judgment.
The best developers have always been stewards. They mentored. They maintained coherence. They protected quality. They just also had to write code, because there was no other way to get it done.
Now there is another way.
The job isn't disappearing. It's being revealed. The stewardship that was always the valuable part is finally becoming the explicit part.
Are you still hiring developers - or are you already looking for stewards?
Build anything with AI. Keep everything. Evolve forever.