#Hidden deep developer manual#
You could try to prevent that with more and more autopilots and warnings, but at some point pilots have to be able to fly the thing on manual and need to have the actual training for the conditions. Pilot exceeded their training and flew into the water. > The probable cause of the crash was "the pilot's failure to maintain control of the airplane during a descent over water at night, which was a result of spatial disorientation".Īt some point there's not much else to do. Look at the analysis of the JFK, Jr crash in 1999: Winning means accepting humans are fallible and doing my best to design systems for them instead of holding them at fault in cases where a better design would have prevented the mistake. There's a saying: do you want to be right or do you want to win? Personally, I want to win (i.e. Meanwhile, if you accept that human behavior is what it is and design around it, you can save many people from mistakes in the first place. The problem with "STOP AND THINK" is that it requires every person to learn that lesson individually. (Yes, ideally, no one is ever logging into a production machine.)
And it protects more than just me, but anyone else who logs into those machines.
That's saved me from even more mistakes than reading back commands. All my production machines have a red shell prompt. So another thing I learned was to make any shells on production systems be visually distinct. Guess what? I still occasionally make mistakes. It was a great lesson and has saved me from a lot of mistakes. One of the first things I learned from a grey beard at the time was after typing a destructive command, take my hands away from the keyboard and read back what I just typed before pressing enter. I've been doing system administration and programming since the early 90s. > should have been for the author to STOP AND THINK when deleting The NTSB does not assign fault or blame for an accident or incident rather, NTSB investigations are factfinding proceedings with no adverse parties and are not conducted for the purpose of determining the rights, liabilities, or blame of any person or entity." Modern accident investigators avoid the words "pilot error", as the scope of their work is to determine the cause of an accident, rather than to apportion blame. It is equivalent to a non-apology-apology. My reading of that blog post is that the author didn't actually accept any blame, didn't see any need to change any of their behavior and shifted it all onto GH. Trying to fashion a world where people can navigate it successfully on completely thoughtless autopilot all the time isn't possible.Īlso, that blog post is irritating because "Lesson #1" should have been for the author to STOP AND THINK when deleting or presented with a scary modal dialog box that actions were going to be permanent. There isn't any good substitute for just learning early that if you are going to delete something you need to stop, think, read and wait a second before hitting that button. I'd like to see if the change to the UX to show that information has made any actual measurable impact on the accidental deletion incidents that GH sees. Gonna delete 8,000,000 stars on this project? Good. Meanwhile, it is going to be very difficult to break people who are stuck on "autopilot" and just aren't reading anything out of it vi any kinds of dialogs or messages. And with UI/UX like this there isn't much ability to do that, since people don't get certified on using GitHub.
#Hidden deep developer manuals#
They can try to address that through training, certification, recertification and updates to manuals and checklists, but at some point some level of human failure is going to be inevitable. For scheduled air transport, pilot error typically accounts for just over half of worldwide accidents with a known cause > During 2004 in the United States, pilot error was listed as the primary cause of 78.6% of fatal general aviation accidents, and as the primary cause of 75.5% of general aviation accidents overall. Yeah they do and pilot error is very common: Accident investigations intentionally do not apply blame.
0 kommentar(er)
