The Case for Boring Tech in Creative Work

There's a paradox I keep running into in my work. The projects that look the most experimental — the ones with fluid animations, unusual layouts, and moments that feel genuinely surprising — are almost never built on experimental technology.

Rift, my WebGL music visualiser, runs on a three-year-old version of a well-understood rendering pipeline. Caramel, the e-commerce platform, uses PostgreSQL, Next.js, and Stripe. Nothing novel. Nothing that would raise an eyebrow at a tech conference.

The reason is simple: when your creative energy is going into the product, you can't also spend it firefighting your infrastructure. Boring tech frees up attention. It means the third Saturday of debugging isn't about a framework's undocumented edge case — it's about the thing you're actually trying to make.

This isn't an argument against innovation. It's an argument about where to innovate. The rule I've landed on: innovate at the interface, conserve at the foundation.

The interface is where users live. It's where the seconds of surprise happen, where you earn the emotional response you're designing toward. That deserves every ounce of creative risk you have to give. The foundation — the database, the deployment pipeline, the state management — is infrastructure. Infrastructure should be invisible. It should work.

Next time you're starting a project, ask yourself which parts genuinely benefit from novelty, and which parts you're choosing because they're interesting to you as an engineer. Both are valid reasons — just name them clearly.