The Case for Boring Technology
By Mykhailo Boichuk · Co-founder & Vice-President
In short
Boring technology is mature, well-understood tooling whose failure modes and limits are known. Choosing it over novel alternatives conserves the limited budget a team has for dealing with the unknown, because every new technology carries operational surprises that mature ones have already exposed and documented. Novelty is worth spending only where it provides a real advantage, not by default.
Novelty has a hidden operational cost
Every technology a team adopts comes with a tail of things that can go wrong: edge cases, performance cliffs, operational quirks, and failure modes. For mature technology, most of this tail has already been discovered by others, documented, and worked around. For new technology, the team discovers it themselves, in production, at inconvenient times. This is the hidden cost of novelty, and it is paid in incidents and lost time rather than in the initial adoption.
Boring does not mean bad. It means the technology has been used long enough that its sharp edges are mapped. A mature database, a well-worn language, a deployment approach that thousands of teams have run, all carry an accumulated body of knowledge that a newer alternative, however elegant, cannot yet offer.
A limited budget for the unknown
A useful way to think about this is that a team has a limited budget for dealing with the unknown. Each novel technology spends some of that budget, because it introduces problems no one has solved before. Spend it all on infrastructure choices and there is none left for the actual product, where novelty might genuinely matter. Choosing boring technology for the parts that are not your differentiator preserves the budget for the parts that are.
- Reserve novelty for the few places it gives a real, product-relevant advantage.
- Default to mature, well-documented tools for everything else.
- Count the operational cost of a new technology, not only its appeal.
When novelty is worth it
This is not an argument against ever adopting new technology. It is an argument for spending novelty deliberately, where the advantage is real and tied to what makes the product valuable. A new technology that solves a problem central to your product, that mature options genuinely cannot, can be worth its cost. The discipline is to require that justification rather than reaching for the new thing because it is interesting.
Key takeaways
- Mature technology has had its failure modes discovered and documented by others.
- Novel technology makes the team discover those failure modes in production.
- A team has a limited budget for dealing with the unknown; novelty spends it.
- Default to boring tools for non-differentiating parts to preserve that budget.
- Spend novelty only where it gives a real, product-relevant advantage.
Frequently asked questions
- What does boring technology mean?
- Mature, well-understood tooling whose limits, failure modes, and operational quirks are already known and documented from wide use.
- Why prefer boring technology?
- Because novel technology forces the team to discover its failure modes in production, spending a limited budget for dealing with the unknown that is better reserved for the product.
- When is it worth adopting new technology?
- When it solves a problem central to the product that mature options genuinely cannot, and that advantage justifies the operational unknowns it introduces.
About the author
Mykhailo Boichuk
Co-founder & Vice-President
Mykhailo is an engineer who builds native applications and the systems behind them. He concentrates on macOS and iOS performance, local-first data architecture, and the synchronization problems that come with offline-capable software.