Index

• need to have a pruning session sometime - a lot of unnecessary nodes that could be better restructured as sub-trees.
• some nodes are just plain useless and are an itch I scratched gone itchier.

• an explicit :wip: tag denotes that I'm actively working on that node (different from :transient:)

• the literate programming setup is live and working well with the publishing script.
• I have it setup for rust, common lisp and elisp for now
• mermaid-cli also works for flowcharts locally but need to figure out the publishing process for it to be rendered properly on the online buffer -> UPDATE (2 mins after I pushed this) : just needed to put in an exports: both in the src blocks..
• making notes is second nature to me now -> whenever I'm studying/want to start a new project, I don't have to think much in terms of how I'll document the process. The snowball is rolling.
• Noticing an significant decrease in the pre-thought of remembering stuff before I get start with a domain. Now that it is delegated to something with the memory of a steel trap, all that I learn is a few keystrokes away.
  • surprisingly, I have a mental parallel of this web that I implicitly call upon when remebering stuff -> that is an unexpected and beautiful side-effect…
• Errors may creep in aynwehr -> I do'nt particurlayl edti what I wirte here and all is typed in a single pass, along with my thoughts.
  • this might result in needlessly long structures that could be better organized. Of course, I don't do this for the main blog. The buffer is not something that I maintain for perfectionism, but for maintaining a playful approach towards my studies.

Here are some conventions that I follow to organize my work:

• Tagging
• Timestamps
• will be expressing math as S-expressions rather than latex
  • the former flow fluidly off my fingers
  • the latter I'll reserve when for publishing on the main blog: latex isn't exactly good while note taking - is a distraction.
  • my goal being encoding the concept (procedure/definition/relation) in a way that is more accessible to that of a programmer's mind
  • I also choose to do so as it'll help me learn map concepts from different domains into a common symbolic representation (hmmmm … : yeah…., math already does that - I guess I'm just being peevish)
• A top-down knowledge building style : the human mind doesn't remember what it knows. Trying to remember a specific latent knowledge node in this graph will be more efficient than building all the base nodes one by one until I reach a practical level of application. I will add atoms as and when I see fit : I might even insert most from memory.
• each major node has its own idea buffer to keep note of specific ideas that I haven't organized yet.
• at any given point of time, several emtpy nodes may exist : I'm not trying to be exhaustive right away when exploring a domain. This is supposed to be an eternal work in progress. However, to indicate that I intend to work on a node later on and it's not just an empty atom, I've placed :tbp: (to be populated) tags on such nodes.