A tour to my Zettelkasten note clusters
lmy.medium.com
lmy.medium.com
Compared to markdown, our non-Emacs org options are few but here are others I know about:
https://flathabits.com (I author this one too)
Karl Voit also has a great effort going to advocate org outside of Emacs and documents some of the tools at https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool...
edit: formatting
See also org-roam (https://www.orgroam.com/) - an emacs-native bidirectional linking PKM solution.
LogSeq also has experimental Android support: https://github.com/logseq/logseq/releases/tag/0.5.8
Which of those downloads is an Android app? I didn't see an APK, which is usually how they come.
Edit: Nevermind. I see they link to the nightly release where a working version can be obtained[0]. Running it now.
However, the structured organization of a large collection of notes (think thousands to tens of thousands of notecards in boxes..) as well as the finding connections between seemingly unrelated notes doesn't seem to be a solved problem. Does anyone know of any solutions in this space? Zettelkasten (per my understanding) seems to make this manual on part of the note-taker, but (1) this is super time consuming and (2) very hard to keep track of all the note cards as the collection grows over time.
Basically it generates an automated graph of relations between your notes and tries to find which "ideas" group them.
I'll probably post the Show HN soon once I make it public!
I am just now learning about it from the book How to Take Smart Notes, so I could be off, but that's part of the idea. With that said, I think what you suggest could possibly be a cool supplement or replacement.
If I have a conversation with X and discover they're an expert about Y, learning fact Z, I like to record Z as a file, and link it to both X and Y. That forces me to keep X and Y as entities in the graph. Which, if I care about them, is worth doing.
The real beauty of making those connections is the act of classifying something can cause you to explicitly recognize what concepts it is related to, and formulate precisely what the connection is.
The real pain point is knowing what your future self will wish your past self kept a file on. Some ideas (generally more social science-related ones, but also something like a bug involving the interaction of a lot of disparate technologies) are so cross-cutting that I'd need to make five parent concepts to file them "completely", and often then I'd like to file those parent concepts further. I generally don't.
I tried to square this circle once by writing Hode[1], which permits encoding certain data as relevant to me, and then filter my view accordingly when I wanted. But the encoding process (i.e. the user experience when adding data to one's knowledge base) was so hard that I gave up.
The flow is: 1. Read something and take notes 2. Review and distill your notes into key ideas 3. Create cards in your zettelkasten linking these ideas with other ideas already in your zettelkasten
When you are writing and get stuck, refer to the topic in your zettelkasten and follow the flow of ideas.
There are often tips for creating habit to write down things „at the end of the day“ or such. But can anyone describe some habits when to consume this stuff? I‘d be interested. Thx.
- Notes are not "write-only": progressively summarize and tree-shake your notes each time you iterate them. You'll leverage your excitement instead of forcing discipline.
- Ideally, notes are organized by project, not by category. It can be a catalyst for action and reviews.
- Only store things that surprise you, not stuff you already know.
I have a terrible memory for proper nouns but I can generally remember enough context so that a quick backward search in my notes buffer can get me back to the name of the person, team, customer, project, action item etc that I'm looking for. (EG it probably has this tag, or it came up during my meeting with Riley, or last Monday, or during the sprint planning meeting etc). I'm now fast enough at this that I can often start talking and do a search in time to mention the 'thing' by the time I need to refer to it.
I see this model as somewhat different than the more reflective, bi-directional link driven, PKM tools being discussed here. Its a great feeder into such a system (IMO) where more active curation can take place. Plus even if there's never any curation I still have all my todo's, calendaring etc accessible to org's agenda features!
I realized I was almost never editing/updating old notes within the massive append-only file, so now I have a at-most-one-folder-deep directory with somewhat descriptive file names. I still have some append-only type files, mainly in the form of logs. If I can't think of a name for the file, I just name it with today's date and try to put it into the "best" folder. Sometimes it's ambiguous where the best place is, so I usually put these files in the root directory until they make sense to put somewhere else.
The former I also do with org-mode and then use the archiving feature for things I put to DONE.
I oftentimes do the latter, but don’t actually use it that often. In college, I used to summarize text-books, which helped me memorize my learnings. After finishing the book, by chapter summary served as a shorter version of the book. Was quite effective.
Haven’t been successful in replicating this for work, though.
Here if you want more: https://github.com/KasperZutterman/Second-Brain
I have a daily note with "Work" and "Personal" sections. As I go through the day, I add entries in those sections:
- Worked on the [[Foo project]] with [[Joe]]
- Called [[Mom]] and asked her about the [[Meatloaf recipe]]
- Helped [[Jane]] with the [[Qux problem]]
This morning it's very easy to see what I was doing yesterday, and have the context for all the mischief I was up to. Also, when I open "Foo project" and look at its backlinks, I get a timeline of when I'd worked on it, and can see what other things I was working on at the same time. Being able to instantly recreate that context is incredibly valuable, and it's very lightweight for me. I'm not going out of my way to associate "Foo project" with "Joe", but still end up with a graph view that has a lot of notes linking to both of those notes.
I am still working on actually implementing a personal ZK system in Obsidian or on paper (I am looking forward to Scott Scheper's book about Antinets). I manage people and write software for a living, but I don't really write articles or papers (which ZK seems a good fit for). I just finished "How to Take Smart Notes" by Sönke Ahrens, and it has inspired me to take another pass at starting a ZK for the benefits of greater understanding and insight about the variety of topics I read about.
Your way of working sounds wonderful, but I find that I would probably struggle with this part. How are you able to define the end of your day and ensure you have such time marked off? I have tried this but always end up getting sucked into endless other issues/problems/etc and basically passing out at some point, only to wake up the next day to dive right in -- no time to be able to do that sort of retrospective note-munging...
(this is not exclusive to trying to find retrospective time; it applies to things like finding time for food/dinner, blocking out vacation time, or other things, too. work never ends!!)
If you literally can't find time to eat, how will you even be able to function to execute work, let alone anything higher level than that? I know you probably didn't mean literally no time to eat, but my broad point is how can you work hard indefinitely without caring about your physical self reliably?
If your workload will never end, what exactly are you racing against by working as hard as you can every day? Even if you 100% everything for one day, you're guaranteed to have just as much or more the next day, right? What are you gaining by battling every day until you give out?
- [ ] write for 5 minutes
- [ ] check inbox
- [ ] process yesterday
- [ ] schedule today
Are you though? You can just view the text as memories. Same as taking pictures on vacations: "reducing vacations to pictures" sounds like a pretty bad vacation/more like photography work. "Taking pictures of cherished moments and places" sounds like something you might look at again from time to time to fondly remember.
One thing I've personally found about maintaining relationships is how much the fact that someone bothered to write something down about me is meaningful. There's a lot to be said for the clerical role in friendships. Noting someone's birthday, the things they like, their family life, etc. so you can write a card or just drop them a note on their birthday is quite the opposite of "reducing" someone to text in my opinion.
There was discussion on open sourcing it but I'm not holding my breath. Does anyone have any additional info on this?
https://forum.obsidian.md/t/open-sourcing-of-obsidian/1515/1...
To be honest, obsidian not being open source doesn't bother me too much, what is important to me is that I own the data and that it is in a fairly common format so i can move it to another software in 10 years. An open source software with a weird binary format to save the data will probably do more harm in the long term
Plug: I wrote a couple of other scripts and put them on GitHub[1]. If you use Drafts and its "Quick Journaling" action group[2], then `process-notes` will look awfully familiar.
[1] https://github.com/kstrauser/glassknife [2] https://actions.getdrafts.com/g/1Sd
My Obsidian vault, for example, is organized into 2 parts: Ad-hoc notes and an organized zettelkasten. This latter part is a single flat directory with Luhmann-style alphanumeric hierarchical addresses as file names. My first task every day is to split up the previous day's ad-hoc notes and file them in the zettelkasten, which naturally leads to a review of the existing material as I look for the proper place in the sequence.
It's open source, you can selfhost it and you can write your own scripts in JS to really make it your own.
that's not true. They have notebooks and sub-notebooks, which form a tree on the left. To the right of that is a list of notes within that notebook.
The other way to interpret it is just a very poorly planned UI that uses separate panes to list folders and notes that are located in the same hierarchy position. Either way, it’s madness.
In theory, seems like a fine idea. But for, me, in practice, I went back to https://zim-wiki.org (like I pretty much always do.) Not exactly sure what that says about it all, or if it much matters.
One thought though is that Obsidian feels "overloaded," almost as if it wasn't allowed to grow naturally like Zim did?
I also just learned about obsidian for the first time in this thread and it looks pretty impressive, but I do agree that the onboarding is a bit hard and all the plugins while impressive are also a bit overwhelming.
But it's interesting that the core plugins including things like slides which is definitely something that is great to have
The main thing it’s lacking for now is good mobile support, for which folks still use Obsidian mobile…
[1]: https://logseq.com/
To build on the features mentioned there's also:
- A community marketplace for plugins and themes
- Simple customization and extensibility
- A builtin PDF viewer with highlighting and linking
I never understood why anyone would accept linking this sort of system to any third party, no matter how sound their business model, no matter how much trust you may put into the individuals running the company.
The first one is data export. If it's a closed component that still generates value and I can capture that value via export, OSS becomes a tie-breaker between otherwise equivalent tools.
Obsidian is an editor on top of a bunch of markdown files. If they go away, meh. The world is not running out of Markdown text editors. Sync is an add-on feature, so I can sidestep potential privacy concerns there.
A working system always beats waiting for a perfect system.
I used the template (TZK) created by Soren Bjornstad to build it.
The author also has a site called "Grok TiddlyWiki" that helped me tremendously when starting out with TW: https://groktiddlywiki.com/read/
I use TiddlyWiki and love it. Because TW's UI and functionality is based on individual "tiddlers" within the wiki (just like your notes), adding functionality becomes part of the wiki itself -- a fusion I like compared to other plain-text note tools that keep the note-taking and note-storing separate.
So while I'd prefer an open source solution, I'm not in a huge rush, though I am keeping an eye on logseq's evolution.
you could look at vscode pkms plugins like Dendron or Foam.
[0] Foam is a personal knowledge management and sharing system inspired by Roam Research, built on Visual Studio Code and GitHub. https://github.com/foambubble/foam
And now when that's done, I just use a set of markdown files and some kind of Zettelkasten indexing system.
e. also this graph understanding of ZK is misunderstood way to do ZK.
Also: I'm a big fan of customized personal note-taking using open standards. I didn't intend to do this, but somehow over time I ended up rolling my own note-taking approach and "software" (if you can call a shell script that) which is too lightweight to have any kind of visualization piece. If you're interested in reading about that journey, it's found at https://dev.to/scottshipp/an-amazing-note-taking-system-with...
My favorite thing so far has been using Daily Notes to track a morning score and an evening score in the markdown's frontmatter. The score is just a "how I'm feeling" and can encompass really any aspect of my wellbeing. I'm working on a project to parse the data out of my daily notes so I can try to visualize trends. Eventually I want to mash in more data (listening history, Strava activity level, steps from Garmin, etc.) to see what kinds of things have, or seem to have, effects on my well-being.
screenshot of last april: https://share.getcloudapp.com/8Lupb7LX