Shipping small things on purpose
1 min read
Big projects teach patience. Small ones teach finishing. For the past three years I have tried to ship one small, complete thing every month, and the constraint has done more for my craft than any course.
The list
I keep a plain text file of ideas that would take a weekend or less: a colour tool, a tiny library, a single interaction done really well. Most never get built. That is the point — the list is a place to put ideas so they stop nagging.
Four rules
- One weekend. If it can't be shipped in two days, it is not a small thing.
- A real URL. It is not finished until someone else can open it.
- No accounts. Anything that needs a login is too big.
- Write one paragraph. Every project gets a short note on what I learned.
Finishing is a skill, and like any skill it needs reps.
What came out of it
Some of these grew up. Springboard started as a single page for tuning one spring. Swatchbook was an afternoon experiment with a photo of a market stall. Most stayed small, and that is fine — each one taught me something I used in client work the following month.
# the whole deploy step for most of them
pnpm build && npx vercel --prod
If you have been sitting on a big idea for a year, try shipping a small one this weekend. It is a surprisingly good way to get unstuck.