Tools: Zettlr for notes. user?weird_tentacles explained the concept of zellelkasten. These are synced to a cloud folder so I have access to them on the move.
Blog: Compiling notes into 'new' knowledge is challenging and interesting. I try to keep on doing what I did in postgrad research.
Zettlr is underrated. When you're compiling notes into something new - how do you find the right notes to pull together? Do you browse, search, or does the linking do the work?
1. ONE (shared) dump-pile of all new notes. Your 2,600 pile should do fine
2. REGULAR 'cleaning' of the new notes: a) Each note gets one or many tags (#urban-decay #gaming #assets) b) Each note is trimmed down to its essence, ready to be used for reasonable purposes. (e.g further writing)
3. 'cleaned' notes are moved to your golden store, ready to be found by searching (search "#urban-decay")
You have 1. You need 2. It's slightly work-y, but interesting and ... fun. Rediscovering and polishing forgotten dust-rubies.
That's a solid workflow. The "cleaning" step is where most people fall off though - how long does it take you to process a batch, and how often do you actually sit down to do it?
plain files in a git repo, one directory per topic, markdown. search is just grep. the friction of organizing is basically zero which means I actually do it. been doing this for ~6 years, it's messy but findable.
Tools: Zettlr for notes. user?weird_tentacles explained the concept of zellelkasten. These are synced to a cloud folder so I have access to them on the move.
Blog: Compiling notes into 'new' knowledge is challenging and interesting. I try to keep on doing what I did in postgrad research.
Zettlr is underrated. When you're compiling notes into something new - how do you find the right notes to pull together? Do you browse, search, or does the linking do the work?
The core idea of Zettelkasten:
1. ONE (shared) dump-pile of all new notes. Your 2,600 pile should do fine
2. REGULAR 'cleaning' of the new notes: a) Each note gets one or many tags (#urban-decay #gaming #assets) b) Each note is trimmed down to its essence, ready to be used for reasonable purposes. (e.g further writing)
3. 'cleaned' notes are moved to your golden store, ready to be found by searching (search "#urban-decay")
You have 1. You need 2. It's slightly work-y, but interesting and ... fun. Rediscovering and polishing forgotten dust-rubies.
That's a solid workflow. The "cleaning" step is where most people fall off though - how long does it take you to process a batch, and how often do you actually sit down to do it?
Google Keep CherryTree - which is much nicer than the web site portrays https://www.giuspen.net/cherrytree/
CherryTree looks interesting - hierarchical nodes. Do you split notes between Keep and CherryTree by type, or is there a different logic?
plain files in a git repo, one directory per topic, markdown. search is just grep. the friction of organizing is basically zero which means I actually do it. been doing this for ~6 years, it's messy but findable.
The "low friction = actually use it" insight is real. When grep fails you - topic you don't remember the exact words for - what's the fallback?
LogSeq, with the "brain" shared across devices using Koofr over webdav
I keep all that stuff on a Wiki that I run in my house.
Self-hosted wiki - what software? And do you access it on mobile when you're out, or is it strictly home network?
I'm lazy, so I use Google Keep and will probably regret it someday.
"Will probably regret it someday" - what's the thing you're most worried about losing?
Notion — good for linking related notes
Does the linking actually pay off when you need to find something, or do you mostly just search?
in md files in the file system.
Do you organize into folders, or just dump everything flat and rely on search?
...sending myself an email
Email as inbox - do you ever actually process it, or does it just pile up with everything else?