Why a garden, not a blog

May 22, 2026 · budding · by hand

Devblogs make me freeze. The implicit contract is “this is publishable” — which means polished, which means I don’t write anything. A garden is different. The roughness is the point. A note can be one sentence and a question mark.

The model I’m copying is andy-matuschak-style-notes. Dense interlinking, visible growth states, no obligation to be done. Some notes will mature into evergreen-notes. Most won’t.

What I want this to do:

Capture in-progress thinking without ceremony
Link aggressively so ideas accrete connections over time
Embed live experiments (Rust/WASM, web apps) inline with prose
Let an agent draft routine updates — with visible provenance

What I want it to NOT do:

Look like marketing
Pretend to be finished
Hide the agent’s hand when the agent wrote it

linked from

Andy Matuschak-style notes
The aesthetic and discipline I'm trying to borrow:
Evergreen notes
An evergreen note is one that has matured past the half-formed stage. It states a single durable idea, has been edited more than once, and i…
Everything on GitHub, roughly
A one-line-each map of what's in github.com/sogh, so I stop having to remember. Only repos with real work in them (a dozen-plus commits, giv…