There is a certain pull toward the new. A framework that launched last month, a database that promises to make the old ones obsolete, a way of building that everyone on the internet seems excited about this week. We feel it too. And then, most of the time, we reach for the boring thing instead.
Boring technology is technology whose failure modes are known. When something breaks at two in the morning — and given enough years, something always breaks — you want to be standing on ground that thousands of people have already mapped. The exciting tool has exciting bugs. The boring tool has a Stack Overflow answer from 2014 that solves your exact problem.
The cost lands later
The trouble with novelty is that its cost is deferred. It feels productive on day one and expensive in year three, when the maintainer has moved on, the plugin ecosystem has evaporated, and the clever abstraction nobody fully understood is the thing standing between a charity and its month-end reconciliation.
So we spend our novelty budget carefully. One genuinely new idea per project, maybe, where it earns its keep — and proven, unglamorous choices everywhere else. It is not the most thrilling way to build. It is the way that is still working when we check back five years later.