What's happening in your ZK this month, October 2026?
The idea: a general chat about what we're working on currently.
---
Evermore increasing expectations at work leave me with limited time, but especially limited energy, to work on my Zettelkasten. But ironically, I am using what time and energy I have to work on finding a new job. So right now my notes are all about interviewing skills.
Using the tags and flowing inline links I talked about in my previous post, I have a nice structure note now:

I miss the days when I could choose my topics for note taking with more freedom, but I have to get my priorities straight. Having said that, I know it's not healthy to only have a job search to focus on outside of work, so I'm setting aside some time for relaxation and fun too.
"You're allowed to be human" ... one of the best things I've ever read. It was in a psychology book, but I think it's good to hear or read it from any source. I do believe it's something we should remind ourselves of: We're allowed to be human.
---
And how is it going for the rest of you? What's happening in your Zettelkasten this month?
Howdy, Stranger!
Categories
- 3K All Categories
- 153 Research & Reading
- 709 The Zettelkasten Method
- 12 Knowledge Work
- 102 Writing
- 475 Software & Gadgets
- 161 Workflows
- 734 The Archive
- 16 Plug-In Showcase
- 88 Resolved Issues
- 225 Projects Logs and Journals
- 86 Project: Zettelkasten.de
- 53 Critique my Zettel
- 181 Random
- 376 Introduce Yourselves!
Comments
In my backwards way of doing things, I use my Zettelkasten as a lab notebook to track my progress with various projects, such as Pointwise provable equality and the failure of composition.
The story is that one of two constructions described in papers I was relying on for another project was fatally flawed. (It made assumptions violating Gödel's second incompleteness theorem; there is another proof avoiding the second incompleteness theorem.) The construction appeared in two refereed papers, the first published in the Notre Dame Journal of Formal Logic, and the second in The Journal of Symbolic Logic. Because the papers had undergone peer review, I decided to formalize the proof of the flawed construction in the Lean proof assistant and register the formalization in the Palomar Registry.
That detour was good news, since it eliminated one half of the examples I needed to formalize for the original project I was and still am working on.
Zettel GitHub. Zettel Wiki Erdős #2. Problems worthy of attack prove their worth by hitting back. -- Piet Hein. PROBLEMS. Grooks, 1966. CC BY-SA 4.0.
@Will_Jenkins Thanks for keeping this up in October! 💪
@ZettelDistraction I clicked around and didn't understand anything, but the
.leanfile looked really clean. What a languageSince I'm a noob, I can only ask newbie questions: why did you pick the form
def fin0 {n : ℕ} : Fin (n + 1) := ⟨0, Nat.zero_lt_succ n⟩ def fin1 {n : ℕ} : Fin (n + 2) := (fin0 (n := n)).succ def fin2 {n : ℕ} : Fin (n + 3) := (fin1 (n := n)).succ def fin3 {n : ℕ} : Fin (n + 4) := (fin2 (n := n)).succwhere a
fin0and a recursive generalization forfinNwould've been possible? I asked the tutor bots of course whether Lean supports these kinds of statements as a proof assistant (Agda does!) but it sounded like bit of a hassle, even though perfectly possible to write. Theℕtype probably does something like that under the hood and 4 names aren't exactly too much to bear or maintain. Just curious about your proof assistant reasoning there!Last month I upgraded some libraries I wrote for apps, including The Archive, to help with new system features and Swift 6.x programming language additions.
I experimented with a Lisp-1 language embedding, Janet, and it's a really nice language to write.
https://learnxinyminutes.com/janet Short intro
https://janet.guide/xenofunctions/ Longer intro
Culminated in the generation of a Swift package,
swift-janet, to have a portable way to ship Janet scripts in apps and executables:https://github.com/CleanCocoa/swift-janet
For that topic I learned about the term "quasiquote", which also applies to Emacs Lisp, but as a concept didn't enter my Zettelkasten before.
The 'house' department of my Zettelkasten grows slowly as the influx of new information and changes outpaces my capability to carefully create notes. -- Things move too fast for me to catch up! Talking about the same topics over and over is less of an investment, and opposed to Zettelkasten work can be done in a car or at the building site or anywhere, really. So I'm learning more things with my first brain, the old-fashioned way, than with my extended ZK brain
Author at Zettelkasten.de • https://christiantietze.de/
It could have been
def finN {n : ℕ} : (k : ℕ) → Fin (n + k + 1) | 0 => fin0 (n := n) | k + 1 => (finN (n := n) k).succThen the names could have been abbreviations
abbrev fin1 {n : ℕ} : Fin (n + 2) := finN (n := n) 1 abbrev fin2 {n : ℕ} : Fin (n + 3) := finN (n := n) 2 abbrev fin3 {n : ℕ} : Fin (n + 4) := finN (n := n) 3These return a pair consisting of an index, either 0, 1, 2, 3 together with a proof that the index lies within an index.
I don't know why not use recursion. There's no performance penalty.
Zettel GitHub. Zettel Wiki Erdős #2. Problems worthy of attack prove their worth by hitting back. -- Piet Hein. PROBLEMS. Grooks, 1966. CC BY-SA 4.0.
Lies within a range defined by
Fin.Zettel GitHub. Zettel Wiki Erdős #2. Problems worthy of attack prove their worth by hitting back. -- Piet Hein. PROBLEMS. Grooks, 1966. CC BY-SA 4.0.
@ZettelDistraction I would love to be able to handle maths at that level, but I'm happy I even remember my school maths at this point. I've taken a Udemy course in maths as a refresher, and intend to get back into both maths and statistics in preparation for a future PhD or DBA (doctor of business administration). I'm not entirely sure what level of maths and statistics ability I would need, but at the very least I'll have to be able to handle some analysis and plotting.
I've considered Operations Research as a possible future career, and knowing what that entails gives me good guidance for what skills I need to develop.
I've never heard of the Lean language before. I'm always amazed how many languages there are out there. That goes for Janet too @ctietze, that's another Lisp dialect I've never heard of. There are so many languages and not enough time to learn them all! I'll be happy to be good at 2 or 3 in the long-run.
What are the words of the year? For 2025, I found these: Slop (Merriam-Webster), Rage bait (Oxford English Dictionary), Parasocial (Cambridge Dictionary) and Vibe coding (Collins English Dictionary). All of these words are related to AI. But what are the words of the year from my own Zettelkasten?
I filtered the index of my Zettelkasten by date. I rated the terms for each month, and then rated the resulting shortlist to get the Word of the Year.
Here are my results for 2026: augmented intelligence, clarity, concept map, context principle, family resemblance, generative learning, journey map, mimetic desire, modular thinking, resonance, self directed learning, syntopical reading, technocapitalism, and zone of proximal development. One of them will win the race.
Do you have a word of the year? What criteria did you use to decide?
Edmund Gröpl — 100% organic thinking. Less than 5% AI-generated ideas.
My Zettelkasten word of the year is 'friction', as I've changed the way I organize my ZK to reduce friction in it, partly thanks to your book on ZK minimalism, and partly thanks to the blog post The Friction Fallacy.
I realized I was making things too complicated, with too many unnecessary notes, and that it was over-organized. I've simplified things a lot this year, and my ZK has a lot less friction because of it.
Funnily enough, simplifying the organization has made it more organized now, as I can more easily find what I'm looking for, and I enjoy using it more too.
As I continue refining my Zettelkasten workflow, I’ve started reviewing another card-based note-taking method that has long been popular in Japan. Developed by the ecologist and anthropologist Tadao Umesao, the method was outlined in his 1969 book, The Art of Intellectual Production (『知的生産の技術』).
It remains one of the country’s most popular knowledge management methods to date. As far as I know, Umesao (who was a few years older than Luhmann) was unaware of Luhmann’s Zettelkasten, yet striking similarities exist between them (e.g., one atomic or granular unit per note, writing clearly for others and one’s future self).
Where they diverge is interesting. Luhmann was explicit about connecting notes, culminating in methodologies like Folgezettel, whereas Umesao avoided this. Instead, his method relies on sorting and shuffling notes based on loosely connected themes of interest or ongoing projects. Periodically, or when a project ends, you reorganize the notes according to evolving themes.
In a sense, Umesao was more radical in avoiding top-down categorization and hierarchy, always attempting to let ideas emerge bottom-up from newly related notes. The trade-off is that the method does not scale well as notes accumulate. This downside is somewhat counterbalanced by the fact that each note in Umesao’s system is larger (B6, as opposed to A6 in the ZK) and he encouraged writing them as if they were micro journal papers. Though perhaps an imperfect analogy, it is as if Umesao’s method deals with chemistry, whereas Zettelkasten deals with atomic physics.
Interesting! Can you recommend an English translation of the book?
Sadly, it seems that there is no English translation.
He seems to have come to similar conclusion as me: Don't treat the writing as a necessary evil to achieve the end of storing, but lean in because writing itself creates the value as a byproduct.
The focus on micro journals confirms this evaluation. I'd still disagree because if you write complete and well-formulate atomic notes, they would feel non-atomic. Even if you write purely atomic notes, you'll have to still write about the knowledge atom and it is good practice to provide yourself with commentary. Also: The link context will add to the note. In the end, you often have a relatively long note compared to the idea of atomicity out there.
I am a Zettler
Unfortunately, I couldn't find an official English translation. But with some OCR and LLM magic, I was able to create a full translation from a scan of the Japanese book.
I have a different understanding of Luhmann's system. It is not atomic. Structurally it resembles more a notebook with page numbers. You can only append and branch, but never rearrange.
The principle of one item per note is much older. For example, European library catalogs from the late 18th century already had one book per card. Umesao used the same principle. He describes in chapter 2 that he was writing bibliographical notes since high school, where each card described exactly one source.
Umesao reinvented topical index cards for his research material after WWII, when he needed to process material from field notebooks.
Umesao's method reminds me of Beatrice Webb's method from the late 19th century. She also prioritized the ability to shuffle.
I'm not aware that Umesao had a problem with scalability. In chapter 3 he writes:
Whereas Luhmann's system was static. Every note had a permanent place ("feste Stellordnung"). And because every note was permanently connected to a predecessor in a sequence, they did not have to be atomic. Each note had a permanent context.
I think it's the other way round. Luhmann's Zettelkasten was chemistry, because it's all about the connections between the smallest units ("Anschlussfähigkeit"). Umesao's cards are atomic. Shuffling requires that each card can stand on its own.
@harr Can you send me the translation?
I am a Zettler
@harr I would also like to get the translation. I assume it would be interesting to others on this forum too, so perhaps you could share it in a more general way, if you have a sharing method you like?
I wasn’t aware that this method was well-known in Japan. It piqued my interest, so I immediately read the book; a Korean edition is available.
While reading, I also got the impression that Umesao intentionally avoids establishing a fixed structure. Umesao suggests using cards (rather than a notebook) to reconstruct content. His key point is to avoid rigid categorization; instead, you should repeatedly review the cards and combine them, regardless of their specific subject matter. Following this approach means that any structure created is merely temporary. Since the cards have no fixed position, finding a specific card might require a bit of luck. This is a point @Sascha has already touched upon when discussing the potential downsides of the PARA method.
Umesao mentions using this card system for a diary as well. He notes that diary entries can be combined with other cards, and since every card is dated, they could theoretically be re-sorted chronologically. In practice, however, once the number of cards grows large, reconstructing them in chronological order becomes nearly impossible.
It seems to me that Umesao primarily used these cards as prompts—as sparks for new ideas. In Chapter 3, Umesao argues that (1) human memory is unreliable, (2) we should record things rather than relying on memory, and (3) since there is no need to record what is already in one’s mind, the card system he proposes is distinct from simple note-taking. He states:
This seems to account for the fact that one might even forget what one had placed in the card box in the first place. It appears, then, that Umesao intentionally embraced the idea of relying on such chance encounters.
Furthermore, the kozane method (こざね法) is reminiscent of the working process of Dustin Lance Black.
Reference (Korean Edition)
우메사오 다다오. (2018). 지적 생산의 기술 (김욱, Trans.). 에이케이커뮤니케이션즈.
Yes, thanks for making that connection! The parallels can be found in chapter 11 of Umesao's book (I'm relying on machine translations of the Japanese edition, p. 201):
Interestingly the kozane method is also about note sequences (compare them to Luhmann's technique at your own peril…). Umesao (p. 202, emphasis added):
Umesao continues (p. 204):
At his point Dustin Lance Black is so familiar with the future movie, that he can write down the first draft of the script from memory. Whereas Umesao looks at each individual slip. Both ignore the slips after they're done writing. Black stores the boxes filled with slips (dare I say zettelkasten…) in a closet. Umesao throws the slips away. The book continues (p. 205):
In other parts of the book, Umesao explicitly encourages non-writers to write (a thought similar to the US-American Writing across the curriculum I mentioned in another thread). On page 205 he continues:
I find it fascinating how people around the globe come up with similar yet different solutions for similar problems.
If I understand the book correctly, Umesao uses two different sizes of index cards: