I found PARA to be a good solution for note taking its quite flexible and I still use it but with some modifications. The hardest part for me was adapting it

I found PARA to be a good solution for note taking its quite flexible and I still use it but with some modifications. The hardest part for me was adapting it to programming and my ADHD brain and I still have some things I need to solve! it stands for projects, areas, resources and archive. areas can be further divided or thought of as "areas of responsibility" and "areas of interest" Resources can include references eg frequently used bits of code, I have mine setup similar to zellelkasten ie they're all shoved in one folder and searchable and wikilink'd up. I tried using areas and project notes but it didn't work so instead I reference the project in the zettle. (I use obsidian) The idea is to keep the structure everywhere so you use the right tool for the document you're working on. Your meant to migrate content from top to bottom - if you make a project note for SQL query to get all the users favourites for a project while it's happening you can leave it there. When the project ends you're meant to review the notes and move them to archive resources or areas of they'd work there. I can't be relied on to do this! There's an alternative version called GAPRA by carl pullein which I feel works better. You have values which align to goals which align to areas, projects all relate to areas and resources relate to all of the above and then you archive again! Two videos on GAPRA https://youtu.be/EmB15Uzzbjw?si=hB2qzutTRCJUpN-U https://youtu.be/EmB15Uzzbjw?si=hB2qzutTRCJUpN-U https://youtu.be/D4b5zHGw2nU?si=VanwWOrzC2sAeZ6E https://youtu.be/D4b5zHGw2nU?si=VanwWOrzC2sAeZ6E