What can programmers learn from pilots?

What can programmers learn from pilots?

A talk I gave at PyCon US 2015

077e9a0cb34fa3eba2699240c9509717?s=128

Andrew Godwin

April 10, 2015
Tweet

Transcript

  1. 2.

    Andrew Godwin Hi, I'm Author of 1.7 Django & South

    migrations Senior Software Engineer at Really likes cheese FAA & EASA PPL, working on IR
  2. 5.

    Commercial flying is very safe AIRLINES GA 0.2 11.2 CARS/TRUCKS

    0.53 MOTORCYCLES 15.6 Source: 2005 Nall report, 2004 NHTSA stats, 1991-2000 FAA stats, 40mph avg. road speed (fatal accidents per million hours) General aviation is still not bad
  3. 7.

    COMMON CAUSES Controlled flight into terrain (CFIT) Disorientation in clouds

    (VFR in IMC) Bad decision making (get-there-itis)
  4. 11.

    Soft Failure Crash hard on any serious error Redundancy, not

    single system reliability Freedom to get rid of servers whenever
  5. 13.

    Noisy Warnings Don't email/notify on every tiny error Choose 5

    top errors, solve them first If you ignore it for a week, delete the warning
  6. 14.
  7. 16.

    Poor Testing Test latency, memory issues, dodgy network and other

    unusual things Interactions are as important as individual units
  8. 19.

    Automation Reliance Don't rely on magical automatic failover Regularly practice

    manual recovery steps Know what your systems are doing
  9. 21.
  10. 24.
  11. 25.
  12. 27.

    Bad Priorities What are your critical features? What can you

    do without? Know what you want to fix first and test most
  13. 29.

    Unclear Responsibility Single person makes key decisions Others are always

    listened to Clear specifications and expectations
  14. 30.

    Blame Culture There is never a single cause of an

    accident Individual problems identified and addressed Blaming someone solves nothing
  15. 31.

    Blame Culture There is never a single cause of a

    problem Work back and find all of the bad factors Blaming people makes things worse
  16. 32.
  17. 34.