miniblog.

Doing another iteration on my diagnostics display. I'm reasonably happy with the bold highlighting within the error message. I'm not sure about the colour on Warning and Error though. It gives the output some visual structure, but arguably the message itself is more important.

I enjoyed watching this documentary on RuneScape (an MMO game): its MUD origins, the challenge of complex 3D models making iteration more expensive, and the team culture around it: https://www.youtube.com/watch?v=7RNK0YBdwko

Some Lisps can be both interpreted and compiled, which allows some lovely workflows. You can iteratively evaluate code snippets, and only compile when you're happy with your new feature! This takes the compiler out of the iteration cycle, so you get feedback sooner.