Lorin Hochstein
Student of complex systems failures, resilience engineering, cognitive systems engineering. Will talk your ear off about @resilienceinsoftware.org
- I can’t predict what the next incident will be, but I will claim with confidence that your prediction about it will be wrong.
- Of all the risks exposed by this incident, what is your basis for claiming that the one that you’ve labeled “root cause” is the one most likely to bite us in the future? If you could predict the future, we wouldn’t have had this incident!
- Air-traffic-out-of-control
- I think of an incident retro as akin to meeting with customer to discuss their needs. Spending that time discussing how you’ll build a solution is not a good use of the limited time you have with them. Instead, we should use that time to understand their problems and context. Solutions come later.
- “Yes, but which hole was the *root cause*?”
- If your goal is to never have the same incident twice, then congratulations, you’ve already achieved it! On the other hand, if your goal is to get better at dealing with incidents, you’re going to need a different strategy for retrospecting on your past incidents.
- Who among us could have predicted that abandoning the “HBO” brand was a bad idea? Except for each and every one of us, I guess.
- Design for operability
- I never appreciated how funny this Simpsons joke was until I moved to the U.S.
- What fruit has the smallest window where it’s ripe enough to eat without being overripe? Is there something that beats avocados?
