Why the boring technology keeps winning
Novelty is a cost you pay every day for years. Most systems cannot afford more than a small amount of it at once.
Every engineering organisation has a finite budget for novelty. Not money — attention. The capacity to hold in mind a system whose failure modes are not yet understood, whose documentation is thin, and whose behaviour under pressure is a matter of conjecture. That budget is small, it is shared across the whole estate, and it is spent whether or not anyone is tracking it.
This is the strongest argument for boring technology, and it has nothing to do with conservatism. It is a question of allocation. Every unit of novelty spent on a solved problem is a unit unavailable for the problem that is genuinely yours.
What boring actually buys
A mature technology comes with a body of knowledge that no amount of engineering talent can substitute for. The failure modes are catalogued. The upgrade paths have been walked and written up. Your specific error message has been searched, answered and argued about by people who had the same problem in 2017. Hiring is straightforward, because the skill is common. Operational patterns are established, so the answer to “how should we run this?” is a decision somebody else already made well.
None of that appears in a technology comparison. All of it determines what the next three years feel like.
Spending the novelty budget well
- Spend it where the problem is genuinely unusual, not where the solution merely looks appealing.
- Spend it on one thing at a time. Two novel components in one system multiply the debugging surface rather than adding to it.
- Spend it where you can retreat. Novel choices that are cheap to reverse are a different class of risk from ones that shape your data model.
- Do not spend it on infrastructure that supports revenue-critical paths unless the existing option has actually failed you, rather than merely aged.
- Keep an explicit count. Most teams are surprised by how many novel dependencies they hold once someone writes the list down.
The argument against, taken seriously
There is a real cost to this discipline, and it deserves acknowledgement. Organisations that never spend the novelty budget accumulate a different debt: they end up on technology the market has moved past, hiring from a shrinking pool, unable to attract engineers who want to work on something current, and eventually facing a migration that is far larger than any of the ones they avoided.
The point is not that new technology is bad. It is that novelty is a scarce resource with a real price, and should be spent on purpose rather than by default.
Let's build the system your business will run on next.
Tell us where it hurts. We'll bring the architects, engineers, and delivery model to fix it — and scale it.