Boring technology wins
The stack with the waitlist and the Discord will not be maintaining your website in five years. Something duller will.
Every so often a technical founder reads our build recommendation and gets a little quiet. They were expecting something newer. Something with a waitlist and a Discord. What they got instead was a stack that’s been around long enough to rent a car.
We get it. Nobody dreams about proven infrastructure. But we didn’t choose it to play it safe in the cowardly sense. We chose it because boring technology is what still works in five years, and five years is the actual lifespan of the thing we’re building.
What boring means
“Boring” deserves a defense, so let’s define it. It doesn’t mean old, and it doesn’t mean bad. Boring means known. A boring stack has been broken in every conceivable way by millions of people before you, which means its failure modes are documented, its edge cases are mapped, and the answer to your 2 a.m. bug already exists in a forum thread from years ago, solved, with a follow-up comment that says “thanks, this worked.”
An exciting stack is exciting precisely because none of that is true yet.
Excitement is a cost. Spend it where failure is cheap.
Here’s the pattern we’ve watched play out more than once. A business ships its site on whatever framework was being praised that year. It works, it’s fast, everyone feels current. Then the framework’s momentum moves on, because momentum always moves on. Two years later there’s a major version with breaking changes, the plugins never got updated, the developer who chose it took a new job, and every candidate to replace them quotes a rebuild, because nobody wants to inherit an ecosystem that’s already cooling. The site didn’t fail. Its foundation went out of fashion, and out of fashion quietly became out of support.
Trends are rented. That’s true of design, and it’s just as true of technology.
The bench you’re hiring from
The hiring math alone should settle it. A boring stack has a deep bench: thousands of developers who already know it, agencies who can pick it up without a ramp, freelancers in every city who’ve shipped a hundred projects on it. An exotic stack has a shallow bench that charges accordingly, and the bench gets shallower every year the hype doesn’t renew. You’re not just choosing what your site runs on. You’re choosing who’ll be able to work on it, and what they’ll cost, for the next half decade.
So before any tool makes it into one of our builds, it has to answer questions that have nothing to do with how it feels to use.
- Will this be maintained in five years, and by whom?
- Can our client hire for it, in Nashville or anywhere, without a nationwide search?
- When it breaks, is the fix a search away or a support ticket into the void?
- If we vanished tomorrow, could a competent stranger open the project and find their footing in a day?
Notice that none of those questions ask whether the technology is impressive. Your customers will never know what your site is built on. Not one of them has ever converted because of a framework. They know whether the site loads, whether checkout works, and whether the thing that worked last month still works this month. Boring technology is how the answer stays yes.
New tools audition at the edges
To be clear, we’re not against new. We’re against experimenting on your dime. New tools earn their way in the way anything earns trust: gradually, at the edges, on internal projects and things we just felt like making, where failure costs us an afternoon instead of costing you a quarter. Some of them graduate into the toolkit. Most don’t. That’s the point of an audition.
There’s a version of this argument that’s just fear of change wearing a blazer, and that’s not the one we’re making. Choosing boring isn’t refusing to move. It’s refusing to make your business the test track for someone else’s ambition. Boring stacks evolve too; they just do it slowly, with deprecation notices and migration guides and a decent apology, instead of a blog post announcing that everything you built last year is now legacy.
Five years from now, today’s most-hyped frameworks will have sorted themselves into two piles: the handful that became boring, and everything else. You want to be built on the first pile. You just can’t know which pile that is yet, which is exactly why we wait.
The most impressive thing your website can do in five years is still work.