8 ms·
Researching the Therac-25 was on the list of topics one of my university lecturers assigned. Also on that list (from memory). * AT&T's switch cascade failure
by noir_lord 13y ago
Researching the Therac-25 was on the list of topics one of my university lecturers assigned.
Also on that list (from memory).
* AT&T's switch cascade failure
* Mars Climate Orbiter
* Ariane 5
He also took us through some bugs in code he'd written when he was doing massive telecomm's systems.
I came away with a few lessons.
* If it can't fail, test it twice.
* If it's designed so it can't possibly fail, test it three times.
* All code is buggy.
- masklinn 13y ago> If it's designed so it can't possibly fail When faced with this kind of requirements, I always lift my eyes right above my screen, where it is written: > The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair. And for emphasis, next to it is a poster of a nuclear island cut-out.
- mpyne 13y agoThe stereotypical example of something that "couldn't possibly go wrong" for our electrical division was the interconnecting wiring embedded in the case that simply connected point A to point B. Sure enough, we once had a motor controller break where the problem was interconnecting wiring...