|
|
|
|
|
by dopu
1633 days ago
|
|
I'm a pretty happy logseq user. I've found that I still need some degree of hierarchy in my notes, as opposed to just having organic, non-hierarchical linking between everything. So I end up making subnotes: [[Topic A/subtopic x]] is a pretty common occurrence in my knowledge database. As an example, all projects I'm currently working on get [[ProjectA/log]] and [[ProjectA/todo]] subnotes. Keeps my TODOs segregated by topic. You could of course do most of these things with typical note-taking apps that rely on the hierarchical file system motif. But the fact that it's up to me to explictly construct my organizational structure in logseq forces me to be more intentional about how I organize my notes. Perhaps the greatest benefit I've found in using logseq is in organizing the scientific literature I'm reading. At any point while writing, linking a paper I've read (the PDF itself, as well as my notes on it) is a few keystrokes away. This linking allows me to externalize the context with which I know a paper. I just need to browse the backlinks to see all the ways in which I've made reference to it over the entire history of my notes. |
|