Building in the Open
18 shipped projects, why I build publicly, and what this blog will cover — the tools, the wins, and the faceplants.
I've shipped 18 projects. Some live in production with real users. Some are sitting in private repos waiting for me to remember they exist. A few crashed spectacularly within 48 hours of launch.
This is what happens when you're a one-person dev shop with ADHD energy and zero patience for things that don't work.
I build fast. I ship faster. And I've learned more from the things that broke than the ones that didn't.
Why Build in the Open?
Because hiding work until it's "perfect" is how nothing gets done. I've built AI tools, workflow automation, web apps, iOS apps, Chrome extensions — some polished, some held together with duct tape and optimism. They all taught me something.
This blog is where I'll document the process. The tools I'm using, the shortcuts I've found, the decisions that worked, and the ones that absolutely did not.
What You'll Find Here
- How I'm building products as a solo dev
- The AI tools and automation that keep me moving fast
- Project breakdowns: what worked, what didn't, and why
- The honest truth about shipping — including the faceplants
If you're building something, trying to ship faster, or just curious how one person cranks out this much work, stick around.
More coming soon.