82,853
edits
Normal Accidents: Living with High-Risk Technologies: Difference between revisions
Normal Accidents: Living with High-Risk Technologies (view source)
Revision as of 20:11, 9 January 2023
, 9 January 2023no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
||
| Line 1: | Line 1: | ||
{{a|systems| | {{a|systems|{{Erebus|gif|Air New Zealand Flight TE901}}}}{{quote|'''[[Accident]]''' /ˈaksɪd(ə)nt/ ''(n).'' <br> | ||
}}{{quote|'''[[Accident]]''' /ˈaksɪd(ə)nt/ ''(n).'' <br> | |||
An inevitable occurrence due to the action of immutable laws. | An inevitable occurrence due to the action of immutable laws. | ||
| Line 56: | Line 55: | ||
===When Kramer hears about this ...=== | ===When Kramer hears about this ...=== | ||
[[File:Shit hits fan.jpg|300px|thumb|right|Kramer hearing about this, yesterday.]] | [[File:Shit hits fan.jpg|300px|thumb|right|Kramer hearing about this, yesterday.]] | ||
So far, so hoopy; but here’s the rub: we can make our systems less complex and ''reduce'' [[tight coupling]] by careful design, functional redundancy and iterative improvement — air transport has become progressively safer as it has developed: it has learned from each accident — but, as long as it is a complex system with the scope for complex interaction, ''we cannot eliminate [[system accident]]s altogether''. They are, as coders like to joke, a feature, not a bug. | So far, so hoopy; but here’s the rub: we can make our systems less complex and ''reduce'' [[tight coupling]] by careful design, functional redundancy and iterative improvement — [[air crash|air transport has become progressively safer]] as it has developed: it has learned from each accident — but, as long as it is a complex system with the scope for complex interaction, ''we cannot eliminate [[system accident]]s altogether''. They are, as coders like to joke, a feature, not a bug. | ||
Furthermore, in our efforts to pre-solve for catastrophe, we tend ''not'' to simplify, but to complicate: we add prepackaged “risk mitigation” components: [[Policy|policies]], [[taxonomy|taxonomies]], [[key performance indicator]]s, [[tick-boxes]], [[dialog box]]es, [[bloatware]] processes, rules, and [[Chatbot|new-fangled bits of kit]] to the process ''in the name of programmatic risk management''. | Furthermore, in our efforts to pre-solve for catastrophe, we tend ''not'' to simplify, but to complicate: we add prepackaged “risk mitigation” components: [[Policy|policies]], [[taxonomy|taxonomies]], [[key performance indicator]]s, [[tick-boxes]], [[dialog box]]es, [[bloatware]] processes, rules, and [[Chatbot|new-fangled bits of kit]] to the process ''in the name of programmatic risk management''. | ||