Why Engineers Should Tend a Digital Garden
Moving away from transient streams toward compound personal knowledge networks.
Most technical blogs operate like chronological streams: you write an article, publish it, and rarely touch it again. Over time, half of the archive becomes stale or obsolete.
A Digital Garden takes the opposite approach. It is an evolving workspace designed around ideas, connections, and continuous refinement.
Streams vs. Gardens
| Aspect | The Stream (Traditional Blog) | The Garden (Digital Garden) |
|---|---|---|
| Organization | Chronological (reverse-date) | Associative / Interlinked |
| Maturity | All posts presumed “complete” | Explicit growth stages (🌱, 🌿, 🌲) |
| Maintenance | Publish and abandon | Continuous pruning and nurturing |
| Structure | Linear narrative | Web of connected concepts |
How Breath Implements the Garden
- Bi-directional Wikilinks: Connect notes using
[[note-slug]]syntax to automatically generate rich backlink networks. - Interactive Note Drawers: Preview linked notes in Andy Matuschak-style slide-over panels without losing reading context.
- Maturity Badges: Visually distinguish between raw sparks and battle-tested evergreen principles.
In Practice
Andy Matuschak talks about this exact philosophy in his 2022 talk on working with evergreen notes:
A useful conversation on the subject from X:
Further Reading
The concept was popularized by Maggie Appleton’s essay on digital gardens, and the Evergreen note-writing approach is documented in detail by Andy Matuschak. For the tooling behind this site, check out the Breath source code and the Astro framework. A second video walkthrough of the same ideas is embedded below: