The posts that say "I don’t feel like a developer anymore" are not about AI. They’re about your boss reading one thread on LinkedIn and deciding everyone on the team needs to completely change how they work.
I often see this confused. Programmers who voice existential dread are mixed up with "anti-AI luddites." However, if you look at the conversations carefully, it’s not about "this tool exists." It’s more about "my manager mandated this tool for everything, and now my work is meaningless."
The real complaint isn't about Copilot
A post that went viral entitled “Don’t feel like a developer anymore after AI” has received thousands of responses across developer communities. The feeling is widespread. People are saying they’ve been reduced to monitoring and checking AI work.
But here's what I notice in those threads. The devs who feel worst aren't the ones experimenting with AI on their own terms. They're the ones whose managers mandated AI-first workflows without asking what problems actually needed solving.
There's a difference between "I chose this tool because it helps me" and "my skip-level saw a demo and now we have an AI-output quota." 🙃
Autonomy is the whole game
Decades of research on developer productivity say the same thing. Autonomy over tools and process is the single biggest predictor of job satisfaction.
→ Devs who choose AI tools feel empowered
→ Devs who are told to use AI tools feel surveilled
→ Same technology, completely different emotional outcome
When a manager says "use AI to ship faster," what a developer hears is: "your craft doesn't matter, only throughput matters." That's not an AI problem. This issue has nothing to do with AI.
The identity crisis is real but misattributed
There are developers who truly enjoy solving puzzles, designing architecture, debugging, and getting into the flow of writing code. But if you take all of that away and instead tell them to "review this AI slop and correct its hallucinations," it's definitely going to seem like a different job, because in reality, it is a different job.
However, there is no compulsion to use them for personal projects. There is no compulsion for open source maintainers to accept AI generated PRs. The coercion is organizational not in the existence of the tool.
The developers who are really winning with Ai right now? They chose when to leverage it for the boilerplate they despise writing. They chose when to ignore it and work on the fun stuff. They have control. 🎯
What managers get wrong
The pattern I see everywhere:
→ Manager reads "10x productivity with AI" article
→ Manager mandates AI usage across the team
→ No discussion about which tasks benefit
→ No acknowledgment that some work is better done by humans
→ Developer satisfaction craters
→ Manager blames developers for "resisting change"
This is not an adoption strategy. It's cargo culting. And it is causing people to burn out faster than any tool ever could.
The fix is boring
Give developers choice. Let them integrate AI where it helps them. Measure outcomes, not tool adoption. Stop treating "uses Copilot" as a KPI.
The developers who feel like developers again will be the ones whose managers trust them to decide when AI helps and when it doesn't. That's it. That's the whole insight. No framework needed. No transformation roadmap. Just trust. 💡
It's not true that AI took away developer joy. The real reason was taking away developer autonomy. AI was just used as an excuse.
Have you ever been forced to use AI tools in your job? Did it help — or did it make you feel like a code reviewer for a mediocre junior dev? Tell me all about it.
Top comments (0)