Software engineering lessons from RCAs of greatest disasters
anoopdixith.com
Software engineering lessons from RCAs of greatest disasters
1–10 of 150 posts
Re: Software engineering lessons from RCAs of greatest disasters
#2[flagged]
Re: Software engineering lessons from RCAs of greatest disasters
#3(Root Cause Analysis)
Re: Software engineering lessons from RCAs of greatest disasters
#4I don't think this list hits any fundamental truths. The great depression doesn't have parallels to software failures beyond the fact that complex systems fail. And many of the lessons are vague and unactionable - "Put an end to information hoarding within orgs/teams" for example, says nothing. The Atlassian copy that section links to also says nothing. A lot of the lessons lack meaty learnings, and good luck to anyone trying to put everything in to practice simultaneously.
Makes a fun list of big disasters though and I respect this guy's eye for website design. The site design was probably stronger than the link content, there is a lot to like about it.
Re: Software engineering lessons from RCAs of greatest disasters
#5(Root Cause Analysis)
This whole RCA terminology has to die. The idea that there exists a single "Root Cause" that causes major disasters is fundamentally flawed.
Re: Software engineering lessons from RCAs of greatest disasters
#6Another train crash that holds a valuable lesson was https://en.wikipedia.org/wiki/Eschede_train_disaster
This demonstrates that sometimes "if you see something, say something" isn't enough - if a large piece of metal penetrates into the passenger compartment of a train from underneath, it's better to take the initiative and pull the emergency brake yourself.
Re: Software engineering lessons from RCAs of greatest disasters
#7(Root Cause Analysis)
This whole RCA terminology has to die. The idea that there exists a single "Root Cause" that causes major disasters is fundamentally flawed.
Actually everywhere "defense in depth" is used (not only in computing, but also in e.g. aviation), there can't be one single cause for a disaster - each of the layers has to fail for a disaster to happen.
Re: Software engineering lessons from RCAs of greatest disasters
#8[flagged]
Bruh! Does it matter if a sensible thought comes from a high scool kid or a parrot, as long as it is sensible?
Re: Software engineering lessons from RCAs of greatest disasters
#9(Root Cause Analysis)
I was excited that it might be about 1960s RCA computers being software incompatible with IBM s/360
https://en.m.wikipedia.org/wiki/RCA_Spectra_70
Then I finished the headline and opened this Wikipedia article