Notes will be markdown, I'll probably use Marked (EDIT: I went with react-markdown) Looking around for info on [[]], it looks like this is commonly referred to as "Wiki links" and there are some nice tools for using them in VSCode. Don't know how long I'll be writing notes in VSCode though, so I'll sort of ignore for now. I just wanna see how easily I can parse them. Some collected notes on progess: Node.js fs promises 44 minutes in Displaying the notes Hello, next! Links out, links in

The act of shipping software is often hindered by Yak shaving. A fix splinters out into several items, which in turn splinter out into several more items each. It is important to exercise caution of this happening, and chop off the tail when necessary. In personal projects, however, I have found aspects of Yak shaving to be some of the most illuminating parts of programming. Take this blog for instance. I could have just set up Mediawiki for myself. If What I wish this to be were truly limited to just getting words on the web, I would have done so. But I wanted to write code in addition to writing words. So I have found myself doing work that is explicitly not related to getting words in front of people. Building an extension maybe helped me get these words out more quickly, but in reality most of the joy came from learning something new. Hello, next! in the end is responsible for you seeing these words right now, but it was not necessary. I could have written my posts as plain ol' HTML(tm). And it's all very fun! A "simple" project (glorified static site generation) can become a beautiful problem that exposes me to different tools and the frameworks, the amount of which is limited only to wear I draw the line.