There was a time when setting up a new project was a rite of passage. Days of Webpack config, Babel plugins, ESLint rule debates, directory-structure arguments. I did my share of it, and I have a confession that took me years to arrive at: none of that work was the product. Every hour spent tuning a build pipeline was an hour the actual thing, the site, the tool, the label's release pipeline, did not exist. In 2026 my tolerance for configuration is zero, and the industry has finally caught up. Opinionated defaults won.

The tools that made boring a feature

• Vite replaced the Webpack era with near-zero config and a dev server that starts before you've switched tabs. The debate is over; nobody misses it.
• Biome does what Prettier and ESLint used to require two configs and a merge strategy for, one fast toolchain, one file, almost no setup. This very site runs on it.
• Next.js and Remix end the router debate by making the file system the router. You stop designing infrastructure and start dropping files into folders.

Notice what these have in common: each one makes a strong decision on your behalf and takes the question off the table. That is not a limitation. That is the product.

Why small operations benefit most

An enterprise can spend weeks custom-tuning a pipeline because the pipeline amortizes across hundreds of developers. A solo builder or small label gets no such amortization. Configuration debt is paid alone, at night, from time that should have gone into the thing you're actually building. And there's a quieter benefit: when you use the default configuration everyone else uses, your problems are already solved somewhere. The bug you hit at 1am is a search away from the answer, because ten thousand people are standing in the exact same spot. Custom pipelines are lonely.

Trading flexibility for velocity

Yes, opinionated tools mean you can't customize everything. Good. The constraint is the feature, it closes the door on bikeshedding and leaves only the work that matters. I've shipped more since I started treating configuration as a cost than I ever did when I treated it as a craft.

A quieter take

I came up in an era where tinkering was identity, if you hadn't rebuilt the toolchain, were you even a developer? That was always a trap dressed as rigor. The craft was never the config file. The craft is the product, the design, the catalogue, the audience. Take the defaults. Spend what you saved on the thing only you can build. Full disclosure of my hypocrisy budget: the reverse proxy in front of this site is hand-configured nginx, and I love it. Defaults where the industry has converged; hands-on where you actually live.