I don’t force projects anymore. If I’m not feeling it, I don’t touch it. I’ve learned I do my best work when something pulls me in—when it feels like the project is ready, not when I schedule it.
Lately, most of my energy’s gone into code. Tools. Infrastructure. I built the Core API because I needed it. I didn’t try to make a product out of it. I just wanted something flexible, fast, multi-tenant, and mine. Now everything plugs into it. It made the rest easier.
The RC boat’s on pause right now. But it’s not forgotten. That thing’s wired up with cameras—one above water, one below. I was building AI-based navigation that used a live video feed. Stream goes in, object detection runs live, and based on what it sees, it decides where to steer. I had Redis queues, TensorFlow models, and a feedback loop that could even stop the boat or turn if it saw something like a crab or a buoy. That’s still sitting on the shelf, waiting. And I’ll come back to it when it calls me.
That’s how most of my projects work now. They aren’t forced. They’re waiting rooms. I rotate between them as ideas come in. Sometimes I’m building a logging engine. Sometimes I’m wiring GPIO pins. Sometimes I’m deep in Apache config hell because I want better control over caching. And then sometimes I’m not building at all. That’s fine.
Everything I build stacks. The boat project isn’t dead—it’s just benefiting from the fact that I now have a better API, a better detection pipeline, and better logging because I worked on those when I felt like it. When I come back to the boat, it’ll be better because I let the rest mature.
I’m not in this to crank out shiny demos. I build when it’s time. And I always come back to the things that matter.