Building in Public: Why I Started Writing
On shipping artifacts instead of consuming content, and why a personal blog felt like the right next step.
I’ve been building things for a long time — software, hardware, businesses, weird robots that spray people with water. But I’ve mostly kept the process private. The artifacts ship, the insights evaporate.
This blog is an attempt to change that.
Why now?
A few things converged:
- I keep solving the same problems twice. Writing forces me to crystallize what I actually learned, not just what I shipped.
- Consulting is storytelling. Every client engagement is a case study in tradeoffs. Writing sharpens the narrative.
- The best builders I admire write. Not thought-leadership fluff — real technical writing about real decisions.
What to expect
Short, opinionated posts about:
- Technical decisions — why I chose X over Y, what broke, what I’d do differently
- Product thinking — the gap between “technically correct” and “actually useful”
- Hardware & making — lessons from the makerspace that apply to software (and vice versa)
- Founder stuff — honest takes on building, not LinkedIn optimism
No schedule. No SEO optimization. Just writing when something’s worth writing about.
The stack
This blog runs on Astro with Markdown content collections, deployed to Cloudflare Pages. No CMS, no database, no JavaScript framework for rendering text. Just markdown files in a git repo.
That’s the whole point. The simplest thing that works.
First post. Let’s see where this goes.