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.…