You've debugged the same cryptic PostgreSQL deadlock issue twice. You've googled the same regex syntax four times this month. You've explained your team's deploy process from memory to the third new hire in a row. Somewhere in your browser history, your Notion, your Slack DMs to yourself, and three different GitHub gists lives every answer — you just can't find it when it counts. This is the knowledge management problem nobody talks about in developer circles. Not because it doesn't matter, but because most of the advice out there is built for writers and project managers, not engineers who context-switch between debugging sessions, architecture decisions, and code reviews before lunch. Here's the system I've built that actually works. The Core Problem: Capture Friction Kills Habits Every PKM system fails the same way. You set up a beautiful Notion workspace with nested databases and emoji-coded pages. You use it for two weeks.…