In praise of the less-is-more stack.

Last week I migrated a side project off four services and onto a single small server. The whole thing took an afternoon. I wrote two scripts. I deleted nineteen pages of YAML. The system has been quietly running ever since, which is, in software, the highest praise.

Every senior engineer I know has, in the last two years, told me some version of the same story. The job that used to require Kubernetes is now a SQLite database and a Bash cron. The microservice that needed three platform teams is one file. The frontend that used to need a sixty-megabyte client is server-rendered HTML, again, like it was twenty years ago, before we forgot.

The most underrated engineering virtue is the willingness to throw something away.

I want to be careful here. I am not making a small-is-beautiful argument because small is always beautiful. I am making it because, in the last decade, every default got bigger. The default React app ships more code than my first computer could store. The default cloud bill for a hobby project costs more than a real apartment in the city I grew up in. We didn't decide this. It accumulated.

The less-is-more stack is not minimalism for its own sake. It's a refusal to add what you don't need. It's a vote for clarity. Every tool you remove is a tool you don't have to learn, debug, upgrade, or explain to the next person who joins the team. Every script you write is one fewer dashboard you have to log into.

The joke is not really a joke. The Bash script is the thing. The fewer moving parts, the more you can move.