Developers Are Dead (Again)

Every few years, someone declares developers dead.

When low-code and no-code tools showed up, developers were dead. When cloud computing made infrastructure easier, developers were dead. When SaaS replaced custom-built tools, developers were dead. When mobile development frameworks abstracted away the hard parts, developers were dead. When ChatGPT could write a function, developers were dead. Now that AI agents can ship entire features, well, developers are dead. Again.

I have been a developer for over two decades. I have heard this so many times that I have stopped flinching. But it begs an honest question: why is the entire tech industry, including developers themselves, constantly trying to make software engineers irrelevant?

I think I have an answer. And it is a little uncomfortable.

The Flaw We Refuse to Acknowledge

Developers, myself included, have a deeply ingrained way of thinking about problems. We want everything to become a system. We want an architecture. We want to model the world in elegant code and clean interfaces. We see a messy human process and our first instinct is to abstract it, decouple it, generalize it, and turn it into something that scales infinitely.

It is beautiful work when it is needed. The systems that run modern life — payments, logistics, communication, healthcare — exist because someone took the time to build them properly. I am not knocking that.

But here is the flaw. Most of the time, that is not what is being asked of us.

Most of the time, the business does not need a system. It needs a thing that works on Tuesday so a customer does not get stuck. It does not need a reusable framework. It needs a script that runs once a month and saves three hours. It does not need an elegant abstraction. It needs you to pick up the phone and figure out what is actually broken.

We resist that. We complain about technical debt. We argue for the proper solution. We push for the redesign. We sigh when someone asks us to “just make it work for now.”

And while we are sighing, the company is moving on without us.

Useful and Quick

The brutal truth is that the business does not care about your architecture. It cares about whether the problem in front of it gets solved.

Useful and quick. That is the bar. Not elegant. Not scalable. Not future-proof. Useful and quick.

The developers I have admired most in my career, and the ones I have worked with at the highest levels, all share this quality. They can absolutely build the cathedral when the cathedral is needed. But they also know when to slap together a duct-tape solution that ships today and revisit it later. They do not get emotionally attached to their code. They get attached to the outcome.

The ones who get replaced, threatened, or made obsolete are the ones who only operate in cathedral mode. The ones who cannot or will not solve a small, ugly, tactical problem because it offends their sense of craftsmanship.

Why the “Developers Are Dead” Narrative Keeps Winning

Every new technology that promises to replace developers wins by attacking the same flank: developers spent too much time building systems when the business needed solutions. Low-code wins because someone in operations got tired of waiting six weeks for a form. AI agents win because someone got tired of explaining a simple workflow to an engineer who immediately wanted to refactor the architecture.

The replacements are not better at building systems. They are better at being useful and quick.

That is the lesson I keep coming back to. Developers are not actually being replaced by these tools. We are being replaced by our own reluctance to operate in the messy, pragmatic space where most business value actually lives.

What This Means for Me

I am still a developer at heart. I still love elegant abstractions. I still get a small dopamine hit when I refactor something into a clean interface. But I have spent enough years watching companies reward useful and quick over elegant and slow that I cannot ignore the pattern.

Be useful. Be quick. Build the cathedral when the cathedral is what is actually needed. Otherwise, ship the duct tape and move on.

That is the developer who never goes extinct. Not because the tools cannot replace them, but because they never gave the tools a reason to.

Maybe that is the real lesson hiding inside every “developers are dead” wave. We are not dying. We are just being asked, again and again, to remember what we were hired to do in the first place.

Solve the problem. Quickly. So someone else can move on with their day.