Introducing... "QuackDoc" (?)

I guess this weekend can be considered somewhat successful on the projects front (even though I only really got around to 1 of the 3 projects I'd wanted to work on, though it *was* the most important one I wanted to knock off too)

Following a few sessions of toil, I have successfully put up an initial attempt at formalising all the conventions I've been using for writing inline code docs for all my projects over the years!

While there are still a few small loose ends to tack on, at least I can finally point to this thing and say: Here's the spec!

(And eventually: "Here's all the docs-compiler tools + editor plugins everyone asks for these days")

 

https://github.com/Aligorith/quackdoc

 

Reflections on my time working with Lilypond

Recently, I saw a post from a music student mentioning that they were thinking of writing up some stuff on the techniques they'd learned while using GNU Lilypond - i.e. a LaTeX-like "music typesetter" with its own custom input/programming language (doused / polluted with a heavy dose of Guile-Scheme).

This post gathers up some of my own notes on my own journey with these tools, and how this has tied into where I am today. Come to think of it, this year actually marks something like "just over two decades ago" that I was doing this shit (since IIRC, I probably started doing all this back in 2004!) - jeez... time flies and makes you feel old when put like that!