Question, evolving ideas, contradictions: how to manage non-truth in a Zettelkasten?
Greetings,
I come to you, specialists and sages of the Zettelkasten, in a quest to understand something I cannot wrap my head around…
I've read How to Take Smart Notes, I've practiced the method successfully for writing fiction, but there is something I cannot yet figure (or maybe need validation to implement?).
How do you manage that which you know you do not know, or do not know enough, or realize you did not know? That is:
- How do you manage questions, which can be ongoing on life? ("How to be a good man in the 21st Century?")
- How do you navigate and evolve forming practices? (Like: the Zettelkasten method, which you hone in through practice, and evolve insight: "this works for me, I should pay attention to that")
- How do you walk back on ideas that do not serve you anymore, or that you realize were false? (like an early 20st Century scientist witnessing the ether being disproved, meaning all theories and constructs pertaining to it become completely irrelevant apart from scientific history)
I guess the underlying issue is "transient" content, which is a little bit at odds with the concept of permanent / evergreen note / Zettel. Now I know a Zettelkasten is personal, that truth is unattainable and everything is potentially transient – please bear with me here 🙂 I also know, in Luhmann's words, that the Zettelkasten is a "septic tank".
And yet. What would be best practices for capturing accruing, unformed ideas and questions, which would free the user by knowing they will not pollute the system down the road if they turn out to be dead ends?
Is it a simple matter of trusting that linking will isolate irrelevant content? Or should you prune links later, remove notes – but potentially destroying the path of thinking that led you to where you are now? Is it a much simpler matter of redirecting the energy of the system simply by altering the geometry of structure notes?
Any insight and especially technical approaches would be hugely appreciated. Thank you!
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
Howdy, Stranger!
Comments
I guess the thing here is that everything is somewhat known as a "truth" based on a thinking and experimenting system that we humans constructed. I don't feel like there's a reason for everything in your Zettelkasten to match the truthiness truth, it just needs to make sense, even if it comes from your own head. It is your personal space for keeping your stuff contained, anyways.
Something I do is always reference the resources that I get the information or inspiration from to write the notes. If the note doesn't contain any reference, then it means it is a personal opinion or idea that I meant to develop further.
I wouldn't use the term "best practice" about Zettel revision since the "best practice" tends to mean personal preference. I have revised notes when that doesn't mean reassigning links. Fixing grammar and improving the wording is a good practice ("good practice" means "this is what I do").
Occasionally, I will relink a note using a new feature in Zettlr that will update Wikilinks if you change the ID of a note--I don't recommend this unless you are simplifying unnecessarily complicated IDs, as long as the note sequence is preserved. But I am tempted to leave things as they are and let moribund threads peter out. That's how Luhmann worked. Some people revise their notes and edit out their prior understanding and struggle--forgetting history can give an overly sunny impression. It can waste time if you end up rehashing ideas abandoned for good reason.
You did give me an idea, though. I am toying with adding a few "terminal notes" for TRUE, FALSE, MAYBE, that I don't update directly (unless I am so inclined) but that other Zettels will link to. By navigating to one of the terminal notes, say, MAYBE, the "Related Files" pane in Zettlr will show (Insidian Obsidian has a similar pane) all the Zettels that link to MAYBE. You can use hashtags for this and search for #maybe, but I find hashtags less useful than Wikilinks. I usually ignore my own hashtags.
GitHub. Erdős #2. Problems worthy of attack / prove their worth by hitting back. -- Piet Hein. Alter ego: Erel Dogg (not the first). CC BY-SA 4.0.
Thank you both for your answers. Doing more research, I found indeed that Luhmann never deleted any notes, which I think makes sense – a past understanding that has been refuted may become again relevant in the future, or serve as an example of a different refutation. I appreciate the idea that we should only clean the wording of Zettels – that's a clear metric, thank you. (Goes contrary to what Andy Matuschak does BTW)
Also appreciate that the presence or absence of a reference means the idea is original or not. That's easy to implement.
However, I remain confused as to how, in a practical way, this would work for a) questions b) accruing insight and c) refutations. How do you go about this?
a) questions: my idea would be to have maybe different structure notes, like yearly, that would reflect an evolving understanding of crucial notions.
b) accruing insight: like questions but on a smaller scale…
c) Refutations – a Zettel could point to a hypothesis: [[192312150928 If the ether exists, then it means this in physics]] and when refuted, that Zettel should point to the most current theory: [[192312150930 The ether has been disproved]].
But in the case of questions and accruing insight, that looks messy and maintenance intensive, which is why my gut tells me there should be a better way.
My fear is to pollute the Zettelkasten with transient content, I guess, or inarticulated thoughts, questions and ideas that get stale. But at the same time, if the Zettelkasten is a "septic tank", shouldn't these things be thrown into it in order to mature?
I'm very curious about a technical approach to make this work without drowing the system.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
One of the aspect I've catched in your post, maybe, is thinking that permanent mean "written on stone".
I've made the same assumption when I first met zettelkasten, and this make difficult to start using the method at first.
How can write "perfect notes" immediately after reading the first article about a new thing? I can't, I don't know enough at this stage about, but I can easily transform the problem in a no-issue abandoning the idea of notes as stones that I can't change or that I must consider always with the same relevance they have at the moment I wrote them.
Permanent doesn't necessary mean immutable content, during my examination of the method in the last year I believe that "permanent" is an unfortunate term.
I prefer the digital garden methaphor, where notes in their life intrinsically grow, can change, can evolve (or even wither, too), just like plant in a garden.
So, the answer of your question, I think, it can be that if your ideas evolve during time, you can evolve you already taken notes. Their content,, how they are written, or their relevance too.
In my implementation evolving, growing, refining notes, discuss them too are maybe half of the effort.
Generating ideas contrasting already taken thoughts is a useful tool in the idea developing toolbox.
Above all, evolving attitude is for me necessary when I don't have an initial full knowledge of a subject, I can start to take notes even when I know very little about. Over time, my knowledge increase, so I can increase the quality of the already taken notes., not only adding new notes.
You can also maintain the history of the idea evolution, for example in a note that contains the evolving train of thought (I sometimes use an outline), or adding dates to the different versions of your thought.
The term "digital graveyard" might be offensive to some, but it has an element of truth: the notion of finality. I think of my Zettelkasten as a combination of garden and graveyard. Here lies idea #23922, contradicted by note #12430958 and the following references [@furd; pp 1111], [@snurd; pp 9], and [@phurd; pp 155-209]. I take a lassiez-faire attitude to my Zettelkasten. It is better to add too much than to add too little.
GitHub. Erdős #2. Problems worthy of attack / prove their worth by hitting back. -- Piet Hein. Alter ego: Erel Dogg (not the first). CC BY-SA 4.0.
Thank you both. Though I am… confused, but I guess I'll have to try things out.
The "permanent" term for note is indeed misleading, but I just realized this means "permanently stored in the system", not "written in a permanent manner". Yet I find there is a difficult balance to strike between the supposedly complete state of a Zettel and the ever-changing nature of understanding and life.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
The terminology of permanent notes is confusing. I disagree with Sönke Ahrens that a Zettel "should be written as if for publication" (Ahrens, 17–18, 43). Only Goethe could have pulled that off. Luhmann wrote telegraphic notes for himself as he got older.
Ahrens, Sönke. 2017. How to take smart notes: one simple technique to boost writing, learning and thinking: for students, academics and nonfiction book writers. North Charleston, SC: CreateSpace.
GitHub. Erdős #2. Problems worthy of attack / prove their worth by hitting back. -- Piet Hein. Alter ego: Erel Dogg (not the first). CC BY-SA 4.0.
There are good comments above. I will add some thoughts even at the risk of repeating some of what was said above.
@KillerWhale said:
One way is to create a question note. See the previous discussion "Do you create question notes?" (April 2020), where, among other good comments, I commented about various note schemas or taxonomies that include a "question" type, including IBIS or issue mapping, which calls question notes "issues". Questions are arguably the most important item type in the IBIS schema.
In a more recent discussion, "Discourse graph and Zettelkasten" (February 2023), I learned that computer scientist Joel Chan recently popularized a similar discourse schema (QCE) that has a question note type too. In 2022, Chan wrote a web page titled "People naturally try to enact typed distinctions in their notes". A question note type seems to be a natural "typed distinction" to make when you start wondering about how to manage questions.
(By the way, I find Jeff Conklin's list of question types to be helpful too. I listed them in the last paragraph of this comment in the aforementioned forum discussion.)
Like anything else, I record new ideas about my note system (and related practices) in the note system itself. But I keep a separate longer document, like what Cal Newport calls a "root document", where I try to document how my note system and productivity system is supposed to work. It is like how software documentation documents how a software system works, but it's for my personal knowledge system. But I emphasize "how it is supposed to work" because it can be hard to keep the document up to date, and it can be hard to follow the principles consistently. I also have to struggle to keep the document simple, because I have a tendency to overthink/overengineer it.
If I experienced the kind of confusion that @KillerWhale expressed in this discussion, I would note it as a question in my note system and/or as an action item about needing to improve my system. Confusion about a system is generally a symptom that my big-picture vision of the system needs to improve (original source: Enterprise Corp. Ltd. 1987).
This question was previously discussed to some extent in "Processing research that's based on shaky assumptions?" (May 2021). I still agree with my comments in that discussion, which you could read as if they were a response to your question. Now I would say that what I would do with false or irrelevant information depends on how much it is integrated with other notes in the note system. If it's not well integrated, I would probably just remove it. If it's well integrated, I would need to note how it's wrong and make any other needed adjustments to the rest of the note system.
I have never used the term "permanent notes". I find it more useful to have a schema of the kind that I described in my answer to the first question above. Such a schema can help you track discourse relations like questions/issues, claims/answers/positions, reasons/arguments, etc.
An idea that is generally related to the subject of this discussion is the property of epistemic status (see also the Urban Dictionary definition!) that some bloggers apply to their blog posts to warn people about how sure they are about their claims. I haven't schematized this in my note system as a property (i.e. as a tag), but at times I write informally about the epistemic status of a note.
Thank you all. I had seen those discussions but I had not taken a definite practice out of them. Time to revisit them in (profound) depth. Appreciate all the links!
I find very interesting though that such a foundational (and important) question for a knowledge management / accruing method has no definite and ready answer, as the linked discussions show. We can clearly define a Zettel, and clearly build them when in-depth research has been made. In those other areas, there is no consensual answer. I am starting to wonder if there might be a flaw in our understanding / research of the whole thing.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
@KillerWhale said:
I doubt that there is even a consensual definition of a digital Zettel if we consider a large enough population of researchers, because using the term Zettel to refer to software is metaphorical, and people can and do stretch the metaphor in various ways. The proprietors of this website have their definition of a digital Zettel, tied to their software, but one could define it differently in other software systems.
When you say "there might be a flaw in our understanding", one has to ask: whose understanding? These issues are well discussed in the published academic literature on argument technology, epistemology, and methodology. There are answers. But there are always new generations of knowledge workers entering schools or workplaces who need to figure out how to solve knowledge-organization problems, and they sometimes reinvent the wheel, as when Joel Chan in the last couple of years reinvented IBIS and called it QCE or discourse graph.
@KillerWhale, I noticed that recently in a comment in another discussion you revealed that you recorded a video about your fiction writing. I watched the video, and it's great. What surprised me is that you already consciously use questions in your writing process, as shown in this diagram at 2:32 in your video. Some of your questions can also be seen at 11:14 and at 13:28, where you mention federating questions into higher-level questions. I wondered: what is missing from your writing process as described in that video that would lead you to the kind of confusion that you described above?
In the diagram at 2:32 in your video, you show a question as leading to a hypothesis/answer. The line between the question and answer is displayed as dashed/broken, not as a solid line. To me, your description in the video suggests at least two implicit principles:
I don't know if those two principles accurately reflect the way you use your note system. Let's pretend that they do, and let's imagine a slight change of those principles that would make your system more like IBIS, which I mentioned above:
These thoughts lead me to want to give another, different answer to your question:
Following the two revised principles above, "walking back" may not be the best metaphor here. "Walking back" is more congruent with the principle that a question has only one answer that replaces the question when it is answered, so if the answer turns out to be wrong then you have to "walk back" and restore the question. But if you change that principle so that a question has multiple competing hypotheses/answers, and all questions and hypotheses/answers are generally retained in the note system (i.e., in the "issue map" or "discourse graph" or whatever term you use), then you need a different metaphor that expresses that you are merely adding a new hypothesis/answer and/or changing the rankings of hypotheses/answers in some way. And this is merely the routine forward motion of working with a note system or knowledge base.
You might object to this with what you said above:
One way to make the process less maintenance-intensive is to use fewer structure notes (which, in the video, you call "maps of content" or MOCs) and instead rely more on an IBIS-like schema of note types and link types that is automatically parsed by software. For example, if you are still using Obsidian (like in your video), you can do this using the Breadcrumbs plugin to specify link types and their relations; the Breadcrumbs sidebar will show you the notes that are related to any given note organized by kind of relation: for example, for an answer note it will show the parent question, the sibling answers, the child arguments. You can also color-code notes in graph view by note type so that you can see the logical (schematic) relations between notes in the graph (if you have a simple schema of one link type per note type). This kind of software configuration can allow you to rely less on structure notes (and spend less time restructuring structure notes) and rely instead on automatically generated views of the note system structure. (By the way, there is also specialized software that works like this in the field of government intelligence analysis.3)
I will end with a relevant quote from an early 20th-century Zettelkasten user:
Cited sources
Discussions of the role of multiple competing/rival hypotheses in inquiry can be found in, for example: Chamberlin 1890, Webb 1926, Campbell & Stanley 1963/1966, Campbell 1988, Walton 1998, Rindskopf 2000, Flower et al. 2000, Elliott & Brook 2007, Walton 2011, Walton 2013, Schneider et al. 2013, Karvetski et al. 2013, van Eemeren et al. 2014, Toniolo et al. 2015, Murukannaiah et al. 2015. ↩︎
See, for example, the explanation of epistemic metadata in Horsch & Schembera 2022 (paper, slides). ↩︎
For example: Karvetski et al. 2013, Murukannaiah et al. 2015, Toniolo et al. 2015. ↩︎
@Andy , thank you so very much for that extremely insightful post – I really appreciate the time and thought you put into it and into sourcing everything. I also appreciate you taking the time to watch the video!
Your naming of questions and a continuum of hypothesis as metadata really resonates with me and it helps me a lot to grasp with the problem. What I deeply appreciate with the Zettelkasten method is the way it "remembers" your path of emergence through linking, and how you can retrace that, put yourself back into that space, eliciting more remembrance and understanding that the notes themselves (which is why I think putting AI into automatic linking is absurd). This, however, clashes with the Matuschak evergreen notes and, to some extent, makes the "permanent" notes a la Ahrens confusing.
I now think these two approaches are at odds with retracing your steps, so to speak.
Why do I not have a problem with questions / hypothesis in writing fiction while I have one with the Zettelkasten? Because my writing notes are project notes; they are (comparatively) short-lived to my regular archive. More importantly, they are completely disposable. In Ahrens parlance, they are not permanent; they help me narrow down the project at hand, and are very often thrown away when the book is done. (Sometimes I extract value out of them, but they have no lasting power.)
So I have no issue consigning questions in there because these questions are short-lived: they will know a definite answer (through the book being written and published), and if the answer is wrong (it happens…), there's no revisiting them anyway, and I will have moved beyond them anyway. They are project-based questions.
Compared to this, Zettelkasten questions seem to me quite open-ended are they are potentially life-long objects of study, which I think needs a more careful approach?
However, this continuum approach really speaks to me, thank you for that. I am starting to see a blurring of the lines between Zettelkasten and journaling, and that's an approach I have to explore — possibly with Hailey René's book, Soul Cards, which I just received – I'm wary of the marketing approach, but curious of the content. I hope this line of thought matures into something usable.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
Then, leave the older, obsolete notes in. I don't use the term "evergreen." I have "autumnal notes" in my digital graveyard. Luhmann's Folgezettel--a term he never used--handles contradictions. My Zettel IDs combine an initial keyword of up to five characters, Folgezettel, and timestamps in my Zettelkasten. If a note continues a thought, I increment the last alphanumeric character of the Folgezettel portion. If a note contradicts, revises, or comments on an aspect of a note, I append a letter or a number to the Folgezettel portion--letters and numbers alternate. I use another keyword if the new note neither continues, comments, or contradicts some prior note. The timestamp is always the timestamp.
I will only revise a note to correct grammar or to improve the wording, but not to break the chain. As the comedian Jerry Seinfeld says, "Don't break the chain."
GitHub. Erdős #2. Problems worthy of attack / prove their worth by hitting back. -- Piet Hein. Alter ego: Erel Dogg (not the first). CC BY-SA 4.0.
I'm glad @ZettelDistraction mentioned his Zettel IDs, because it gives me an opportunity to point to a useful principle: It is not so important where you put your epistemic metadata. There is some epistemic metadata in ZettelDistraction's Zettel IDs. When I described metadata above, I was thinking of a header such as YAML frontmatter. (ZettelDistraction puts his Zettel ID in the filename and in YAML frontmatter, if I'm not mistaken.) Any format would be fine; the common principle is that there is an established schema that is consistently encoded so that not only can your future self clearly follow what you were thinking, but the metadata could even be programmatically converted into some other format or even—if you really wanted to go crazy—interpreted by some kind of semantic reasoner software.
That's right.
That's precisely correct. The point of the Folgezettel is to preserve the sequence. You read the Folgezettel portion of the ID from right to left. It tells you something about the relation of one note to the next at a glance. Annotated links can do this (a good idea) but sometimes you want to see the metadata at a glance in the file pane.
I should mention another case: when I add a Zettel with the same keyword, which isn't a continuation or comment on another Zettel. Then, I increment a section number after the keyword. For example
LUCK.2c1a.0.24.0102 might have the successor
LUCK.3.0.24.0102
This is another section under "LUCK."
How do you read this? For the record, LUCK.2c1a.0.24.0102 is a comment on LUCK.2c1.0.TIMESTAMP1, which is a comment on LUCK.2c.0.TIMESTAMP2, which is the continuation of LUCK.2b.0.TIMESTAMP3, which is a continuation of LUCK.2a.0.TIMESTAMP4, which comments on LUCK.2.0.TIMESTAMP5.
[There are other possibilities with this ID system, but I will spare you.]
The ID system went through several changes. You could avoid some of this complexity by opening files and looking at links. But I have a way of seeing the immediate predecessors of any note with this system.
GitHub. Erdős #2. Problems worthy of attack / prove their worth by hitting back. -- Piet Hein. Alter ego: Erel Dogg (not the first). CC BY-SA 4.0.
Some musings perhaps better captured in a Diary.
Luhmann had lots of "dead ends" in his Kasten; research topics that he had moved on from or were no longer relevant; sort of becomes a record of what you were thinking about in the past. Leaving old ideas in may show evolution of thought. Or could just delete them.
Thank you very much for all your input. You've sure given me a whole lot to think about, and I will be adhering to @ZettelDistraction 's rule of "only improved wording" on Zettels. I will try and introduce questions slowly in the system as I accept, through practice, that it's a septic tank and dead ends are accepted (as per @JasperMcFly ).
My intent is to centralize all my explorations in the same system:
I hope to be able to have all this percolate together. A diary entry could lend itself to a Zettel, only to find that I already have written one on a given idea. Sometimes we need to re-learn the same life lessons (I know I do); I hope that this flow of diary → Zettel will improve retention in all areas of life. As I finally learn some things and make good Zettels out of them, hopefully I will not need to write again and again on the same subjects to rediscover good practices and ideas in my writing workflow.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
Following a discussion in Reddit these days, I noticed that the problem of evolving ideas and contradictions is more complex than I thought at first.
I'm studying again the problem from the start, trying to reflecting more about.
In my model I need to find the right balance between two requirements:
According to the first requirement, when I use the system, I need to have the picture of "only the ideas and principles that are good today".
According to the second, in another moment I need to have in the picture even the outdated and conflicting ideas that I've left behind during time.
Making a practical example, developing my workflow about notetaking, it's more important that I've a clear and clean vision of my actual (so, hopefully the best until today) workflow and its actual principles, rather than having a big relevance for techniques and ideas used and abandoned a year ago.
So, in this case I need ways for explicitly deprecate abandoned ideas. In the context of my actual workflow, the note with title "It's better to...1" related to a principle A valid today need to appear, while the note "It's better to...2" related to a conflicting principle with A need to disappear.
I'm working on how to obtain this.
As the first idea I think that the simplest and most effective way is having a "my workflow note" that contains the list of link to principles and techniques I use today. When my ideas about notetaking change, I change the composition of this note, rather than changing, erasing or messing with the impacted principle notes.
I'm realizing, thinking about this idea, that the expression of importance, relevance and impact of a note moves from the note itself to the "chains" which I form with that note.
If I have two conflicting notes with two "strong" titles, it's not the title of the notes that makes one of them survive. Survive the note that I use for making "active chains" in other notes.
After writing this mess, I restart re-reading this thread again :-)
This is what I don't truly get. I have no interest in tracking back the evolution of my thinking. I capture past fallacies that I don't want to commit again. But they are not personal or biographic.
Example: For some time, my thinking about the empirical nature of experiments in nutrition science was wrong. I improved it. I created a note about the flawed conceptualisation of experimentation in nutrition science and integrated it in both my areas of philosophy of science and nutrition. That's it. I have little interest in the iteration that I needed to take to come to my improved thinking.
I have the same inclination towards journaling and personal memories. The only pictures I keep are pictures of my family, especially from my daughter. The reasons are 100 % sentimental. In a decade or two, the photo collection of my daughter is a tool for me to sit down and have either an emotional moment of my own or with my wife or daughter. This is why I collect the photos.
In contrast, I don't see any point in keeping tokens of memories like journals etc. that are basically solved. I don't need to re-read my introspection from 2013 about materialism and resentment that can build up if you are limited by lack or resources in your ambitions. I thought about it, implemented the conclusions in my life and moved on. My diary from that time went into the trash bin.
The same is true for the knowledge in my Zettelkasten. If something is wrong, I either make something correct out of it (e.g. I turn a faulty idea into a correct idea about the committed fallacy) or I cut it out (remove the note, remove the links, change the link context etc.)
To me, the energy invested into revisiting the personal history of ideas seems to be like a waste of time.
I am not 100 % confident in this approach, so I don't make a universal claim about the correctness of this approach (yet). It might stem from a personal inclination of moving on after a problem is solved and more just an expression of my character than a correct deduction.
I am a Zettler
I wonder about this stuff as well:
I'm more inclined to be a hoarder and collector and having a trail of "the truth" to span all my life's thinking. I'm not sure where that came from. It's maybe the naive believe that a comprehensive collection of everything I ever thought, a record of the whole objective truth, can be relied on better than anything else.
As if a complete record in itself produces any insights.
None of the practical insights I ever had spawned from meticulous records.
Even with version control systems for software projects, the practical use of 10 years worth of changes is minimal. You need to go back in time occasionally to see when you introduced a bug and compare changes. But in most cases you can't go back as much as 10 years and expect the old code to even compile. It's like having a complete history of everything, but nothing that's older than a year is intelligible.
So none of my experience backs up that a complete history is super useful, yet the inclination is still there. It's a call in the back of my mind that's a bit more muted these days, but that doesn't go away. Maybe one could make a more compelling argument, or come up with a guide that encourages people to be a bit more bold, to not distrust their progress so much that they want to have a backup of everything that happened in their time to potentially revise where they currently are. Just spitballing here, I can imagine that the wish to collect all pieces of the progress, every deleted character, ever mistyped word if need be, just in case, stems from uncertainty.
Author at Zettelkasten.de • https://christiantietze.de/
@Sascha said:
Speaking for myself, nothing in my current note system is older than around 2010, which for me is already well into adulthood. So everything in it is my mature thinking. It does not contain material from my teenage years, nor even young adulthood. I too would abandon large quantities of content if I thought that it were no longer relevant. I would even completely start again from zero if I thought that was most helpful. But what I have now is still relevant to me, at least much of it, and I always want to remain open to surprising insights from the past.
@ctietze said:
Or it could just be a way of appreciating your life. Your little life, or mine, is not so lengthy that it's impossible to remember all of it in broad outline. Life is so short, why not why remember as much as you can, good and bad, and see what you can continue to learn from it?
Martin Buber wrote in "Productivity and existence" (1914):
To distinguish from then on what is actually won from what is merely possible: that is what I want—to know what is actually won and to have some understanding of how it was won.
My thoughts on this are a bit different. I feel there is value in understanding how we reached the point at which we now are in life; retaining some vestiges of the journey is necessary in that regard. And sharing the journey helps instruct or mentor others. I find myself in that position with many young engineers - they always appreciate the embarrassing stories of their "senior" as it illustrates that we are all on a similar journey. The lessons are better understood within their context. There is no shame in making mistakes or discovering truths about ourselves from experience.
You will find that when you are 70+, your memory is not as good as it once was, and having a few recall aids is essential. I was writing about some memories of my oldest (47-year-old) daughter this past week and was startled by how difficult it was to recall details of her life. I was thankful for many albums of photographs.
I have mentioned before that one of the primary purposes of my ZK is to record memories of what I have learned and then weave those into a story for my children and grandchildren. When writing sections of the story, it is helpful to review those memories from when I was much younger and then reflect on my path in life and what I learned along the way. The lessons learned and how they fit into the larger arc of my life were not always fully appreciated at the time.
@GeoEng51: Well said, thank you. I would add: You may remember that I once said before, quoting David Wildon Carr, that "we are unfinished". A Zettelkasten can be not only for recording the finished, but recording how we are unfinished at every stage of our lives, including right now. That was a big part of @KillerWhale's original post above: "How do you manage questions, which can be ongoing on life?" "How do you navigate and evolve forming practices?" How do you continue being unfinished?
I think it's a good way for managing the issue, and I think I'll tend to follow it at the end.
Remain for me only one issue.
I suppose that you don't remove obsolete stuff from your zettelkasten, simply you "forget" that notes in your future activities.
Doing this, do you experience, in your system, the issue of outdated notes/ideas that resurface when you try to integrate new things in your Zettelkasten? How do you can hold obsolete things "on the seabed" of your Zettelkasten, avoiding that become noise during your activities of editing/searching/consulting?
I'm convincing myself that the most effective method for separating "active stuff" from the "obsolete stuff" is maintaining active stuff organically linked on their own, making "active structures" at first and following them later when there is need to return to notes.
An active structure could be a structure note, a sequence of links, what I call a "train of thought" note, or whatever similar artifact.
I am not inclined to trace my thinking over time either – I'd rather retain the most finished level of understanding that I have, along with the reasoning that came to it and detailed explanations of why some avenues turned out to be dead ends (so that I may revisit that thinking if it turns out there was merit in it).
I think I get where people are coming from with this though: some concepts build over time, through accretion. For instance, through experimenting with a vague concept or rough idea, you will quickly see if it makes sense or not, but most importantly, it will reveal itself in the process.
It seems quite a hassle to manufacture Zettels for that in my opinion (write for your future self, assign ID, links, tags), but maybe I'm too "bureaucratic" about it. So far I have "somewhat-zettels" which are rough ideas and logs of things that occurred to me and that I'm toying with. Conclusions get drawn out of this as Zettels, but I can't help but think there's a more efficient way to do this in a system.
I guess the end goal is: not to lose the agility of thinking and capture those scraps of ideas in a way that allows them to "snowball" into something usable (whether that something is: that was a great insight, or: nope, that's stupid, do not revisit – two equally valid results in my book). Despite the Zettelkasten method's great agility, I am failing to find it even agile enough for that use case of very raw emergence (when you actually don't really yet know what it is you're dealing with). But I may be do it wrong.
@Andy , you've encapsulated it exactly, thank you.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
It is a hassle, though I have scraps of paper for anything that isn't worth the hassle, not to mention nothing. By definition, I tell myself, an idea that cannot make it past the speed bump has run out of gas--if you believe in the self-deception of personal narrative. I have tried to automate some of the hassle away. But your point remains.
The GPT doesn't know that we are unfinished--a defect of the Zettel Critique Assistant GPT I have been laboring over. Somehow, I have to get that into its thick electronic skull. It dislikes personal journaling, reflection, transactions, and BOMs (bills of materials), claiming these belong outside a Zettelkasten. But such things can jog the associative memory and be useful when writing engineering reports or thinking about new projects.
Regarding not looking back, always starting from the current state--being "Markovian," has some advantages. This is the economic logic of the sunk cost. That and the opportunity cost of completing everything is lost on the GPT. My work is...unfinished.
GitHub. Erdős #2. Problems worthy of attack / prove their worth by hitting back. -- Piet Hein. Alter ego: Erel Dogg (not the first). CC BY-SA 4.0.
You know, guys, thinking about this, I’m getting a feeling that Roam and its derivatives, with daily notes where you « vomit » bullet point quick jots linked in many different ways were onto something for that use case. Thing is, that methodology is very bad as producing good refined Zettels because it doesn’t go any further than that.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.
@KillerWhale said:
I'm reminded of a discussion from last December, "Current process: CHURN file", where @mediapathic described an ongoing "churn" file where you "vomit" material and work with it in an agile way, and the material is then archived to a weekly note or to stand-alone notes. The "churn" file is edited with any app that has a good outliner interface, not unlike Roam.
oh, these are good points.
@Andy I think this is the way to go. I have several of those files on various ongoing subjects, in the form of a chronological log, but they are not systematized. Embracing this would be a simple way to go.
"A writer should write what he has to say and not speak it." - Ernest Hemingway
PKM: Bear + DEVONthink, tasks: OmniFocus, production: Scrivener / Ableton Live.