This is a lengthy but relentlessly fascinating story about the Boeing software (MCAS) whose recent malfunction killed hundreds of people. Not just worth a read, but probably worth multiple re-reads, too. I'll be thinking about this for a long time.

@marsroverdriver @marsroverdriver This, the Challenger accident, TMI, Chernobyl, Ford Pinto, Tacoma Narrows Bridge, Taum Sauk, etc.

All these engineering failures are worth knowing inside and out.

@cj @marsroverdriver Many, if not all, of those failures were due to politics and mismanagement. Engineering aspects are simply technical details or how exactly it turned out.


Some of the design failures were engineering oversights (not doing harmonics analysis on a bridge), some the engineers protested loudly due to the dangerous designs (NASA), and some the design was sound but construction company didn't build it to the design (sky bridge at a mall).

I don't think it's in an ethical engineers interest to just stay silent or blame up mgmt chain, they're in the best position to identify all 3 of these failure cases.


"The people who wrote the code for the original MCAS system were obviously terribly far out of their league and did not know it. How can they implement a software fix, much less give us any comfort that the rest of the flight management software is reliable?"

This is the money quote.

When I started working in the industry, I received an half-day training on "how your mistakes can kill people". I wonder now if it's standard practice.
Sign in to participate in the conversation
Mastodon for Tech Folks

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!