The developer identity crisis
The developer anxiety is real. Every week brings a new model, a new framework, a new "meta" for AI-assisted coding. The expectation seems to be that you should stay on top of all of it, all the time. I feel it too.
The developer anxiety is real. Every week brings a new model, a new framework, a new "meta" for AI-assisted coding. The expectation seems to be that you should stay on top of all of it, all the time. I feel it too.
But I think the anxiety is pointing at something real, not just FOMO.
Programming used to be harder
Five years ago, learning to code meant grinding through problems. You had to understand how things worked at a lower level. You'd dig through Stack Overflow, hit walls, figure out why something broke, and eventually get it working. That process was slow, but it built intuition. You learned how systems actually behaved, not just how to make them run.
People without a CS degree could still learn, but it took serious effort. The barrier was high enough that crossing it gave you real understanding of the tools you were using.
AI changes the path from idea to code
A wave of people got into programming during 2020-2021. Myself included. Many of us were just hitting our stride when AI tools started reshaping the field underneath us.
The distance from "I want to build this" to "it works" has compressed. AI tools have lowered the floor of what you need to know to ship something. You don't have to understand every part of the stack to get something running.
That's useful. It also changes what the market needs. Fewer developers will be required to do the same amount of work. That's already visible in how teams are staffed and how fast individuals can move.
What the role looks like next
Developers will shift toward two things: software architecture and AI operations.
The architecture part is about decisions AI can't reliably make: understanding tradeoffs, system design, long-term maintainability, and what to build and why.
The AI operations part is more hands-on. Less writing code line by line, more directing the process: breaking down problems into clear tasks, reviewing agent output, catching mistakes, and orchestrating work across tools and models.
That's already what the most productive people in this space are doing. The anxiety comes from watching that shift happen without a clear map for how to navigate it. But the map is forming. The developers who adapt are building judgment, and judgment is something no tool replaces.
Related posts
Most people close their laptop at 5 and go live their lives. That's reasonable. It's also going to collide with how managers think about output.
It's genuinely hard. You're not alone. And it does end.