Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
What can programmers learn from pilots?
Search
Andrew Godwin
April 10, 2015
Programming
0
300
What can programmers learn from pilots?
A talk I gave at PyCon US 2015
Andrew Godwin
April 10, 2015
Tweet
Share
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
320
Django Through The Years
andrewgodwin
0
210
Writing Maintainable Software At Scale
andrewgodwin
0
450
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
360
Async, Python, and the Future
andrewgodwin
2
680
How To Break Django: With Async
andrewgodwin
1
730
Taking Django's ORM Async
andrewgodwin
0
730
The Long Road To Asynchrony
andrewgodwin
0
660
The Scientist & The Engineer
andrewgodwin
1
770
Other Decks in Programming
See All in Programming
rage against annotate_predecessor
junk0612
0
140
エンジニアのための”最低限いい感じ”デザイン入門
shunshobon
0
130
Portapad紹介プレゼンテーション
gotoumakakeru
1
130
tool ディレクティブを導入してみた感想
sgash708
1
150
Processing Gem ベースの、2D レトロゲームエンジンの開発
tokujiros
2
100
旅行プランAIエージェント開発の裏側
ippo012
1
500
Improving my own Ruby thereafter
sisshiki1969
1
130
AIでLINEスタンプを作ってみた
eycjur
1
210
AI OCR API on Lambdaを Datadogで可視化してみた
nealle
0
210
RDoc meets YARD
okuramasafumi
3
150
令和最新版手のひらコンピュータ
koba789
14
8.1k
STUNMESH-go: Wireguard NAT穿隧工具的源起與介紹
tjjh89017
0
390
Featured
See All Featured
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.8k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
51
5.5k
Building Better People: How to give real-time feedback that sticks.
wjessup
368
19k
Building an army of robots
kneath
306
46k
Writing Fast Ruby
sferik
628
62k
Gamification - CAS2011
davidbonilla
81
5.4k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
18
1.1k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
131
19k
Reflections from 52 weeks, 52 projects
jeffersonlam
351
21k
Making Projects Easy
brettharned
117
6.3k
Visualization
eitanlees
147
16k
Transcript
Andrew Godwin @andrewgodwin Programmers LEARN FROM WHAT CAN Pilots?
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
flickr.com/photos/russss/16735398019/
Learning about aviation Applying lessons to coding 1 2
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
Pilot Source: 2005 Nall report Mechanical Other 76% 16% 9%
GA ACCIDENT CAUSES
COMMON CAUSES Controlled flight into terrain (CFIT) Disorientation in clouds
(VFR in IMC) Bad decision making (get-there-itis)
WHY DO I KNOW THIS? Detailed investigation of every accident
HOW DOES IT HELP US? Let's look at common problems
Soft Failure Explicit disengage signals Covering inaccurate instruments Replacing parts
at first sign of issues
Soft Failure Crash hard on any serious error Redundancy, not
single system reliability Freedom to get rid of servers whenever
Noisy Warnings Limited number of warning sounds Clear, unambiguous text
& speech No constant low-level warnings
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
Poor Testing Every part tested to destruction Well known statistical
limits Knowing when, not if, things fail
Image: © Boeing 2010
Poor Testing Test latency, memory issues, dodgy network and other
unusual things Interactions are as important as individual units
Automation Reliance Tested without autopilot/instruments Plane usually advises, rarely controls
Easy to see what's happening and why
flickr.com/photos/wkharmon/4631001766
Automation Reliance Don't rely on magical automatic failover Regularly practice
manual recovery steps Know what your systems are doing
People Reliance Checklists for everything Warnings built around common assumptions
Reduce workload at critical times
None
People Reliance Checklists for releases/testing/onboarding Automate common tasks Reduce workload
at critical times
Bad Priorities Aviate, Navigate, Communicate Minimum Equipment Lists Mayday priority
Minimum Equipment Quiz Passenger video screens Lavatory ashtrays Air conditioning
Fuel recepticle caps Seatbelt signs Weather radar
Minimum Equipment Quiz Passenger video screens Lavatory ashtrays Air conditioning
Fuel recepticle caps Seatbelt signs Weather radar
Margaret Hamilton
Bad Priorities What are your critical features? What can you
do without? Know what you want to fix first and test most
Unclear Responsibility Single person always in command Others are always
listened to Clear, concise communication
Unclear Responsibility Single person makes key decisions Others are always
listened to Clear specifications and expectations
Blame Culture There is never a single cause of an
accident Individual problems identified and addressed Blaming someone solves nothing
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
Deadlines Always carry extra fuel Always have an alternate Land
safely rather than at the destination
Deadlines Don't schedule everyone at maximum Always expect unknown problems
Ship good code rather than to a deadline
Takeaways
Checklists First step before automation
Filter unimportant errors Keep ignoring it? It's not important.
Pick your key features Don't worry about breaking minor stuff
Reward good decisions It's often not the people staying late
Ops are like pilots Boredom punctuated by moments of terror
Thanks. Andrew Godwin @andrewgodwin eventbrite.com/jobs