Notes store answers; systems store relationships

A note might say “Redis cache TTL is 300s.” A knowledge system links that note to [[auth-service]], [[incident-2025-11]], and your runbook on cache invalidation. When any of those contexts change, you follow links instead of searching from scratch.

What a minimal system looks like

  • Plain files — Markdown on disk, versioned with Git, syncable with any tool.
  • Wiki links — [[Note title]] connects ideas without rigid folders.
  • Backlinks — see who references a concept from anywhere in the vault.
  • A graph view — spot clusters, orphans, and missing bridges between topics.
You do not need a complex taxonomy on day one. Start linking the next note you write to one related note—that is already a system.

Why developers feel the pain first

Codebases are graphs: modules import modules, services call services, docs reference tickets. Developers intuitively think in references—but flat note apps hide that structure. Tools like Lunote bring the same linking model to your personal docs without locking files in a proprietary database.

Getting started without a rewrite

Open the folder you already use—Obsidian vault, Typora project, or a docs/ tree. Add wiki links where you would otherwise paste a URL or duplicate a paragraph. Let backlinks reveal which notes deserve a clearer title or a short summary at the top.