In this post, I write fleeting notesThe simplest way to use Zettelkasten for note managementEverywhere I look, I find complicated Zettelkasten workflows that require a multi-step setup process. On top of the setup, notes must be regularly reviewed and categorized. For some, this workflow may be a godsend, but for most, it's overkill. I'm here to unveil my method of using Zettelkasten. It may be unconventional, so beware.
Zettelkasten can be distilled into two principles: take atomic notes and make connections. What this means is to take notes that are limited to on an article titled "When Should You Start a New Note?". This article gives tips on when to create a note and when to use an existing note. Hopefully, this process can give you ideas about how to improve your Zettelkasten workflow
Article Link: https://zettelkasten.de/posts/when-start-new-note/
- sometimes it's difficult to know whether to create a new note or append an existing note. And that can stop note-taking entirely because there is cost in starting an activitythere is cost in starting an activityLike inertia, it's not easy to get things going right away. Usually there is a cost.. the most important thing is to just start writing and worry about organization second. starting is always better than not doing anythingstarting is always better than not doing anythingWhen we start something, we can get things done. Even if we go about it in the wrong direction, we can get real experience from actually doing the thing and learn from it.
- probably one of the most important things about Zettelkasten is that you're always in search for related or already existing notes. because reusing components is more efficientreusing components is more efficientso we don't need to "reinvent the wheel"
related to reuse code for efficiency and maintainability
- expanding a new note can be dangerous because it might take the atomicity out of the note making it harder to reuse the component. reusing components is more efficientreusing components is more efficientso we don't need to "reinvent the wheel"
related to reuse code for efficiency and maintainability. So it's better to keep notes smaller and contained
- notes are too big when info retrieval is slownotes are too big when info retrieval is slowBecause getting info is slow it's harder to follow principle of atomicity and reusing the component is hard
notes/reusing components is more efficient
- the process of taking notes with Zettelkasten is organic. The types of connections you make change and adapt as you develop better systems of connecting things. Reminds me of the brain. the brain has an organic structurethe brain has an organic structurenotes/the brain is a network of ideas. The structure is dynamic and grows unlike notes/organization with the tree structure.
- best not to overthink things or else you lose speed and productivity starting is always better than not doing anythingstarting is always better than not doing anythingWhen we start something, we can get things done. Even if we go about it in the wrong direction, we can get real experience from actually doing the thing and learn from it.
- no universal guidelineno universal guidelinemost things don't have a universal guideline, it's more about understanding your use case and how you can adapt a solution for it.
Here is a video of me taking the notes + my commentary.