Why I finish small projects
The case for building things you can complete in a weekend.
For years I had a folder of half-built apps. Each one started with real excitement and died somewhere around the third weekend, when the interesting part was over and the boring part arrived.
What changed wasn’t discipline. It was scope.
Small enough to see the end
If I can picture the finished thing — the whole thing, including the dull bits — I’ll probably finish it. If I can’t, I won’t. That’s it. That’s the whole rule I use now before starting anything.
A weekend project doesn’t mean it takes a weekend. It means the shape of it fits in a weekend’s worth of thinking. The building can take a month.
Finishing teaches more than starting
Starting is the fun part and the part we’re all good at. Finishing is where you meet the problems that actually matter: naming things, handling the empty state, deciding what to cut, writing the one paragraph that explains what this is for.
I learned more from the last mile of a tiny bill-splitting page than from three months on an ambitious app that nobody, including me, ever used.
A finished thing changes you
There’s a quiet confidence that comes from having shipped. Not because the thing is impressive — most of mine aren’t — but because you now know you’re someone who gets to the end.
So I keep the list short. One project at a time, small enough to finish, written down before it’s built. The ideas I turn down don’t disappear; they wait, and the good ones come back sharper.