Developers have a knowledge problem. After 5 years in a codebase, you know things that aren't written anywhere: why certain architectural decisions were made, which patterns work in which contexts, what that obscure error message actually means.
Notion databases are good for project management. They're bad for this kind of knowledge.
Why Notion fails for developer knowledge
Notion's model is: everything is a page in a hierarchy. Knowledge is organized by project, team, or category.
The problem: developer knowledge doesn't organize neatly. A note about "idempotent operations" is relevant to API design, database transactions, distributed systems, and caching. Where does it go?
You end up duplicating or losing it.
Why Obsidian works
Obsidian is built around one idea: links over hierarchy. Instead of filing a note in a folder, you link it to related concepts.
idempotent-operations.md
→ [[REST API Design]]
→ [[Database Transactions]]
→ [[Distributed Systems]]
→ [[Cache Invalidation]]
Now "idempotent operations" is discoverable from any of those topics. You don't need to remember where you filed it.
The developer Zettelkasten
Applied to software development:
Concepts: algorithms, patterns, principles (e.g., least-privilege.md, eventual-consistency.md)
Decisions: architectural choices with context (e.g., why-we-chose-postgres-over-mongodb.md)
Failures: post-mortems and lessons learned (e.g., n+1-query-production-outage-2024.md)
Learnings: things that surprised you (e.g., tcp-slow-start-affects-api-latency.md)
Each note is small, named precisely, and linked to related notes. Over time, your vault becomes a queryable map of your technical knowledge.
The workflow
Reading an article or paper:
- Use — paste any article, get atomic notes with wikilinks. Free, no account.↗ Original-Artikel auf dev.to lesenVollständiger Original-ArtikelDen kompletten Beitrag mit allen Details direkt auf dev.to lesen.
SOCIAL SHARE CARD GENERATOR