The Cost of Cheerleading
Technology hype in our industry tends to work like a ratchet: we celebrate the systems we use, and even when reality fails to match the praise, we rarely dial it back. Decades of pushes for XML, Scala, PHP, MySQL, CouchDB, Erlang, CoffeeScript, Node, Rails, React, MongoDB, and countless others have left a trail of tools that looked promising at the outset. Some remain perfectly fine choices today. Many do not.
Existential problems—a pathological lack of runtime safety, a decaying ecosystem, or a design that makes operation a burden—only become clear with hands-on use. By then, the cost of walking away is high enough that rational teams stick with a system they know is flawed. Sometimes the tool was never good; sometimes the state of the art simply moved on.
Why Nobody Says Anything
It is a very human instinct to withhold criticism. Real people build and maintain these technologies, and often they are people we know and like. Speaking ill of a system we are realistically married to for the foreseeable future rarely feels personally useful.
But silence has wider consequences. By not articulating the problems in our stacks, we cheat the people and companies who have not adopted them yet. The insight you gain from being on the inside—the disastrous pitfalls, vampiric operational overhead, chronic underdesign, or simple obsolescence—never makes it into the manual. It is often not visible until a team is already waist deep and fully invested at great expense.
This is not an argument for slinging mud. Honest, detail-oriented, thoroughly researched criticism—even when it is critical—may be the best help you can offer your fellow builders. By sharing what is wrong and what the tradeoffs really are, you can inform better decisions and potentially save millions of hours of productivity that would otherwise be lost to hype.
