Categories

How the Boeing 737 Max Disaster Looks to a Software Developer

https://tech.slashdot.org/story/19/04/20/2152215/how-the-boeing-737-max-disaster-looks-to-a-software-developer?fbclid=IwAR3gspSc-vKIOv9XnVv0PmChPyVoMpnudXFfGFqs8cd27FKB55zoo7iAyas

“Slashdot reader omfglearntoplay shared this article from IEEE’s Spectrum. In “How the Boeing 737 Max Disaster Looks to a Software Developer,” pilot (and software executive) Gregory Travis argues Boeing tried to avoid costly hardware changes to their 737s with a flawed software fix — specifically, the Maneuvering Characteristics Augmentation System (or MCAS): It is astounding that no one who wrote the MCAS software for the 737 Max seems even to have raised the possibility of using multiple inputs, including the opposite angle-of-attack sensor, in the computer’s determination of an impending stall. As a lifetime member of the software development fraternity, I don’t know what toxic combination of inexperience, hubris, or lack of cultural understanding led to this mistake. But I do know that it’s indicative of a much deeper problem. The people who wrote the code for the original MCAS system were obviously terribly far out of their league and did not know it“.