Today, I've been revisiting Docker things, docker-compose things, writing a bit of yaml. I've also been plotting a wedding anniversary getaway, setting up a backup power supply for hurricane shutters and doing just a little bit of tidying. I've been staying mainly indoors as the outside world alternates murder attempts via heat stroke, gale force winds, and whatever diseases the biting insects carry.

Malevolent nature -- that rainbow means us harm. Clearly.

There's a nice book out right now -- Tim Boring's Build An Orchestrator In Go, which is in the MEAP phase of publication at Manning. I appreciate the clarity of it. Not every book is so straightforward in detailing what a reference implementation should do before delving into the actual code. The code in some books is left to speak for itself. In others, the author seems like they'll never get to the point and so you just have to download the repo and ignore the prose. So far, the book is concise and illuminating and it pairs nicely with a day spent upping and downing containers.

On that point, it's gratifying to at least roughly comprehend how a tool works, and admire those inner workings as you're using it. Especially when that tool cradles years worth of your effort. I think Fred Dretske said that "understanding a thing is knowing how to build it" ...or something like that. I shouldn't have put that in quotes, but it sounds like a reasonable enough standard for understanding. I'm sure I'll wake up in the middle of the night with counter-examples.