cheers @bepolymathe - one of the main (mental) blockers I always have is "where should this note belong?" or "when i want to find this note again, where will i look?" - for example, imagine I have a task "write device driver for ABC-123", which is required for a specific project. Should that note go in the project notebook? should it go in my "Linux Dev" notebook? should it go in my device specific notebook "ABC-123" - it equally applies to all three of them, and I will make use of that info in all three places.
Gut instinct says to file it in the project notebook, as thats where it will immediately be used, and then link it to other projects - this could work of course, however it is overhead.
On the other hand, if I just write that note, without worrying about catgorization and instead tag it with "Linux Dev", "ABC-123", and "Project X" - and i have "dynamic notebooks" that are defined as "all notes with tag 'Linux Dev'" or "all notes with tag 'Linux Dev' AND 'ABC-123'" - any time i write a new note and tag it, it will go into the respective notebooks - I then don't have to worry about catgorization - if i use that note in the future in a completely new place, i can add a tag and just be on my way
For me "dynamic notebooks" or "smart notebooks" are like Smart Playlists is iTunes, you build them based on a collection of metadata - all my 5-star songs for example. or 5-star AND metal
this method of working increases the chances of finding the information you want/need when you need it.
I will also add that this is talking about a note as being part of a journal, and so it makes sense for it to be in the flow/timeline of multiple projects. There is a related case, where you want to reuse notes in the sense of a howto
- You want to link in a previous guide and use it as is - for example imagine in one project you write a guide on setting up an Ubuntu VM in a specific way, and you want to reuse it for another project
- you want to link to a previous guide and use it in the latest version, for example you might update the guide on building an Ubuntu VM for the latest virtual box or Ubuntu version
these two use cases are related, case #2 would be covered, but not #1 (which would require linking to a specific version of a note, or creating a fork - and you can do this by duplicating a note)
