Why This Digital Garden Exists

This is a digital garden, not a blog in the tidy, finished sense. Some pages here are seedlings, a rough note I wanted to get down before it slipped away. Others are essays I’ve tended for months. They all grow in public, and I keep editing them as my thinking changes.

The throughline is AI for knowledge work: how AI changes the way we capture and organize what we know, automate the busywork around it, and write documentation that machines, not only people, can actually use. That last piece has a name I keep coming back to, agent readiness, and it runs through a lot of what I write here.

I arrived at this by a long detour. I spent more than two decades in software, first writing C and Java, then building and shipping DRM and content-security products for media and streaming, most recently in developer relations at a content-security company. That background isn’t a separate topic I set aside to talk about AI; it’s the reason my AI takes stay concrete. Years of explaining hard systems to engineers, and writing the documentation they depend on, taught me exactly where a vague instruction starts costing you. An AI agent reading those same docs only raises the stakes.

So this garden grows along a few recurring threads:

• Knowledge management: capturing what you know so you, and your tools, can find it again.
• Automation: handing repetitive work to language and image models, and what building real pipelines taught me, including a side project with nothing to do with my day job.
• Agent-ready docs: structuring documentation so a careful engineer and an AI agent can both follow it.

Some of these notes are technical. Some are closer to thinking out loud. A few will be wrong, and I’ll fix them in place rather than pretend the first draft was final. That’s the whole idea of a garden.

Pull up a chair. Things will change.