Discover and read the best of Twitter Threads about #ResilienceEngineering
Most recents (3)
An excellent overview of @LauraMDMaguire's dissertation ("Controlling the Costs of Coordination in Large-scale Distributed Software Systems") is on the Resilience Engineering Association's site.
Will give the url after some fascinating bits regarding the results...
Will give the url after some fascinating bits regarding the results...
(1)Incident Commanders needing to recruit other folks to help with a response underway have to make multiple efforts.
They have to:
- Monitor the current capacity (of the response) relative to changing demands and identifying additional resource requirements
They have to:
- Monitor the current capacity (of the response) relative to changing demands and identifying additional resource requirements
- Identify the skills and experienced required
- Identify who is available
- Determine how to contact them
- Contact them and alert them to the event
- Wait for a response
- Identify who is available
- Determine how to contact them
- Contact them and alert them to the event
- Wait for a response
"Resilience engineering is about identifying and then enhancing the positive capabilities of people and organizations that allow them to adapt effectively and safely under varying circumstances. Resilience is not about reducing negatives (incidents, errors, violations)."
1/8
1/8
"Resilience engineering is based on the premise that we are not custodians of already safe systems. Complex systems do not allow us to draw up all the rules by which they run, and not all scenarios they can get into are foreseeable."
2/8
2/8
"Systems are not inherently safe: they need to operate under competitive pressure, having to meet multiple conflicting goals at the same time, and always with limited resources. People and organizations have to create safety under these dynamic circumstances."
3/8
3/8
I am somehow surprised when I encounter folks with such strong beliefs in the "Humans-Are-Better-At/Machines-Are-Better-At" approach to designing software. At this point I shouldn't be surprised, but still am. 1/n
This "HABA-MABA" philosophy has been so ingrained that it almost flies under the radar as worthy of attention to some.
Who will argue with "make the computers do the easy/tedious stuff so humans can do the difficult/interesting stuff"? (apparently, I will) 2/n
Who will argue with "make the computers do the easy/tedious stuff so humans can do the difficult/interesting stuff"? (apparently, I will) 2/n
This notion was first described in the late 1940s, and it was known as "Fitts' List" - original is shown here... 3/n 
