Thinking about writing a book
Over the years, by haphazardly filling-in missing details to the docs as questions arose, I've let the Uxntal language pages grow into a tangled and overgrown labyrinthine mess that oftener threw folks into opaque dead-ends than answer questions.
This week, a pointedly cutting criticism of the Uxn documentation shook me out of the laissez-faire that I had over these few pages and reminded me how letting it go the way I did was a disservice to others, but especially myself, considering that I may be using this tool, possibly for the rest of my life.
Since I couldn't clearly discern what should and shouldn't be there, I've asked for help, and got excellent ideas. With feedback from both new learners and experienced folks, I rewrote most of the documentation, included new examples, expanded tests and added setup instructions for both Uxn, and Varvara.
Looking at the documentation now, I feel like I would very much like to work on writing a book about it, to have a paperback artifact in the style of Henderson's LispKit Manuals. A treatise on the design and implementation of the system from the bottom up, but also, plastered with drawings.
