February 10, 2026
3 min readBuilding in Public: Why I Started Writing Again
After months of building in silence, I built a pipeline that turns discoveries into published writing — not through content marketing, but by capturing what matters in the moment.
After months of building an AI operating system called Reeves, I realized the most interesting discoveries were trapped in conversation logs and devlogs that nobody would ever read. So I built a publishing pipeline that captures insights at the moment they happen.
The spark
Somewhere between the third cup of coffee and the fourth git rebase, I realized I'd been building interesting things for months without writing a single word about them.
Not because I didn't have things to say. Because the gap between doing the work and talking about the work felt too wide to cross casually.
What changed
I built a publishing pipeline. Not a blog platform — a pipeline. Content flows from AI-assisted conversations through a review queue into this site. The articles aren't generated; they're captured. The AI helps me notice when something I figured out is worth sharing.
That shift — from "I should write a blog post" to "this discovery should be a blog post" — changed everything.
What you'll find here
This isn't a content marketing operation. It's a notebook that happens to be public.
You'll find:
- Technical deep-dives on things I'm actually building (AI systems, infrastructure, agent architectures)
- Honest retrospectives on what worked and what didn't
- Patterns and techniques that emerged from real work, not theoretical exercises
The writing will be first-person, specific, and occasionally wrong. That's the point.
The bigger picture
We're in an era where AI can help us think and share. The bottleneck isn't ideas or even execution anymore — it's the gap between discovery and communication. I'm trying to close that gap.
Welcome. Let's see where this goes.