Tinderbox can be used to create good things. Implementing “Building a Second Brain” (BASB} principles can be used to create good things.
Learning how to use Tinderbox while constructing a second brain is my present venture. This is a joyful venture made more so by the insights, wisdom, good humor, and ideas many of you have shared with me and others.
Thank you, Michael Becker, for inspiring me to jump into YouTube video publishing. Yours are always helpful!
Building a Second Brain: Exploding and Distilling Kindle Notes videos are being created and posted to the playlist. Each will be five minutes or less in duration.
The Scope: From: Having Captured (Kindle notes) To: Distilling (Tinderbox)
Really interesting thread. Thanks for sharing and for all the unseen extra effort put into describing your process. I like your explicit reference to doing small tests first, an important assistive process we all to overlook … until after it would have avoided a bigger misstep.
Another helpful video and nice. The point about careful use of regex, back-references and scale is a subtle one. When starting out and without a background in regex (regular expressions), any successful result is a win.
The gentle point re ‘best practice’ is that if you start out doing things that may not matter now but may affect you later, that is also a win as you won’t have to re-factor (improve) existing code.
Importantly, in a test doc the size of the demo, don’t expect to see any difference in behaviour. You are doing these optimisations to help you future self.
To give some insight on the scale. IIRC, the original regex had to make 6 back-references and the regex was run 3 times per note: 18 back-reference creation tasks. This demo makes 3 and the stamp is used once, so 18 tasks → 3 tasks for just a single note. 18/3 is a reduction factor of 9. In a small doc, of no significance. In a note with several thousand notes, perhaps less trivial.
Importantly too, the ‘effort’ involved in regex is not a design quality issue of Tinderbox. Regex are a general software function: under the hood they do complex work and complex work normally takes more time/effort than simple work regardless of software language/code used—a constraint the app can’t work around but the user’s thoughtful employment of the feature can.