I know there's plenty of plane nerds in my circles...
-
I know there's plenty of plane nerds in my circles... and I know there's plenty of people always looking for new talk ideas... it strikes me that there’s a lot of potential for a “programming analogy” talk based off this. The video being referenced (linked the thread) is a fascinating set of insights, and the observation in this toot is just one of many possible interpretations of those insights.
https://hachyderm.io/@danderson/113142792603203381 -
James Bennettreplied to Russell Keith-Magee last edited by
@freakboy3742 @danderson I'm not gonna get into too much argumentation, but I'd be very very careful with selections from the AAMP; the stuff in those lectures was itself implicated in a horrific crash (AA 587 in 2001) for teaching pilots to be way more aggressive with the controls and mistrusting the aircraft than they should have been.
https://en.m.wikipedia.org/wiki/American_Airlines_Flight_587
tl;dr the first officer in the AA587 crash should have just taken his hands off the controls and let the plane level itself out (as it would). Instead he kept yanking on the rudder so hard that the force literally ripped the vertical stabilizer (the "tail fin") off the plane.
-
@ubernostrum @freakboy3742 It's good to place these things in proper context, but over-indexing on one accident is also unhelpful. The recorded lectures emphasize multiple times the power of the stabilizer and the importance to be gentle with its inputs, for instance.
Also, I was drawing parallels with things happening in software, not dispensing advice on how to fly an airliner
-
@ubernostrum @freakboy3742 That said, you do point out another valuable lesson that software could internalize more: there are no silver bullets, education and safety are a process and not a badge you earn or a tool you purchase. I also wish software would spend more time learning from other peoples' mistakes, rather than continue having the same crashes with different livery, so to speak.
-
@danderson
Ongoing safety trainings for internal software tools that someone at your org wrote on the train ride to a conference seems pretty unlikely give the state of that tools design and documentation...The lesson is that you need a government body to enforce safety with fines and public shaming via incident reports for an org to even consider ongoing accreditation/safety programmes