Building in Public

The friction wasn’t in the writing. It was in the reviewing. I’d generate a draft, get distracted, then forget about it. Days later I’d find it buried in a folder, context gone, momentum dead. The writing was fine. The workflow wasn’t. I needed to review from my phone—while waiting for coffee, sitting on the couch, whenever I had two minutes free. The insight came from my smart home setup. When someone rings the doorbell, I get a notification with a video preview. Tap it, see who’s there, decide what to do. No app-switching. No mental overhead. ...

Here’s the thing about shipping code: the friction between “done” and “live” kills momentum. I used to write posts, save them locally, then go through this whole dance of uploading files, checking links, fixing formatting issues. By the time something went live, I’d already lost interest in the next idea. The gap between creation and publication was eating my motivation alive. This week something clicked. Instead of treating my blog like a static site that needed manual updates, what if it behaved more like a living system? What if pushing code meant going live instantly? ...

Every project starts with a problem you’re tired of solving manually. For me, it’s the mental load of tracking things that should track themselves. The weekly reviews that become monthly (then quarterly, then forgotten). The decisions that get delayed because the information isn’t ready. So I’m building systems to handle it. Not the flashy kind that make good demos. The boring kind that just work. This blog is part of that system. Instead of waiting until something is “ready” to share, I’m documenting as I go. Raw progress. Real timelines. ...