Publish knowledge that grows, not just posts.
The dominant model for publishing knowledge online has not changed much since the early 2000s: write something, polish it, publish it, move on.
Notes that improve instead of decaying.
Most engineering notes are written once and forgotten. You capture something in a debugging session, paste it somewhere, and find it two years later with no context for why it mattered.
Organize notes by action, not topic.
Organizing notes by topic sounds logical until you have notes on PostgreSQL in five different folders and cannot find the one that matters for today’s problem.
Build a developer knowledge graph.
Developers do not usually suffer from a lack of information. We suffer from too much of it.
Notes are storage. A second brain is computation.
Information overload is less about sheer volume than about unresolved inputs. Modern knowledge work leaves a trail of tabs, chat threads, docs, highlights, snippets, transcripts, screenshots, and half-written notes.
PKM tools, methods, and self-hosted wikis compared.
Personal knowledge management spans Obsidian, Logseq, DokuWiki, Zettelkasten, and PARA — the right choice depends on whether you want a local note graph, a self-hosted wiki, or an outliner-driven workflow.
