In this episode, we respond to Peter’s question: What do we not put into our archives? Here are a few links for stuff we discussed in the video. Shoot questions at us here, below the video, or e-mail for the next episode. We’ll be on air again in January. Watch this space for an announcement.
Posts from 2016
Sujith Abraham asks on YouTube: Why did you choose nvALT, where you have to create manual links so that you can search and find which other notes ‘backlinks’ to other notes, instead of a wiki (like DokuWiki, Tiddlywiki) where this would be provided automatically along with the benefit of plain-text writing/storage.
Sorry, folks, but this week’s episode recording didn’t take place. On Wednesday night I was struck hard by spontaneous and annoying bowel-emptying and I still couldn’t think straight when the scheduled recording would have taken place. I’m feeling a lot better already and we’ll try again next Thursday, Dec. 15th, same time: 16:00 UTC+01.
As always, just shoot your questions and demo requests at us!
We’ll be on air this Thursday, 3:00 p.m. UTC. Go to our live stream page on YouTube to see the countdown and localized times.
You’re all welcome to chat with us there on Thursday or leave questions here in advance if you can’t make it.
I set up a public Google Calendar you can look at subscribe to, if you want, although it updates super slow:
Useful resources to subscribe to announcements:
- Our YouTube Live page
- iCal Google Calendar file link
The actual calendar source for you to copy and subscribe to in your native calendar apps is this:
Johannes Schmidt gave an awesome lecture but most of you don’t understand German. So I thought I’d give you a quick flash of my notes of some points that I found most important. Keep in mind that this is not a comprehensive overview. Some points are left out or presented with the intention to be more relevant but as a result can be biased.
Hello dear friends of knowledge work and knowledge management! – Today we’re thrilled to tell you that our video experiments did bear fruit. We hereby announce the Zettelkasten Live channel.
We’ll announce the next recording time a few days ahead so you can tune in for the true live experience. If you want to suggest a topic, then leave a comment here or below the video.
Our videos will be heavy on live demonstrations, so if you want to see how we create and integrate new Zettel into our archive, this is the time to find out!
The videos will not be webinars or lectures. We’re going to chat about topics and see where the conversation is leading and demonstrate the workflow. But as Sascha announced in the intro, we’re working on a video project to make up on the lack of an English Zettelkasten Method book.
If you want to schedule a live participation with us, suggest a time and topic via e-mail and we’ll see if that fits out schedule. We’re based in Germany (UTC+01), so we may not always be live in your time-zone.
I am a huge proponent of not having any overview. The reason for that is the self-selective nature of the need for an overview. The need for a reasonable amount of overview can become a fetish which not only is not only unnecessary but even harmful for your productivity and creativity. If the need of generating overview for your knowledge archive becomes self-selective, it becomes non-functional and is cancerous to your knowledge system we call a Zettelkasten.
I managed my writing ideas in a to-do list for years. Since I follow the principles of the Getting Things Done methodology, a book idea was the perfect candidate for a “someday/maybe” project. That’s a project which you can prepare with anything from the top of your head without much real planning. You don’t have to follow-up on it anytime soon if you don’t want and thus defer taking any action until later. You can have ideas now and execute them later, whenever you wish.
After the scriptogr.am shutdown a while ago, Manfred Kuehn’s translations of Luhmann’s essays on note-taking and reading were gone.
I love that the source files are available, too, for anyone to see and edit, at GitHub.
In my opinion, Nassim Taleb’s most important idea is the concept of Antifragility. Here is his three-concept-model: Fragile means that something doesn’t like volatility and variability. In short: It doesn’t like to be touched. If you send something fragile via mail you write fragile on it so to say: Do as little as possible with it.
I fixed a few broken links on this site, both outgoing and between blog posts. To that end I re-read a few of the older pieces on this site.
Check out these goldies:
- Create a Zettelkasten for your Notes to Improve Thinking and Writing
- The Collector’s Fallacy
- Building Blocks of a Zettelkasten
- The 2 Forms of a Zettel Note
Sascha’s next post is in our extensive review loop already, by the way, so stay tuned.
Say you start with a fresh Zettelkasten or you learn more about an existing topic. You write your note and expand the text – and then you ask yourself this: should I create a new Zettel? Should I split this up? Can I attach this detail there? Finding an answer is pretty easy as the scenarios are limited:
If you work with the Zettelkasten Method you have to deal with a lot of reading. It is obvious that it is often not very obvious what to include into your archive and what not. I chose to create a typology of items to serve me as an epistemiologic amplifier. If you know how things look in general (type) you can find specific items more easily. I struggle a little bit with finding the correct english term. They are not themselves thoughts neither are they Zettel types. There are six of them:
I noticed that none of the tag indexes did show articles. Today I fixed this, so you can browse all tags like you should.
The Zettelkasten note archive is the storage of your knowledge. The Zettelkasten Method is an ideation tool, though. Using your Zettelkasten should help remember stuff and spark new ideas which will be stored as Zettel notes again. This process is fruitful and potentially never-ending. All that sounds nice, but naturally you have to start somewhere. How do you start working with your Zettelkasten? What’s the best first note?
With the help of intentions and promises, he maintains the honest impression that he is moving toward the good, yet all the while he moves farther and farther away from it.
Making decisions isn’t progress. Planning soothes your mind. But it’s a false sense of accomplishment. You still haven’t done anything by then.
Similarily, reading itself isn’t progress. We have learned a bit, but until we process the information, we haven’t yet succeeded.
Remember the Collector’s Fallacy:
‘[T]o know about something’ isn’t the same as ‘knowing something’. Just knowing about a thing is less than superficial since knowing about is merely to be certain of its existence, nothing more. Ultimately, this fake-knowledge is hindering us on our road to true excellence. Until we merge the contents, the information, ideas, and thoughts of other people into our own knowledge, we haven’t really learned a thing. We don’t change ourselves if we don’t learn, so merely filing things away doesn’t lead us anywhere.
Reading is cheap. Reading is easy. Processing notes is hard and time-consuming. But the hard work is the work that matters in the long run.
Last week I completed a script to help automate the process of compiling a first draft from an outline and Zettel notes. You can find it on GitHub or install it as a gem from the terminal:
gem install zettel_outline. Learn more about the format it supports and how you can adopt it to your Zettelkasten note archive.
If you are familiar with the latest research on Luhmann’s original Zettelkasten you already know that his first Zettelkasten is not lost. That’s right: he had two archives over the years. Somehow, a rumor did arise that he lost his first Zettelkasten. It was said that he had to start a new one because of that.