How to Fix an Over-Engineered Frontend (When Plain HTML Was Enough)

Every few months, I watch a junior dev spin up a new React app with Next.js, Tailwind, a state management library, and three different build tools — for what turns out to be a mostly static page with a contact form.

I've been building for the web since the jQuery days. And look, I genuinely like React. But I've also shipped projects where the framework was the problem, not the solution. The real issue isn't nostalgia — it's that we've lost the ability to diagnose when our tooling is working against us.

Let me walk you through how to recognize an over-engineered frontend and what to do about it.

The Symptoms

You know your frontend stack is fighting you when:

• Your build step takes longer than your deploy
• You have more config files than actual page templates
• node_modules is larger than your entire backend
• You're debugging hydration mismatches on a page that barely has interactivity
• New team members need a full day just to understand the dev setup

I hit this exact wall last year on a client dashboard project. We'd started with Next.js because "we might need SSR later." Six months in, we had 47 dependencies, a 90-second build, and exactly zero pages that actually needed client-side rendering. The whole thing could have been server-rendered HTML with a couple of