In this discussion, Pip and Mara explore the recurring technology hype cycles, focusing on a consistently misleading phrase: “This is the one.” Over four decades, various technologies have been prematurely declared the future, only to be forgotten when newer contenders appear. They advise approaching tools with skepticism, emphasizing problem-solving over hype.
Pip: Sumir Nagar has spent four decades watching the same sentence get delivered with total confidence in rooms full of smart people — and he has thoughts.
Mara: This episode covers one extended argument about technology hype cycles: why we keep mistaking detours for destinations, and what the pattern looks like when you lay fifty years of it on a single timeline.
Pip: Let’s start with the graveyard.
The Graveyard of Sure Things
Mara: The central claim here is about a sentence — one specific sentence that has been delivered with complete confidence across four decades, in firms that no longer exist and firms that now run the world.
Pip: And the sentence is this, quoted directly: “This is the one. This is where the industry is going. We need to be on it.”
Mara: That sentence has been said about the relational database, about the technology that was going to replace it, about a dozen programming languages, twice as many frameworks, and right now, in more or less every technology meeting on Earth, about artificial intelligence.
Pip: The remarkable part is not that the sentence keeps being wrong. It is that we forget it was wrong the moment the next candidate shows up.
Mara: The post works through specific cases. PowerBuilder, released in 1991, was a genuine productivity revolution for client-server business applications — close to a million developers worldwide by the late nineties, running critical systems inside major banks. Then the web arrived, Java was free, and the migrations began.
Pip: A tool that was excellent for one leg of the journey got asked to be the whole destination.
Mara: Sybase is sharper still. By 1993 it was the world’s second-largest enterprise client-server database vendor, growing at over sixty percent a year, closing on Oracle. Then it licensed its own database code to Microsoft, which turned it into SQL Server and competed Sybase into the ground. Its market share fell below four percent by 2002.
Pip: They armed their own executioner and called the deal a partnership. That one stings.
Mara: The NoSQL story runs the other direction — enthusiasm that swung all the way out and all the way back inside a single decade. SQL was declared dead around 2009. Then Amazon Aurora, a SQL-compatible database, became by AWS’s own chief technologist’s description the fastest-growing service in the history of Amazon Web Services.
Pip: The industry traveled in a circle, arrived back where it started slightly out of breath, and called the return a breakthrough.
Mara: Blockchain gets its own headstone and a different epitaph. The others were good tools mistaken for destinations. Blockchain was, as the post puts it, “a genuinely clever answer that went looking for a question, and largely failed to find the ones it had been promised.” Gartner by 2024 had so lost interest it signaled it might stop publishing a hype cycle for it entirely.
Pip: So what is the actual advice? Because “be more humble” is not a roadmap.
Mara: The post is direct on this. The engineers who survived these cycles best were never the earliest or most enthusiastic adopters. They asked not “is this the future?” but “what specific problem does this solve well, and what will it cost me to leave when something better comes?”
Pip: Hold the tool loosely. Keep the receipt.
Mara: And the post closes by naming the current occupant of the boardroom — AI — and refusing to call it. It may be the web, a genuine civilizational shift. It may be another Rails. The confidence in the room, the post argues, tells you nothing about which it will be. The confidence was identical every previous time, including all the times it was wrong.
Pip: Which brings us to the costs that do not disappear — they just move.
Mara: The pattern is the same whether the technology succeeds or fails: the prophecy outruns the tool, and someone pays the difference.
Pip: Next time — what that bill actually looks like, and where it ends up.
Leave a Reply