The graveyard of 80%-done side projects isn't a motivation problem. It's a skill gap — because finishing is a different skill than building, and most of us only ever practice building.
The first 80% of a project is the fun part: green fields, fast progress, every day visibly better than the last. The final 20% is error states, empty states, the settings page, the onboarding, the cut list. It's deciding what the thing is by deciding what it isn't. Client work forces you through this; side projects let you escape to a new green field instead.
Why it matters professionally
Every meaningful career step I've made traces back to something finished. Not big — finished. The icon set got me the conference talk. The journaling app got me the job interview. A finished small thing beats an ambitious dead repo every time, because finished work is the only kind that can travel without you standing next to it explaining what it was going to be.
The mechanics of finishing
- Define done in writing before you start — scope creep is unfalsifiable otherwise
- Cut features, never quality; a small polished thing outranks a large rough one
- Set a ship date tied to something external you can't move
- The last week is only allowed to remove things
A side project isn't practice for building. You already know how to build. It's practice for shipping.
My rule now is one in flight at a time, and nothing new starts until the current one has a URL. It's cost me a dozen exciting starts — and given me the six finished things this site is actually made of.