> "A properly trained pilot should be able to solve an MCAS anomaly or any uncommanded flight-control input through procedures that are taught to all 737 pilots"
It blows my mind that anyone still talks like this.
My first job was writing (non-life-critical) scientific software for detail-obsessed university researchers working in a lab with notebooks and procedures. If "just solve it with training" could work for anyone in the world, it would have been these people. Yet it was immediately and abundantly clear that designing usability into the system would have far more impact on their success rate at any task than documentation or training or even the reliability of the software itself.
The movie "Apollo 13" showed astronauts working in a simulator, and engineers giving them faulty sensor inputs to try to trick them. They had to train to be able to identify this possibility, and react correctly to it. This isn't the sort of thing you can figure out on the fly (so to speak). If the solution to flying an aircraft with a faulty MCAS sensor was "the pilot should have read it in a book last month", it's no wonder they were in trouble.
The software industry does make some programs with random inputs and hidden internal state, and require users to figure out what's going on and solve it anyway. We call them "games". Perhaps the defining characteristic of a game is that, even if you've read the manual, you won't succeed on the first try.
> "But, he said, if he were designing the system from scratch, he would emphasize the training while also building the plane with three sensors."
Is even three enough? From an earlier version of the "2001" Wikipedia page [1]:
> "In the story HAL features a design with triple redundancy, so that if one of the three modules fails the other two can outvote it. However, there is a [[theorem]] in [[computer science]] that proves that for such [[distributed systems]] a vote-based [[sanity check]] only works if ''less than'' one third of the modules fail. Thus the failure of a single one of HAL's redundant modules would be sufficient to compromise the system, as apparently happened in the movie."
I don't know what theorem this is referring to. Help?
See also: Segal's Law.
[1]: https://en.wikipedia.org/w/index.php?title=2001:_A_Space_Ody...