Digital Garden: Connected Thoughts
Welcome to my Digital Garden. Unlike a traditional stream-based blog where articles are static and ordered purely by date, a digital garden is an evolving web of interconnected notes at various stages of maturity.
Ideas in this space grow organically:
- π± Seedling: Initial thoughts, sparks, and rough working notes.
- πΏ Budding: Developing concepts that have been revised with references and examples.
- π² Evergreen: Mature, well-structured insights written to stand the test of time.
Core Explorations
- Abstractions Should Hide Complexity: Why deep interfaces minimize cognitive overhead.
- Complexity Grows Automatically: Systems naturally degrade unless actively simplified.
- Good Names Are Cheap Documentation: Naming is the highest ROI design activity in codebases.
- Preventing Goroutine Leaks: Practical patterns for managing concurrent worker lifecycles.
For a deep dive into the philosophy behind this approach, see Andy Matuschakβs evergreen notes and the source code of this site. The concept of a βsecond brainβ was also covered by Tiago Forteβs Building a Second Brain and in this explainer video:
And a short thread worth reading:
All Notes & Ideas
π² Evergreen Notes(3)
How Breath's private notes work and how to protect them with HTTP Basic Auth on Cloudflare Pages
A good abstraction encapsulates difficult details behind a simple, intuitive surface.
Entropy is the default state of any evolving codebase. Keeping systems simple requires deliberate pruning.
πΏ Budding Ideas(1)
Common leak patterns in Go concurrency and how to audit them with tooling.
π± Seedling Thoughts(1)
Precise naming aligns code with mental models and eliminates the need for redundant comments.