Engineering practice
Why I default to boring technology
June 22, 2026 · 4 min read
The allure of the new thing
Every project has a moment where a shiny new tool looks like it'll solve everything: a database, a framework, a queue you read about last week. It's tempting, and sometimes it's right. But most of the time, the pitch is measured against an imagined best case, not against how it behaves at 2am when it breaks in a way nobody's documented yet.
What "boring" actually buys you
Boring technology has already had its surprising failure modes discovered by someone else, written up, and fixed or worked around. That's not a lack of ambition — it's a transfer of risk away from your project and onto the years of production use that came before you. The interesting part of your system should be the product, not the plumbing.
When it's worth the risk
New tools earn their place when they remove a category of problem entirely, not just when they're more pleasant to write. If the boring option genuinely can't do the job, that's a real reason. "It's more fun" isn't — save that appetite for the parts of the system only you are building.
Got a project or idea you want to talk through?
Get in touchNew explainers, straight to your inbox
One email whenever a new concept goes up. No spam, unsubscribe anytime.