A Developer's Anxiety in the Age of AI

Claude Wrote Better Code Than Me

This happened last week. I needed to build an API endpoint. I spent 30 minutes designing, coding, and running tests.

A coworker gave the same task to an AI assistant. It came back in 5 minutes. And honestly, the error handling was more thorough than mine.

That moment triggered a strange mix of emotions. Wounded pride? Anxiety? Or just the visceral realization that times are changing? All three, probably.

Two Years Ago, I Laughed

Two years ago, when I saw articles about "AI will replace developers," I laughed. "Yeah, right. Have you seen AI-generated code? It's hilarious." And back then, it genuinely was. The code was a mess.

But now it's not funny. AI-generated code has surpassed junior developer level. Simple CRUD is a given, and complex logic with good context produces surprisingly decent output.

"AI can't do creative work," people said. Honestly, what percentage of my work is truly "creative"? Eighty percent is pattern-based. If AI handles that 80%?

The Mood Around Me

When this topic comes up at developer meetups, reactions split into two camps.

"Still a long way off" camp: "Can AI design an entire system? Can it do requirements analysis? We're nowhere near that." They're not wrong.

"It's serious" camp: "At this rate, junior hiring will drop dramatically within three years. Some companies are already replacing roles with AI." They're not wrong either.

I'm somewhere in between. I probably won't get laid off tomorrow, but I have no confidence that I'll be doing the same work five years from now.

(This anxiety itself drains energy, but I can't not be anxious.)

What Should I Be Preparing?

"Developers who use AI well will survive," they say. Sounds right. But what exactly does "using AI well" mean?

Writing good prompts? That's going to become a general skill soon enough. Anyone will be able to do it.

Doubling down on what AI can't do? System architecture, business understanding, team leadership. But how long will those remain things "AI can't do"?

I'm essentially chasing a moving target. While I adapt, AI also advances.

The Scariest Scenario

The scariest thing isn't getting replaced "suddenly." It's getting replaced "gradually."

First, AI writes the boilerplate. Then unit tests. Then API implementations. Little by little, the scope of what I do shrinks. Like water slowly rising. When your feet are in it, you don't notice the temperature changing.

Then one day: "AI can handle that. Do we really need this many developers on the team?"

I hope that day doesn't come, but I can't be sure it won't.

Still, Code Has to Be Written

Even with the anxiety, I'll go to work tomorrow and write code. Ironically, I'm anxious because of AI while using AI as a tool to write code.

In the end, all I can do is "the best I can right now." Understand the system, build domain knowledge, leverage AI as a tool without becoming dependent on it. It's a cliche answer, but I don't know what else to do.

When I re-read this post five years from now, it might be "that was nothing" or it might be "I should've prepared more."

Not knowing is what makes it the most unsettling.