Beyond the Code: The Developer Identity Crisis
Software engineering has always been a craft built on pride. For decades, our entire identity as developers was tied to one thing: writing every line of code by hand.
Before stepping into management, that was my entire world. That was my identity. I loved writing code. I loved taking a complex logic puzzle, digging into someone else’s broken implementation, debugging it, and bringing it back to life. There was real craftsmanship in knowing every single line, variable, and syntax choice in the codebase.
So when developers look at the rise of AI and feel defensive, threatened, or angry, I get it. I’m not writing this from the outside looking in. The loss of that identity is real, and it’s not something I’ve fully worked through myself.
I know developers who built their whole sense of competence around being the person who could out-debug anyone in the room, who knew the codebase cold. That’s a real skill, and for a long time it was the skill. Telling that person “focus on the bigger picture instead” doesn’t land as a promotion. It can just feel like the thing you were good at doesn’t matter as much anymore.
We’re asking people to let go of the very thing they built their careers on. And as a leader, I don’t have this fully figured out. How do we actually manage AI systems day to day? Do we trust an agent to write and test its own code, and if so, how much? I still don’t have a clean answer for that one. What does the role of a developer even look like now, what’s the process we even follow anymore? I’m asking myself these as much as anyone on my team is.
Here’s the part I keep coming back to: we’re not going back to how it was.
Not the last 30 years of it, anyway. I don’t think that’s a funeral for software engineering, though. It’s closer to what happened to furniture making once factories and machine tools took over what used to be entirely hand work. Furniture is still around. It’s just not built the old way anymore, not for most people.
When I was in the trenches writing code, there were high-level engineering problems I genuinely wanted to solve, but I just ran out of time. The manual boilerplate, the UI wiring, the basic syntax, the constant drumbeat of the 2-week sprint all ate up the bandwidth before I ever got near the interesting part.
I wrote about this in my last post. We’re not starting at step[0] anymore, the blank file and the manual wiring. We’re starting at step[10], past the boilerplate, into architecture, context, and intent. Once you stop measuring your worth by how much syntax you personally typed, that’s where the actual engineering work has always been waiting.
A few ways I’ve seen that show up so far:
You stop fighting UI components for hours and start actually thinking about the end-to-end user experience: the domain context, how the feature feels to use, not just whether it compiles.
Debugging stops being line-by-line and starts being about the system underneath it: security models, boundaries between services, what happens under load, whether the thing behaves the same way twice.
And the execution itself moves from you doing it to you directing it. Your debugging instinct doesn’t go away. It just moves up a level. You’re auditing the output, setting the guardrails, deciding what “good” looks like instead of typing it yourself.
If you’re anxious about this shift, I’d say lean into it, but I’d also say it’s fine if that takes a while. It took me a while.
Your value was never just your ability to type syntax into an IDE, even if it felt that way for a long time. It’s your problem-solving, your logic, your understanding of how systems actually behave. AI just takes the tedious part off your plate so you can get to the part that was always the real job.
The traditional developer role is changing. What isn’t changing is the instinct that made you good at this in the first place. You’re just pointing it somewhere higher up the stack now.
Where are you finding the most leverage right now? System architecture, UX flow, something else entirely? Or are you still fighting to keep the old way alive a little longer? I’d genuinely like to know. Drop it in the comments.