5 ms·
> ...why these design trade-offs were made. While your line of reasoning is sound in most scenarios, in this case, the why is pretty obviously written on the w
by Rooster61 7y ago
> ...why these design trade-offs were made.
While your line of reasoning is sound in most scenarios, in this case, the why is pretty obviously written on the wall. The overriding reason why this hacky-hack software solution was slapped into the airframe was to keep from having to reclass the plane following the addition of too-large engines. Your reasons listed played into the design decisions that became MCAS, but the underlying reason as to why any of this nonsense was needed in the first place is because non-engineers forced a shitty situation on the people who actually implement these airframes.
Hacker News is frequented by engineers from multiple disciplines, including software engineering, and many of those engineers know the kinds of terrible design decisions forced by management that come about to make a quick buck. People are pissed about it due to this fact, and rightly so.
- ethbro 7y agoI get the impression half of HN is pissed at Boeing because they understand terrible management-driven engineering decisions. The other half just think we're "pissed off at Boeing" and makes claims like "well, they should have just built the plane right." And so you get engineers taking umbrage (IMHO, rightly so) for the ridiculous simplification being made by the second half.
- Rooster61 7y agoThe lovely thing about HN is that that first half is probably indeed half of the people reading; whereas this same conversation on reddit might be 10% engineers, 90% echo chamber. That's at least my experience.