Anyone actually solved the 'notes for future me' problem?
Hey all, starting a new job in a week (C#/.NET + Angular/TypeScript full stack) and I'm trying to get ahead of a problem I've had forever: retaining domain knowledge across projects/jobs.
I've tried the whole Second Brain / PARA thing in Obsidian more than once. Every time I build a template it just doesn't stick, I end up tweaking it every single time I use it until it's not really a template anymore. And half the time the fatigue hits before I even take a real note, just setting up folders and figuring out "what's this for" burns me out and then I ghost the whole system.
Pretty sure some of this is ADHD related. When I take notes in the moment they're very "right now" focused, whatever's directly in front of me, and not written for future me at all. So a month later I look back and it's just fragments that don't mean anything out of context. Tags are also a mess, I never know what's worth tagging or how specific to get, and I've got no real process for going back and combining/cleaning up notes once they pile up.
Right now my actual workflow is just paper. Task notes while I'm working a ticket, meeting notes on paper during discussions, because that's what actually helps me retain stuff in the moment. But I want something that turns into an actual knowledge base over time, one that fits how my brain works, so later I can search my own notes and look like I know what I'm talking about instead of just remembering everything.
Anyone actually solved this? How do you decide what's worth capturing vs just letting it go? Do you organize by project, by concept, something else? And how do you deal with tagging and cleaning up/merging old notes without that becoming a whole chore itself.