Howdy, Stranger!
Categories
- 3K All Categories
- 152 Research & Reading
- 692 The Zettelkasten Method
- 7 Knowledge Work
- 99 Writing
- 464 Software & Gadgets
- 154 Workflows
- 729 The Archive
- 15 Plug-In Showcase
- 88 Resolved Issues
- 225 Projects Logs and Journals
- 83 Project: Zettelkasten.de
- 53 Critique my Zettel
- 171 Random
- 373 Introduce Yourselves!
Comments
I'll say I do sometimes find it useful to capture how a train of thought originally unfolded (i.e. not necessarily strictly sequentially), even if some of the underlying connections are still obscure in the moment. But if and when I do want to work in that mode, I can use an ad hoc meta-note (I'll avoid the term 'structure zettel' because I'm not sure you don't have some aspects in mind when you use that term that I might not be seeing) without having to make it a fundamental organizing principle of my box as a whole.
Doesn't that just take you back to the habit of sorting ideas into a (maybe slightly looser version of a) preconceived hierarchy of categories that the Zettelkasten was designed to avoid in the first place?
The conclusion I am moving towards is that all of the systems have weaknesses and the complicated question to answer is how to balance them. Hierarchies are cognitively limiting, so we can't have 100% hierarchy. Loose networks do not capture logical structure, so we cannot have 100% loose network links.
What Luhmann's ZK does is allow or encourage hierarchy (depending on implementation) but balance its rigidity with direct links. What @Sascha's ZK does is allow or encourage loose networks but balance its loose structure with hierarchical structure notes.
We cannot _completely _avoid sorting ideas into preconceived hierarchies of categories. Language and our structure of thought requires that. We cannot learn anything new without connecting the new information to existing "preconceived" knowledge. It is a matter of balancing the advantages of preconceived categories with techniques that overcome their disadvantages.
@cobblepot, change "hierarchy" with pattern and we 100% agree. (There are more patterns than hierarchies. I call each type of pattern a structure. A Structure Zettel is aims to deal with a structure as one thought in adherence to the principle of atomicity)
I am a Zettler
Before reading the entire topic, I try to say my opinion about the use of Folgezettel.
I state that I don't use it, so I don't have a real practice about. I've studied something about, and I got the idea that the method could have these potential benefits:
I think these are potential benefits of Folgezettel I could have, if I used it.
But, as stated before, I don't use.
Because Folgezettel has relevant drawbacks for my attitudes.
And I think that other methods can produce similar benefits and are closer to my attitudes.
In my process of learning Folgezettel, I've tried to identify these benefits, and for each of them I've tried to find other ways to obtain them.
I think I've succeeded (I obtain serendipity, good friction, slowness, and so on from other things), so I gave up, beeing uncomfortable for my attitudes, to use not only Folgezettel, but every kind of similar coding in the title of notes.
I'm still convinced that folgezettel could fit the purpose for others. If doesn't work for me, it does not mean that it can't for others, with different attitudes.
Learning about Folgezettel It hasn't been a useless work only because I don't use. This learning helps me to improve my method.
Even this last point (how to learn from things you don't use) it has been a lesson learned
Now I read your opinions :-)