Does anyone have any good examples they've seen?
But I don't know how much of the advantage of the Zettelkasten is tied to its being in the physical realm. On the one hand, the more physically rich an experience (of browsing or traversing or entering info for example), the more it will tend to stick in memory. On the other hand one of the things computers are good at is remembering indexes and linking them to other places where that index was mentioned.
I think part of what can make the concept hard to see in practice, is that it's both the Zettelkasten artifact, and your methodology for adding and linking concepts when you're learning
But there was one article standing out: https://www.lesswrong.com/posts/NfdHG6oHBJ8Qxc26s/the-zettel...
It is a wall of text too but the best explanation I've found yet.
Again, I get the concept, but I want to see examples in use.
Regards Zettlekasten itself: the key notion to me is simply capture and reference. Those are the dual-natured heart of the system.
The rest is just mechanics. Important mechanics, in cases, but mechanics all the same.
I learn best by example, personally, and I’ve never seen good examples on this topic myself.
As such, one might wish to instead consider using Hypertext Fiction tools for creating a Zettelkasten, such these two (proprietary software, Mac OS X only, unfortunately):
http://www.eastgate.com/Tinderbox/
http://www.eastgate.com/storyspace/
Note that there exists an EXTREMELY useful plugin for Tinderbox which implements Stretchtext:
https://natematias.com/stretchtext/
Now gimme a combination of what roamresearch.com does with the above, but using the data structure of Hode:
https://github.com/JeffreyBenjaminBrown/hode
But with support for zzstructure like hyperthogonality:
https://github.com/JeffreyBenjaminBrown/digraphs-with-text/i...
And secretly use the patching patches feature of pijul.org in the background so version control actually becomes sanely doable, throw in elastic tab stop support, and maybe an entire kitchensink in which someone let a mixture of ChrysaLisp, SmallTalk, Hazel, Scala 3, /r/nosyntax, Inferno, RINA, GNUnet, & every single proof assistant and theorem prover sit for a tad bit long, and then MAYBE we can stop living in the dark ages of computing.
(Yes I'm bitter)
P.S.: Identity Transclusion ≠ Instance Transclusion
P.P.S.: Birth & Death of Javascript, anyone?
Thanks for the links! I'll check the rest out.
- How many of things I know nothing about should I have. - Don't use this aspect in the thing, use the other. …
And every article is a text wall of minutia addressing questions which are going to be relevant later on, but are just information overload if you try to understand What is it?
But, yeah, when it works it's very nice indeed.
As a backend engineer, I just think: "Man, this data is just sitting in a db somewhere for any engineer to grep." Until we get to a point where everything is just encrypted by default, I just can't see myself trusting software like this.
https://forge.medium.com/the-incredible-creative-power-of-th...
You can probably still find some in use among retired professors who started their careers 60 years ago and already had a system in place when computers started to replace physical organization systems.
Nowadays there are still many people who use digital equivalents.
Tutorial: https://niklas-luhmann-archiv.de/bestand/zettelkasten/inhalt... Zettel 1: https://niklas-luhmann-archiv.de/bestand/zettelkasten/zettel...
At the time I used my own translation (based on the text in Short Cuts published by Zweitausendeins), but I see somebody else has now translated (most of) it here: https://takingnotenow.blogspot.com/2007/12/luhmann-on-learni...