Half Done

I’ve been building things on nights and weekends for years now, and at some point I noticed a pattern. Everything is half done. Not abandoned — that’s a different thing entirely. More like... perpetually in progress. Somewhere between “oh this actually works” and “I should really ship this.”

By day I’m a software engineer. The rest of the time I’m tinkering with micro SaaS ideas — small, focused tools that each solve one specific problem. The goal is side income, but honestly I just like building them.

None of these are finished. Most won’t be for a while.

That’s kind of the point of this blog. No tutorials. No grand frameworks for productivity. Just notes from the middle of building things — what’s working, what broke, what I figured out at 11pm that I’ll forget by morning if I don’t write it down.

The name is intentional. “Half done” isn’t a confession. It’s the default state. You’re always half done. The interesting stuff happens in that gap between starting something and actually shipping it — the debugging, the pivots, the moments where you realize your whole approach was wrong.

So that’s what I’ll be writing about here. We’ll see how it goes.