TechWorkRamblings

by Mike Kalvas

202109091134 Notes should be concept-oriented

Each of our 202109091129 Evergreen notes should be written about a concept, not about a book, project, or event. This is the only way to ensure that we're able to discover connections across books, projects, events etc. (202109091131 Notes should surprise us) and that our notes will form a web of tightly linked concepts (202109091132 Notes should be densely linked).1

This also ensures our principle that 202209091130 Notes should be atomic. If we write a single note about a book, we may write more than one concept into that note. Now recollection and linking requires remembering the book and the fact that the concept was in that book, instead of just the concept. If we keep it concept oriented, 202109091133 Notes should associate organically and similar concepts from individual books will still coalesce.

Another benefit of keeping notes concept-oriented is that we can build on our previous work. 202109060836 Knowledge should accumulate, and by ensuring we're noting concepts, we can accumulate our learnings from one book on a concept with other learnings on that same concept. Contrast this to just taking notes per book. In that situation, we never realize the connection between two books talking about the same concept, or if we do, we don't fully investigate the depth and breadth of that relationship — we just remember that they covered similar topics and yet were slightly different. An even more extreme example is two very different books that are related only by one subtle point. Would we notice that point if we weren't keeping our notes concept-oriented?


  1. Matuschak, A. (2017). Evergreen notes should be concept-oriented. Andyʼs Working Notes. https://notes.andymatuschak.org/z6bci25mVUBNFdVWSrQNKr6u7AZ1jFzfTVbMF