Build one small feature for a side project

Side projects die from inertia — one focused session keeps the flame alive.

1.Pick one small, self-contained feature you've been putting off.
2.Write a 3-line spec before touching code.
3.Build it, test it manually, and push to your repo.
4.Write a one-line commit message that explains why, not what.

You'll need

Laptop
Development environment

Now doing

Build one small feature for a side project

00:0045–75 minhigh energy

Steps

0 / 4

Was this useful?

Help us know what works for you.

Why it works

An hour of focused feature work on a project you care about produces more momentum than three hours of distracted work. The 'care about' part matters — side projects die without intrinsic motivation, not without time.

Best for

•Weekend mornings
•Early evening after the main workday

Variations

•Pick the smallest possible shippable unit — a single form, a single bug, a single microcopy change. Ship it tonight.
•Write the changelog entry first; the scope becomes clear.

Frequently asked

How do I keep a side project alive?

Ship something every week, even tiny. Side projects die when the gap between 'last shipped' and 'today' stretches past 2 weeks — momentum, not scope, is the lifeblood.