3 ms·
Software was definitely part of the issue.
by tiredofit 7y ago
Software was definitely part of the issue.
- tiredofit 7y agoBut it wasn't a software issue! /S https://philip.greenspun.com/blog/2019/04/08/boeing-737-max-crash-and-the-rejection-of-ridiculous-data/ https://philip.greenspun.com/blog/2019/04/08/boeing-737-max-... Any competent engineer would raise moral and ethical questions when working on software that is "mission ciritical". Causing a passenger plane to continually go into a nose dive because of data coming from a single sensor is absolutely ludicrous. Just because the software was horribly designed, doesn't mean it isn't a software issue.
- kahlonel 7y agoIt is a hardware design issue. There's a concept of N+1 redundancy in safety-critical systems, a hardware design decision. This basic philosophy was missing from the MCAS system[1]. You can argue that the software could just ignore bad sensor readings, but that's just software making up for hardware deficiencies. 1. https://www.seattletimes.com/business/boeing-aerospace/a-lack-of-redundancies-on-737-max-system-has-baffled-even-those-who-worked-on-the-jet/ https://www.seattletimes.com/business/boeing-aerospace/a-lac...