drmorrTwo new blog posts today! First is the (now public) transcript from my SRECon talk: "Stop Reading Changelogs: Safer Kubernetes upgrades with simulation"
https://blog.appliedcomputing.io/p/stop-reading-changelogs-safer-kubernetes
I'm trying a new experiment with my blog: all posts will still be public, but instead of putting them behind a paywall for a weekend, I'm going to leave them behind the paywall for a week. As I have mentioned, I'm trying to get a few more paid subscribers to help support ACRL's conference attendance, which is were I'm able to get most of my business and new leads.
So this week's post, which is a recap of my SRECon talk from last week, is now available for paid subscribers only, and will be available for free to the general public next Monday! Check it out if you want.
https://blog.appliedcomputing.io/p/stop-reading-changelogs-safer-kubernetes
"No one ever made a decision because of a number. They need a story" Daniel Kahneman.
How to get better at storytelling? Lots of practice! If you're involved in incidents you'll have lots of practice, and you can tell them to people at SRECon :D
(Is this a good time to plug ACRL's one public postmortem? 🤣 🤣 🤣 🤣 🤣)
https://blog.appliedcomputing.io/p/postmortem-intermittent-failure-in
"So what, Lorin, you told us all this stuff, what am I supposed to do with it?"
One take-away: when you do your incident writeups, tell it as a story.
A third story told by Diane Vaughan said that challenger was a story about normalization of deviance.
If you tuned a noisy alert, that is normalization of deviance: if the alert is firing, but the system is healthy, we make the alert less noisy! We do this all the time.
Another story, told by Edward Tufte (of Visual Display of Quantitative Information fame) said this was about "poor information presentation and bad visualization".
Not surprising that an info-vis guy said it was an info-vis problem 🤣