Delight and Outrage

A twin page between dojo and ubu , now also pixie-recurse . See Twin Pages in FedWiki.

While I compiled my lists of topics and techniques I wanted to learn, and habits I wanted to build during this time, two particular learning lists sorted themselves out: **Delight** and **Outrage**.

While between jobs, I connected (reconnected) with learning communities focused on two of my motivations for learning within the field of software development. Both of them branch from a common root - what do I find engaging? What causes me to seek information and try things out?

**Delight** touches the feeling of satisfaction I get for creating things. It includes my side project, reviving Tamsin Bowles' Weatherpixie paperdoll weather report. In terms of learning topics, it covers literate programming, computational notebooks such as Jupyter and Observable, and Federated Wiki. It's significantly visual in focus, but not limited to that. It aims mostly to avoid the points of complication (platforms, dependencies) that motivate the second list.

**Outrage** comes from my feeling that software development and operations come with a large and unnecessary amount of work related to *coordinating the pieces*.

Reasonable people may differ in their expectations for the amount of work to coordinate the pieces and stages of software development. For me, the overhead of installing, deploying, and maintaining software is a drain on my morale and productivity. This strikes me especially when learning unfamiliar environments. Starting a new job remotely made my challenges obvious.

I am hoping to take a leaf from Larry Wall's virtues of Perl: Laziness, Impatience, and Hubris. (I'm not good at Hubris, but it's something to work on).

Justin Searls' talk (RailsConf 2019) on The Selfish Programmer YouTube speaks to both Delight and Outrage.

Things on the **Outrage** list relate to *developer experience*. Broadly this includes DevOps tooling, learning modern approaches including Kubernetes and HashiCorp's suite of tools; I like their attitude. (Or rather, I liked HashiCorp's attitude until they changed their software terms to be no longer free software terms; not clear now; Docker did a similar "no longer free" change earlier).