and it's all
Any conversation
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Putting a slide deck together (outside of work), despite agreeing with Tufte on this matter. Iโll also create a handout that tells the story better than the slides and deliver that, too, but was asked to produce a slide deck, and I think thatโs part of the โeffort theater.โ
Using Beamer for the slides, but not a theme that looks like Beamer because humans have eyes.
I needed to process 20,000 json files & 20,000 JXL files. I'm pulling together a website from them all. Anyway, started with emacs elisp to handle it all, just because I've not done that before. Went kinda ok, and I'm gonna use org-mode to export it all to a website (done that bit loads of times before).
In the end, I ended up breaking out my C programming skills (late 80s->nowish). It was a delight. Nothing more refreshing than writing raw code, that doesn't rely on 3rd party code/libs.

