Software Engineering Was Never Meant to Be a Lifetime Career

“Will you still be writing code 20 years from now?” It’s the kind of question that surfaces over beers at a developer meetup, usually deflected with a shrug. But Sean Goedecke, a senior engineer at GitHub, recently posted a blog that refuses to let the question slide. His verdict, blunt and uncomfortable: software engineering is probably not a lifetime career anymore.

The myth of the forever job

For about two decades, software engineering enjoyed a run that’s genuinely hard to overstate. From the mid-2000s through the early 2020s, a six-month bootcamp could land you a six-figure salary at a name-brand company. No medical residency. No bar exam. No decade of apprenticeship. Just ship code that compiles.

That kind of payoff-to-effort ratio is historically rare. And inside that window, an entire generation of developers absorbed a comfortable assumption: keep your stack current, and you’ll still be writing production code at 55. Goedecke’s central provocation is that we mistook a once-in-a-generation labor anomaly for the natural order of things. The golden age wasn’t the baseline. It was the exception.

AI isn’t replacing coding. It’s repricing it.

The lazy version of this argument goes: “AI writes the code, so developers are toast.” Goedecke is more careful. He doesn’t think Copilot is firing your team next quarter. What he sees is a structural reweighting of what the job actually is.

For 20 years, the scarce, well-paid skill was writing the code. As AI assistants commoditize that act, the premium migrates elsewhere: deciding what to build, verifying what the machine produced, and integrating it into systems that don’t fall over. These aren’t trivially adjacent skills. They’re closer to product management, systems thinking, and technical review than to the craft most senior engineers spent a decade perfecting. The job title may not change. The job itself already has.

Careers were never going to stay linear

There’s a parallel signal worth noting. Outside tech, a recent Career Dojo interview profiled a former Coca-Cola copywriter who’s now an architect at Adobe. The title of the segment lands hard: “The Best Careers Are Rarely Planned.”

That’s not a tech story. It’s a labor-market story, and software engineering is finally catching up to it. The model of 30 to 40 years in one stack, one role, one company is now the outlier — and it’s getting rarer by the quarter. Read in that frame, Goedecke isn’t being pessimistic. He’s describing the mean reversion of a profession that was, briefly, allowed to be weirdly stable.

What to actually do about it

None of this reads as “don’t learn to code.” If anything, the opposite. Code literacy is becoming table stakes for an expanding set of roles — analysts, PMs, ops people, designers — not a shrinking one.

The bet that no longer works is single-skill specialization for 40 years. The bet that does: pair the coding fluency with something else that compounds — domain expertise, product instinct, fluency with AI tooling, the ability to write a clear memo. The T-shaped engineer wins this decade. And the mindset shift is the harder part: planning to reinvent yourself every five to seven years, instead of expecting one career arc to carry you to retirement.

Crisis, or just normalization?

Read generously, Goedecke isn’t predicting a collapse. He’s describing software engineering becoming a normal profession — one where doctors retrain into administration, lawyers move in-house, designers pivot to research. The exceptional thing was ever thinking we’d be exempt.

So: will the code you’re shipping this week still be feeding you in 2036? If you hesitated even a little on that, the useful move isn’t panic. It’s starting to sketch the next chapter while the current one is still paying well.