May 9, 2026

Side Projects: Why I Rarely Finish

Notes on starting too many projects, leaving them unfinished, and what writing helps me understand.

Development

I keep starting side projects and almost never finishing them.

I reach different points in the lifecycle when I stop working on it. Obviously there are valid reasons to put something down.

Why this keeps happening

Part of it is energy management. I love beginnings. Beginnings are all possibility and no maintenance.

Part of it is fear. Finishing means exposing the work. An unfinished project can still feel “full of potential.” A finished one can be judged.

Part of it is identity. I like seeing myself as someone who builds. But building includes the middle: debugging, rewriting, and polishing. That is where I usually disappear.

What writing changes

Writing slows me down enough to notice what I am avoiding.

When I write honestly, I can see the story I repeat:

  • New idea gives me momentum.
  • Friction makes me doubt the whole project.
  • Doubt turns into distraction.
  • Distraction becomes a new project.

Putting that in words makes it harder to pretend I am “just exploring.”

What I am trying next

I am not promising a perfect system. I am trying a smaller commitment:

  • One active side project at a time.
  • Weekly progress notes, even if the progress is tiny.
  • A clear definition of done before I start.
  • Shipping rough versions instead of waiting for a perfect one.

This post is part of that experiment.

If I can keep writing while I build, I might finally finish more than I start.