Building a Personal Knowledge System (That You Will Actually Use)

Second brain content is everywhere; functioning second brains are rare. Engineers abandon PKM when capture takes longer than the insight. The goal is retrieval under stress—during incidents, interviews, and design reviews.

Principles

Capture in 30 seconds or it will not happen
One inbox — do not choose a folder while the idea is hot
Link beats folders — tags + backlinks > deep hierarchy
Expire aggressively — stale notes erode trust

Minimum viable structure

inbox/           → unprocessed (weekly zero)
projects/        → active work context
permanent/       → distilled concepts (Evergreen)
reference/       → cheatsheets, commands, links

Note types that pay off

Type	Template
Incident	Timeline, root cause, detection gap, action items
ADR-lite	Decision, options, why, revisit date
Snippet	Command + when to use + failure mode
Book chunk	3 bullets you will apply, not summary

Weekly review (20 min)

Empty inbox to ≤5 items
Promote one note to permanent (rewrite in your words)
Archive completed project notes
Delete anything you would not search for

Integrate with work tools

Link PRs and postmortems from permanent notes
Paste verification commands in snippets—future you is tired
Use AI to rephrase your notes, not replace your thinking

Common failures

Perfect taxonomy before first 50 notes
Copy-paste documentation instead of personal insight
No search habit — if you never search, the system is decoration

Outcome

After 90 days, you should answer: “How did we fix OAuth token refresh last time?” in under two minutes. That is the bar—not aesthetic dashboards.