have been thinking about something that nobody in tech wants to say out loud.
Not because it is controversial. Because it is uncomfortable in a way that hits closer to home than most tech debates do.
When I started using Claude regularly not just for experiments but as an actual part of how I work something shifted. Not in my output. My output got better. Something shifted in how I thought about myself.
The question I kept circling back to was simple and had no clean answer.
If a tool can do part of what I spent years learning to do, what does that make me?
The Developer Was Always More Than the Code
Here is the thing nobody tells you when you are starting out. You think you are learning to write code. But what you are actually doing is building a mental model of how systems behave. You are learning to think in a particular way. To break a problem into smaller problems. To reason about state, about failure, about edge cases, about what happens when two things interact that were never supposed to meet.
The code is the output of that thinking. It was never the thinking itself.
I knew this intellectually. But emotionally, the code felt like proof. It was the artifact that said: I was here. I understood this. I built this.
AI changed the artifact problem. The code still gets written. My name is still on the commit. But now I am less sure how much of the thinking was mine.
The Senior Developer Problem
I want to talk about someone I keep thinking about.
Imagine a developer who spent eight years getting really good at Angular. Not just using it. Understanding it. Reading the source code. Knowing why decisions were made. Building the mental model that lets them look at a bug and know within two minutes where it is hiding.
Eight years. Real years. Late nights, bad documentation, Stack Overflow at 2am, conference talks, side projects that went nowhere, arguments about architecture that sharpened their thinking.
Then a junior developer sits down with Claude and produces working Angular code in twenty minutes.
The senior watches this happen.
What does that senior feel?
I think the honest answer is not just threatened. I think they feel something that has no clean word in English. A kind of retroactive confusion. Like the ground shifted under years they already lived.
Did I waste that time? Was the struggle necessary or just the tax I had to pay before the shortcut existed?
The answer matters because it is not just about them. It is about what we tell the next generation of developers. It is about whether depth still means something.
Top comments (0)