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
310
Django Through The Years
andrewgodwin
0
200
Writing Maintainable Software At Scale
andrewgodwin
0
440
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
350
Async, Python, and the Future
andrewgodwin
2
660
How To Break Django: With Async
andrewgodwin
1
730
Taking Django's ORM Async
andrewgodwin
0
720
The Long Road To Asynchrony
andrewgodwin
0
660
The Scientist & The Engineer
andrewgodwin
1
760
Other Decks in Programming
See All in Programming
Flutterで備える!Accessibility Nutrition Labels完全ガイド
yuukiw00w
0
170
PHPでWebSocketサーバーを実装しよう2025
kubotak
0
320
LT 2025-06-30: プロダクトエンジニアの役割
yamamotok
0
870
20250704_教育事業におけるアジャイルなデータ基盤構築
hanon52_
5
1.1k
テスターからテストエンジニアへ ~新米テストエンジニアが歩んだ9ヶ月振り返り~
non0113
2
220
テストから始めるAgentic Coding 〜Claude Codeと共に行うTDD〜 / Agentic Coding starts with testing
rkaga
15
5.6k
RailsGirls IZUMO スポンサーLT
16bitidol
0
200
生成AI時代のコンポーネントライブラリの作り方
touyou
1
290
Azure AI Foundryではじめてのマルチエージェントワークフロー
seosoft
0
200
リバースエンジニアリング新時代へ! GhidraとClaude DesktopをMCPで繋ぐ/findy202507
tkmru
3
960
DMMを支える決済基盤の技術的負債にどう立ち向かうか / Addressing Technical Debt in Payment Infrastructure
yoshiyoshifujii
3
410
AI時代のソフトウェア開発を考える(2025/07版) / Agentic Software Engineering Findy 2025-07 Edition
twada
PRO
99
37k
Featured
See All Featured
The Straight Up "How To Draw Better" Workshop
denniskardys
235
140k
Producing Creativity
orderedlist
PRO
346
40k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.7k
Side Projects
sachag
455
42k
GitHub's CSS Performance
jonrohan
1031
460k
Practical Orchestrator
shlominoach
189
11k
How to Ace a Technical Interview
jacobian
278
23k
[RailsConf 2023] Rails as a piece of cake
palkan
55
5.7k
Balancing Empowerment & Direction
lara
1
450
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
Rebuilding a faster, lazier Slack
samanthasiow
83
9.1k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
45
7.5k
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