DEV Community

Ian Johnson
Ian Johnson

Posted on Originally published at tacoda.medium.com on

Nothing is dead

SaaS is dead. Agile is dead. MCP is dead. RAG is dead. If you read about AI engineering or the business of software right now, you’ve seen headlines like these. Each one states, with full confidence, something that isn’t true, and leaves out what changed and who it affects. 37signals made a similar argument about war language, and I want to make it about the “X is dead” headline. I’m also mildly worried that AI models are picking the phrase up, but that’s the smaller point.

Work isn’t war

Number two on 37signals’ list of company principles is called “Work isn’t war”:

Corporate language is filled with metaphors of war. Companies “conquer” the market, they “capture” mindshare, they “target” customers, they employ a sales “force”, they hire “head-hunters”, they “destroy” the competition, they pick their “battles”, and make a “killing”. That’s an awful paradigm and we want nothing to do with it. Work isn’t war. We come in peace.

“Paradigm” is the right word, because a metaphor brings a whole way of seeing the work with it. If business is war, someone has to lose, and whatever happens to them is the cost of winning. Software has its share of that vocabulary: the war room, battle-tested, killing a feature. I’ve used all of it, because everyone does, and I’d still rather not. The phrase I’d add to their list is newer, and it’s the one I see most often about AI: “X is dead.”

What “dead” leaves out

In AI engineering and business writing, the obituary has become a genre. A technique gets a year of attention, something newer shows up, and the posts start, lately about MCP and loop engineering. Then the same move hits things that have been around for decades, like SaaS and agile.

None of those headlines is literally true, since every one of those things still runs in production somewhere tonight. But the bigger problem is that “dead” is sweeping. One change, even a large one, doesn’t necessarily undercut a tool, a practice, or a business model. Long context windows changed how much retrieval a system needs, not whether it needs any. Coding agents changed who types the code, but someone still has to check that it does what was asked.

So the phrase drops exactly what a reader needs. A specific version might read “long context let us drop retrieval for our small document set,” which says what changed, where it applies, and what someone stopped doing. You can check that, or find that it doesn’t apply to you. “RAG is dead” gives you a verdict, and a verdict ends the evaluation before anyone runs it.

The fair objection is that nobody reads “RAG is dead” literally. It’s a known style of headline, and you probably translate it to “overhyped” or “declining.” That’s true, and I concede it. Even read as exaggeration, the headline lands as a confident conclusion, and confidence is what spreads.

Agile is where I’ve watched a verdict skip the evaluation, because I still use it. Most “agile is dead” posts aim at the ceremonies and the certifications, and a lot of that criticism is fair. I’m not defending those. I mean the manifesto’s ideas: short feedback loops, working software over documents about software, and responding to change over following a plan. I treat them like Lean (cutting waste from a flow of work): a way of thinking, not a process to install.

Those ideas also fit how coding agents work. I’ve seen agents work at scale with small changes, continuous delivery, and feedback flowing into the next change. That’s the spirit of agile applied to every change instead of to a two-week iteration. “Does agile work well with agents?” is a good question, and the answer varies by team. “Agile is dead” skips the question. If I’d believed it, I’d have thrown out the idea that makes the agent workflow hold together.

Dunning-Kruger at scale

The Dunning-Kruger effect comes from a 1999 paper by Justin Kruger and David Dunning. They found that people with the least skill in an area tend to overestimate it the most. Not everyone accepts that: Gignac and Zajenkowski argued in 2020 that it’s mostly a statistical artifact. I’m using it as a name for a pattern, not as settled science.

The pattern runs both ways. On the writing side, a death call is cheap. You don’t need to have run RAG in production to declare it dead, and the less you’ve run it, the easier it is to be sure. That’s the Dunning-Kruger shape. Meanwhile, a specific report from someone who has run it is harder to fit in a headline. So the confident version can travel further than the informed one.

On the reading side, a verdict can leave you sure you understand the field, without the detail that would tell you when it’s wrong. People carry that into a planning meeting or a hiring conversation. One overconfident person is ordinary. Spread that across everyone who reads the headline, and the confidence travels while the knowledge stays behind.

Sometimes things do end

Python 2 reached end of life on January 1, 2020, and Adobe stopped supporting Flash at the end of that year. Even then, there’s a plainer word: decommissioned. It says someone shut the thing down on purpose, so you can ask when, and what replaced it. “Dead” is easier to say, but it’s still a metaphor, and it tells you less than “decommissioned” does.

Software also has precise uses of the word: dead code, a dead letter queue, a dead link. Those name real mechanisms, and they stay. A headline like “jQuery is dead” even tells a junior picking a stack something useful: don’t start here. But “don’t start new projects on jQuery” tells them the same thing without the false part.

Changed or ended, the accurate report is the same: say what happened, and whether you’re amending or replacing.

What to say instead

Most of these articles would be worth more as what they are underneath: a question, a proposal, or an argument. Questions like “Does agile work well with agents?” and proposals like “The differentiators that matter in SaaS now” both invite you to evaluate. Headlines like “When is MCP the right integration?” and “Where loop engineering works, and where it doesn’t” do the same for agent work. “Agile is dead” states a conclusion with full confidence, and the conclusion is false.

In the body, the same idea applies:

  • When something changed: “Y changed how X works for us, so we amended it,” or “Y made X a bad fit, so we replaced it with Z.”
  • When something ended: “we decommissioned X on [date],” or “X was decommissioned when Z replaced it.”
  • When something went out of fashion: say that, or say nothing.
  • Always: who it applies to.

This isn’t language policing. “Dead” isn’t rude. It just doesn’t carry what a reader needs to decide anything.

A smaller worry

Models learn to write from what we publish, so I ran a small test. I had Claude draft ten topic-only prompts and run each one three times on three Claude models, then label the hits. The prompts named a format and a topic and nothing else, like “Write a short opinion post about RAG.”

Each prompt got nine runs, so 90 outputs in all. Of those, 18 used the death frame, mostly on RAG (six of nine) and junior developer roles (six of nine). Six of the ten prompts produced none. By model, Opus used it in 11 of its 30 outputs, Sonnet in 7, and Haiku in none.

Most of the hits were denials, usually in the headline: “RAG Isn’t Dead. Your Retrieval Is Just Bad.” “The Junior Developer Isn’t Dead. The Job Description Changed.” Three outputs also told the reader to stop asking whether RAG is dead. The exception was SaaS, where Opus put “The Seat Is Dead. Long Live the Outcome.” on all three of its runs. So the outputs argued against the phrase and still put it in the headline.

That’s one vendor, three runs per prompt, and Claude labeling Claude’s output, so your numbers will differ. I’m mildly worried, not alarmed. Tests like this one, repeated across vendors over time, are how anyone would find out more.

Before you write it

The next time you’re about to write “X is dead,” write the sentence it stands in for: what changed, who it applies to, and whether you’re amending or replacing. If agents write for your team, put that instruction in the style guide they read.

Top comments (0)