Most side projects don’t end with a crash. They end with a slow, quiet stall. Not because the tech is too hard, but because the choices are too many.
The Productivity Illusion
We often mistake choosing for building. We spend hours mixing and matching options, reading “Stack A vs Stack B” articles, and planning for scale we don’t have yet.
It feels like progress because your brain is working hard—but nothing ships. In a side project, where there are no managers or deadlines to push you through the friction, this stall is usually fatal.
The Momentum Trap
Even small things start to carry too much weight. Which state management? Which folder structure? We pause more than we build.
Every choice burns your “momentum budget.” By the time you get to the actual logic, you’re already out of gas. That’s decision fatigue.
The Fix: Boring Defaults
I realized I was stuck not because I didn’t know what to do, but because I had too many ways to do it. The fix wasn’t to learn more. It was to decide less.
I started defaulting everything. Same auth flow. Same structure. Same deployment script. I don’t want to be creative with infrastructure; I want to be creative with the product. If I’ve done it before, I don’t rethink it.
The Goal
Now, I treat decisions like a tax. Every time I have to stop and think about “the right way” to do a small task, I’m paying a price.
If you want to ship, you have to outrun the fatigue. Pick the “boring” option. Use the tool you already know. Build the minimum version that works.
Because the goal of a side project isn’t to make perfect decisions. It’s to exist. You can’t improve what doesn’t exist.