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
310
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
330
Django Through The Years
andrewgodwin
0
220
Writing Maintainable Software At Scale
andrewgodwin
0
460
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
370
Async, Python, and the Future
andrewgodwin
2
680
How To Break Django: With Async
andrewgodwin
1
740
Taking Django's ORM Async
andrewgodwin
0
740
The Long Road To Asynchrony
andrewgodwin
0
680
The Scientist & The Engineer
andrewgodwin
1
790
Other Decks in Programming
See All in Programming
その面倒な作業、「Dart」にやらせませんか? Flutter開発者のための業務効率化
yordgenome03
1
130
Writing Better Go: Lessons from 10 Code Reviews
konradreiche
0
3.1k
Google Opalで使える37のライブラリ
mickey_kubo
2
110
SwiftDataを使って10万件のデータを読み書きする
akidon0000
0
230
(Extension DC 2025) Actor境界を越える技術
teamhimeh
1
270
Six and a half ridiculous things to do with Quarkus
hollycummins
0
190
monorepo の Go テストをはやくした〜い!~最小の依存解決への道のり~ / faster-testing-of-monorepos
convto
2
510
Flutterで分数(Fraction)を表示する方法
koukimiura
0
140
釣り地図SNSにおける有料機能の実装
nokonoko1203
0
190
CSC305 Lecture 08
javiergs
PRO
0
250
Software Architecture
hschwentner
6
2.3k
Leading Effective Engineering Teams in the AI Era
addyosmani
7
510
Featured
See All Featured
Speed Design
sergeychernyshev
32
1.2k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
32
1.6k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
10
880
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
657
61k
RailsConf 2023
tenderlove
30
1.3k
Context Engineering - Making Every Token Count
addyosmani
7
270
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Become a Pro
speakerdeck
PRO
29
5.6k
Mobile First: as difficult as doing things right
swwweet
225
10k
Build your cross-platform service in a week with App Engine
jlugia
232
18k
Balancing Empowerment & Direction
lara
5
690
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