·1 min read
The Boring Stack Wins
developmentcraft
Every few months, a new framework drops. It is faster. It is lighter. It rethinks the fundamental assumptions of web development. It gets 30k stars on GitHub in a weekend.
I have been building web apps for years. The projects that are still running, still maintainable, still deployed, are the ones built with boring technology. Next.js. Postgres. Server-rendered HTML. Simple CSS.
The exciting frameworks are exciting because they are new. Not because they are better. They solve problems you do not have yet and introduce problems you did not expect.
Boring technology means the Stack Overflow answers exist. The community has solved the common pitfalls. The hosting providers know how to run it. The junior developer you hire next year has already used it.
Excitement is a terrible basis for technical decisions. Reliability is not exciting, but it ships.
I have been building web apps for years. The projects that are still running, still maintainable, still deployed, are the ones built with boring technology. Next.js. Postgres. Server-rendered HTML. Simple CSS.
The exciting frameworks are exciting because they are new. Not because they are better. They solve problems you do not have yet and introduce problems you did not expect.
Boring technology means the Stack Overflow answers exist. The community has solved the common pitfalls. The hosting providers know how to run it. The junior developer you hire next year has already used it.
Excitement is a terrible basis for technical decisions. Reliability is not exciting, but it ships.