Notices by Lorin Hochstein (norootcause@hachyderm.io)

I blame everyone who has ever conducted an interview where they asked a leetcode question instead of a question on how to implement staged deploys.

I have no information about how this incident came to be but I can confidently predict that people will blame it on greedy execs and sloppy devs, regardless of what the actual details are. And they will therefore learn nothing from the details.

I’m just young enough that I never had to deal with “near” versus “far” pointers in C on Intel machines.

@unnick checking for byte size … 8 bits

Whoever is responsible for redirecting https://wedontneedno.education to wikipedia: I salute you.

Complexity-as-a-service

If you don’t know how the work actually gets done, your proposed improvements are unlikely to have the effects that you expect.

One day I’d like to write a “Senior Software Engineer” chatbot that randomly responds to questions with answers like:

- “It depends…”
- “What are you trying to accomplish?”
- “You’re asking the wrong question.”

@stuartmarks Right??? We should just stop writing bugs altogether.

Two of the biggest sources of incidents I’ve seen are:
1. Legacy code
2. Migrating away from legacy code

The conclusion is clear: you should only write non-legacy code

@thomasfuchs How did they ever get Mark Hamill, Malcolm McDowell and John Rhys-Davies to star in this game???

New blog post: https://surfingcomplexity.blog/2023/06/10/treating-uncertainty-as-a-first-class-concern/

Courtney Nash of https://www.thevoid.community speaking now at #srecon

Drink!

Woo, stories!

So much to learn from near misses.

She mentioned the Rasmussen safety model. Here’s my doodle of it: https://twitter.com/norootcause/status/1489113158732038150?s=46&t=ESZh20L6i6SGjIf5be8m9A

* Bankrupt - boundary to economic failure
* Burnout - boundary to unacceptable workload
* BOOM! - boundary of fundamentally acceptable performance