11 ms·
my goodness, yes. My background is aerospace engineering, software engineering, and finance. Here on hacker news, the software discussion is good, aerospace
by vpribish 7y ago
my goodness, yes. My background is aerospace engineering, software engineering, and finance. Here on hacker news, the software discussion is good, aerospace is terrible, and finance/investing is teeth-gnashingly, garment-rendingly hopeless. Despite this I do read lots of the health and wellness discussions - and have no idea whether they are really any good.
- rayiner 7y agoAs an AE major, what aerospace discussion do you think is terrible?
- NikolaeVarius 7y agoAE myself. Reading the discussion on the 737Max incident generally is extremely painful. Also anything involving electric airplanes
- NoodleIncident 7y agoIt would be a lot quicker for you to have posted your own interpretation of the incident, so that everyone could compare their own views with it at once. But, I'll post the version of events I gathered anyway: * Boeing wants to make a new plane, by pretending it's a "small" modification of their existing plane. (don't have to get certified; the old plane designs wouldn't get certified today; costs a lot to certify and re-train; take your pick) * One of the regulations they have to stay within is that the plane shouldn't pitch its nose up without any pilot input in that direction. (Maybe it was more specific than that; something about requiring more force to pitch higher up?) * Some airplanes comply with this requirement because they comply with the laws of physics. (Including presumably the original 737; otherwise this system wouldn't be new, right?) Not so the 737Max. * The system that caused the crash was meant to comply with the above. If the aircraft was pitched up, it applied a force on the controls down. (every 10 seconds or so?) * One of the problems was that there were only 2 sensors feeding into this system. If you have 3 sensors, a single failure can be outvoted; if you have only 2 that disagree, no matter what you try, you'll get it wrong in some cases * Something something software. We've already established we're working with too few sensors to be safe, and the system applies force intermittently every 10 seconds, so it's hard to even tell that it's a problem. Who cares how the software works? * Because of the original desire to pass through this new plane under the same certification, there was no new pilot training that mentioned this system. There was some sort of optional indicator, I think, too? The output of the broken system was also intermittent, so it was hard for pilots to quickly realize what was happening.
- starpilot 7y agoThe "as a pilot..." posts baffle me. It's like asking a car driver for his thoughts on automotive engineering, or asking a random computer user about which programming language is best for whatever. This of course is fine if the topic is piloting, but there's a vast gulf of understanding between aircraft pilots and aeronautical engineers.
- base698 7y agoMaybe, but as a pilot you are tested in depth in systems to a degree not found in automobiles. Aeronautical engineers also miss a lot of the skin in the game that a pilot would have.
- arkades 7y agoAs a physician, I can tell you that the health and wellness discussions in the media, Internet, and HN are horrendous.