Book Report
A Clojure macro to turn source files into interactive notebooks.
Goal
When learning Clojure from books there is no great solution for organizing notes, exercises, and examples. Online notebooks only provide a subset of Clojure functionality and using comments mean evaluation and documentation are separated providing difficulty in revisiting notes later on. For instance I ended up sinking an hour on the first few examples from a chapter only to find out the notebook service I was using doesn’t fully support full Clojure functionality. Not only is debugging made more difficult with add an extra layer of frustration but now there is this extra context you need to be aware of when trying to follow along with examples.
I wanted a full Clojure experience that would allow me to organize what I’ve read and wrote into bite-sized lessons. It needed to let me revisit my notes and not lose any context such as the code that was written, what it does, and what I want to learn from it. It also needs to feel natural to use so retyping code as a string to show along side evaluation results would not cut it. Book Report allows you to send notes and code to a lesson macro and it gets printed with the notes, the source code, and the evaluation results to provide the whole story.
Process
- Learn how to work with macros from Clojure for the Brave and True book.
- Researched if a similar macro existed already in Clojure, didn’t see anything similar.
- Wrote a quick and dirty version of the macro, pushed it up, asked for feedback in the Clojure slack community.
- Community feedback was positive. Cleaned up code, added new features.
- Wrote unit tests where appropriate.
- Designed a logo, for fun, to give the library a more polished look.
- Announced the library in both Clojure Reddit and Clojure Slack.
Discoveries
- Got a strong first taste of the power of Clojure macros. They’re quite powerful!
- I can work from books a bit faster now 😄
- Learned that asking simple, more general Clojure questions in the Slack received more answers with better discussion than asking very tool-specific questions. For instance asking “What is the best way to concat two lists together?” provided way better answers than “How do I combine two vectors of reitit route collections?”.