This is yet another culmination of my troubling relationship with notes to be done. I am going to keep this short, becuase thats the whole idea behind a stub note.
Central point, defined a little in Colophon For Mind Structure, is that the best way to properly utilize the inbox system is to write a very short, incomplete note and immediately move it out. Inbox has been working great, but I want to prevent a backlog from happening while also capitlizing on the ideas of “set and forget” note taking.
- essentially, I need to learn to trust that notes will resurface on their own through Passive Obsidian Worktime. I get OCD like sensations of distress when I have something I deeply want to learn/materialize, but cant at that very moment. not only that, but many of the things that would normally go to the inbox are concepts which cannot be just learned on a whim.
- Kuramoto model is the perfect example of stub notes in action - it is a complex model/concept that is obviously not completely written, as I have avoided talking about like half of the math behind the model. However, because it has something and exists outside of the inbox now, it will develop organically through backlinks, where I will eventually return and update it, like when I read papers.
This is also the best way to solve the Uncreated Note problem: dont leave broken links lying around the place, make them in inbox and write some shitty summary which obviously misses a lot of the content. A note doesnt need to be complete to be out of the inbox.
- oftentimes we do still need Uncreated Notes/links, or else we would be forced to write out the whole tree when doing one concept. broken links have their place, we can track by number of links to that uncreated note to find when we should write something.