Building a personal knowledge base in public

Why the site separates dated working notes from evergreen technical topics.

Building a personal knowledge base in public

I want this site to do two jobs without mixing their rhythms: a blog can capture what I am thinking today, while a knowledge base can preserve what remains useful after the context changes.

Two speeds of writing

The blog is chronological. It is allowed to contain questions, partial results, and the trail behind an experiment. The knowledge base is topical. It should be edited when an idea becomes clear enough to reuse.

That distinction keeps the archive honest: unfinished thinking does not need to pretend to be a manual, and a useful concept does not disappear in a timeline.

The maintenance rule

Every new note should answer one of three questions:

1. What did I learn?
2. Where does it connect to an existing topic?
3. What should someone try next?

If a note answers those questions, it earns a place here. If it does not, it can stay private until the next revision.