Zettelkasten
This is a standardized way of note-taking where information come from readings and fleeting ideas, which are then organized and developed in permanence, building a critical mass. When put into work, the ideas are further distilled into projects which are writings meant to be published and scrutinized. This is more flexible than elementary systems of (1) taking everything into permanence, (2) the lack of a system thereof where ideas are unprocessed, and (3) notes inefficiently distributed into projects that are archived and disjointed from the knowledge frame at a whole. It is more efficient than that of an infinite canvas of mind-maps because it can be indexed and more easily converted into writing; mind-maps in this format is still a powerful format of fleeting notes that should be deleted when processed.
Official Terms For the Notes
- Fleeting Notes - Ideas thought of on the fly, written very roughly and will be discarded quickly once processed into permanent notes
- Literature Notes - A type of permanent notes that allows fleeting entries but also essential entries that can be referenced back that depends on the fleeting entries of the literature notes.
- Concept Notes - A type of permanent note which is context-independent which can provide a reference back to the literature notes used. These are the more distilled forms of the fleeting and literature notes.
- Project Notes - Distillation from concept notes with reference from literature into works for publication.
Adapting “Note-taking Edge-Cases” With Heuristics
A flexible note-taking system likes Zettelkasten makes things more efficient. Refusal of standardization-based efficiency comes largely from circumstances alleviated by heuristics. These refusals are motivated by prior subscription to the three elementary note-taking systems discussed.
Problem-Based (Mathematics)
When it comes to using Zettelkasten to approach mathematics, this note-taking system might be seen as an extra burden when it comes to drilling problems for a test. This contention is trivial. We can regard problem-drilling as a type of fleeting note. We analyze the pattern into a problem cookbook while drafting the permanent note. This should also help to rationalize problems you have not seen before because the patterns and connections between ideas are studied over the memorized problems.
Project-Based (Programming)
We do not assume that the lack of notes in programming projects destroys its credibility, though any reliable technology of scale comes with a manual and from that users benefit from using that technology. From the perspective of a developer of a module, this gets more nuanced. You are the (one of) the creator(s) of the documentation which covers a form of argumentative writing for the most essential details. Besides the discussed notes fleeting, literature, and concept notes there is also another note called the project note which is very implementable in your average software documentation despite the traditional Zettelkasten definition for project-notes comes initially estranged—(varying) form of drafts, bibliography, etc. are necessary components of any documentation that respects its users.
Reference
- How to take Smart Notes by Sönke Ahrens.
- Goodreads Link: https://www.goodreads.com/en/book/show/34507927-how-to-take-smart-notes
- My specific edition: https://library.vhmp.dev/book/13