The Case for Boring Technology in Small Projects

·

·

You want to build a side project. You hear that everyone is using Kubernetes, microservices, GraphQL, and the frontend framework that launched last month. You start architecting a system that could serve a million users.

Then you never launch it.

Boring technology is the most underrated competitive advantage in small projects.

Boy in front of computer monitor
A man who writes code. Photo by Arif Riyanto on Unsplash.

What boring technology means

Boring technology is tools you already understand, tools with stable documentation, and tools that have been around long enough that every problem has already been solved on Stack Overflow.

For a web project, that might mean:

  • PostgreSQL instead of a new NoSQL database
  • A single VPS instead of Kubernetes
  • Server-rendered HTML instead of a single-page application
  • Plain CSS instead of a design system with thirty dependencies

Why boring wins for small projects

1. You ship faster

You do not spend two days configuring a service mesh. You spend two days building features. The goal of a small project is to validate an idea, not to demonstrate infrastructure.

2. You can hire or find help easily

If you need a freelancer or a collaborator, finding someone who knows PostgreSQL is easier than finding someone who knows the database you picked because it was trending on Hacker News.

3. Fewer things break

Boring technology has boring failure modes. When something goes wrong, the error message means something, and someone else has already fixed it.

4. It costs less

A single VPS costs $5–$20 per month. A Kubernetes cluster costs more in management time than in infrastructure, and you probably do not need it yet.

When to introduce complexity

Add complexity only when you have a problem that boring technology cannot solve. You outgrow a single server? That is a good problem — it means people are using your project. Split the database when queries get slow, not before.

The trap

Choosing exciting technology feels like progress. It is usually procrastination. You are avoiding the hard work of deciding what your project actually does by focusing on how it is built.

Launch with boring technology. You can always migrate later. You cannot migrate a project that never launched.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *