787 Upvotes and a Quiet Crisis: AI Isn't Taking Senior Developers' Jobs — It's Taking Their Identity

Spend enough time in developer forums lately and you start noticing a strange kind of post. Not salary negotiations. Not job-hopping advice. Confessions. “I don’t know why I’m doing this anymore.” One of them, written by a senior engineer, climbed to 787 upvotes. Stripped down, the title reads: AI is eating my career, and I don’t know what to do about it. It wasn’t a vent. It was a flare sent up by someone who assumed he was alone — and got hundreds of “me too” replies in return.

Let me be straight about one thing. This isn’t breaking news. The fresh community data over the last 30 days was thin, so think of this less as a trending moment and more as a current that’s been running under the surface of the developer world for a while. It’s worth pulling up anyway. Because this isn’t a passing mood. It’s a structural anxiety that keeps getting deeper.

It’s not the job. It’s the self.

Here’s the part most people get wrong. The standard framing of AI’s threat to developers is “the jobs are disappearing.” But the 787-upvote post wasn’t about that. The guy hadn’t been laid off. The paycheck still lands. The desk is still his. And he says he’s falling apart anyway.

Why? Because being a developer was never just a way to pay rent. The high of wrestling a brutal bug for three days and finally killing it. The ability to hold a sprawling system in your head and see how it fits together. The quiet pride of “I built that.” Those things stacked up into an answer to a bigger question: who am I. And AI started walking off with the core of it.

One reply stuck with me. “I’m not a person who writes code anymore. I’m a person who reviews code the AI wrote.” The workload didn’t shrink. The meaning drained out of it. That’s not a productivity problem. That’s an existential one.

The thing you were great at isn’t rare anymore

A senior engineer’s value comes from time. Years of trial and error compressed into instinct — the gut sense that lets you glance at a single line and think, that’s going to blow up in production six months from now. That was the weight of experience. That was what tenure bought you.

The problem is how fast AI is closing that gap. A junior working alongside a model now solves things that, a few years ago, would have meant walking over to a senior’s desk. Patterns a veteran spent a decade absorbing, the model spits out on demand. No, the AI isn’t always right. That’s not the point. The point is that the information asymmetry — the senior’s quiet monopoly on hard-won knowledge — has collapsed.

A former senior engineer turned YouTuber laid this out bluntly in a May video. It pulled close to 69,000 views and over 2,000 likes. The gist: yes, the market is cold, but the deeper shift is that experience itself no longer carries the premium it used to. Having done this for a long time isn’t a safe harbor anymore.

Why it hurts seniors more

Counterintuitively, this lands harder on seniors than on newcomers. Two reasons.

First, they have more to lose. A junior starts their career working with AI from day one. It’s the default, so there’s no sense of loss — you can’t grieve a world you never worked in. A senior remembers being good at this without the machine. They get to watch, in real time, a skill that used to make them stand out flatten into something ordinary.

Second, relearning is expensive. Adapting to new tools and workflows is hard for anyone, but it’s worse for someone who already mastered the old way. The better you were, the more painful it is to change direction. “Twenty years of sharpening this craft, and it’s worthless now?” — that feeling grabs you by the ankles and won’t let go.

So some get angry. Some go numb. Some quietly start scouting for an exit. The comment section under that 787-upvote post was exactly this landscape: no consensus, no answer, just a few hundred people shaking in their own particular way.

So where does this go

It’s too early to write the obituary. There’s a real counter-voice reading the same shift as an opening.

The move is to redefine the identity. “I’m someone who writes great code” is a definition on increasingly shaky ground. But “I’m someone who frames the problem, designs the system, and decides what actually matters” is still standing on solid rock. AI generates code. It does not decide what to build. When it serves up a wrong answer dressed in confident syntax, the one who can stop and say “no, not this” is still a human being.

Put differently, a senior’s value is migrating from the hands to the head. Not the speed of your typing — the quality of your judgment about direction. None of this is as easy as it sounds, and not everyone makes the jump. That’s exactly why this crisis is real. It’s not the kind of thing you can paper over with a feel-good pep talk.

That number — 787 — wasn’t one person shouting. It was hundreds of people resonating from the same unsteady ground. Technology has always reshaped what we do for a living. This time it’s reaching further, into the question of who we are. So ask yourself: is writing code a paycheck, or is it your identity? The answer decides whether this moment is a crisis or an opening.