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
You Have Control
Search
Andrew Godwin
June 04, 2018
Programming
0
560
You Have Control
My keynote from PyCon Israel 2018.
Andrew Godwin
June 04, 2018
Tweet
Share
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
230
Django Through The Years
andrewgodwin
0
130
Writing Maintainable Software At Scale
andrewgodwin
0
370
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
280
Async, Python, and the Future
andrewgodwin
2
570
How To Break Django: With Async
andrewgodwin
1
620
Taking Django's ORM Async
andrewgodwin
0
640
The Long Road To Asynchrony
andrewgodwin
0
560
The Scientist & The Engineer
andrewgodwin
1
650
Other Decks in Programming
See All in Programming
Kotlin 2.0が与えるAndroid開発の進化
masayukisuda
1
410
エラーレスポンス設計から考える、0→1開発におけるGraphQLへの向き合い方
bicstone
5
1.5k
Rubyとクリエイティブコーディングの輪の広がり / The Growing Circle of Ruby and Creative Coding
chobishiba
1
270
Perl 5 OOP機構30年史 - Perl 5's OOP Mechanism over the past 30 years
moznion
0
250
LangChainでWebサイトの内容取得やGitHubソースコード取得
shukob
0
160
実践!難読化ガイド
mitchan
0
200
KSPの導入・移行を前向きに検討しよう!
shxun6934
PRO
0
280
The Shape of a Service Object
inem
0
520
サーバーレスで負荷試験!Step Functions + Lambdaを使ったk6の分散実行
shuntakahashi
6
1.6k
RAGの回答精度評価用のQAデータセットを生成AIに作らせた話
kurahara
0
250
LangChainの現在とv0.3にむけて
os1ma
4
920
Hono・Prisma・AWSでGeoなAPI開発
nokonoko1203
5
680
Featured
See All Featured
Why You Should Never Use an ORM
jnunemaker
PRO
53
8.9k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
326
21k
Optimising Largest Contentful Paint
csswizardry
30
2.8k
What's new in Ruby 2.0
geeforr
340
31k
A designer walks into a library…
pauljervisheath
201
24k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
36
2.1k
How to Think Like a Performance Engineer
csswizardry
16
960
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
28
1.6k
Into the Great Unknown - MozCon
thekraken
29
1.4k
A Philosophy of Restraint
colly
202
16k
The Brand Is Dead. Long Live the Brand.
mthomps
53
38k
Design by the Numbers
sachag
277
19k
Transcript
None
Hi, I’m Andrew Godwin • Django core developer • Senior
Software Engineer at • Private + Instrument pilot
Content Warning
Software is difficult.
By Derek Lowe "Things I won't work with"
On Hexanitrohexaazaisowurtzitane "...a more stable form of it, by mixing
it with TNT. Yes, this is an example of something that becomes less explosive as a one-to-one cocrystal with TNT."
On “Sand Won’t Save You This Time” "...the operator is
confronted with the problem of coping with a metal-fluorine fire. For dealing with this situation, I have always recommended a good pair of running shoes."
Unicode Locales Time Calendars Geography Money
Network latency Hardware unreliability Deadlocks Bit flips Ambiguous specifications No
documentation
We just move faster and hit them at higher speed.
Not unique to software
None
Who's solved this? Aviation.
A Boeing 747 has six million parts
…and a 0.000006% accident rate A Boeing 747 has six
million parts
Airplane Car Walking Train 220 130 30.8 Deaths per billion
hours (Per passenger, UK 1990-2000) 30
People matter as much as machines
Pilot 76% Aviation Accident Causes (2005 Nall report) 9% Other
16% Mechanical
And how we can apply them to software. Let's look
at some aviation principles
Principle #1 Hard Failure
If something is wrong it turns itself off Autopilots, engines,
air conditioning, and more
This only works if you have redundancy All of these
systems have a backup that lets you land.
"We'll ignore errors so the site doesn't crash!" "Save the
invalid data and we'll fix it later"
These are great ways to ensure you never fix something.
No accident or outage has a single cause. Stop your
code getting into odd states.
Fail hard if anything unexpected happens Validate all your data
strictly in and out Deploy changes early and often
Single points of failure can be good Only one place
to look when things go wrong!
None
Principle #2 Good Alerting
Cockpits are incredibly selective about what sets off an audio
alarm
Alert fatigue is real. Avoid at all costs.
Never, ever, put all errors in the same place
Critical Normal Background
Critical Normal Background Wakes someone up. Actionable.
Critical Normal Background Wakes someone up. Actionable. Fixed over the
next week.
Critical Normal Background Wakes someone up. Actionable. Fixed over the
next week. Metrics, not errors.
Have you been ignoring an error for weeks? Then turn
off its error reporting.
Principle #3 Find your limits
Everything will fail. You should know when.
Copyright Boeing
What's your Minimum Equipment List? What can you run the
system without?
Lavatory ashtrays Air conditioning Seatbelt signs Passenger video screens Fuel
caps Weather radar REQUIRED OPTIONAL
Did you load test? Did you fuzz test?
You don't have to perfectly scale. But you do have
to know where your limits are.
Risk is fine when you're informed! Unknowns are the most
dangerous thing.
Principle #4 Build for failure
No single thing in an aircraft can fail and take
it down.
We all want this for our code, but the way
to do it is to build for failure.
Kill your application randomly Practice server network failures Develop on
unreliable connections
The majority of pilot training is handling emergencies.
None
Use checklists. Don't rely on memory.
If you practice failure, you'll be ready when the inevitable
happens.
Pilot 76% Aviation Accident Causes (2005 Nall report) 9% Other
16% Mechanical
Principle #5 Communicate well
"You have control" "I have control" "You have control"
Complex software means separate teams.
As you grow, communication becomes exponentially harder.
None
None
None
Clear communication is vital.
Write everything down. Written specs = less time in meetings.
Have a clear chain of command.
Make decisions. They don't have to be perfect, just good
enough.
Principle #6 No blame culture
How do I know all these aviation stats?
Every incident is reported and investigated.
There is never a single cause of a problem.
Make it very difficult to do again. Why did your
software let this happen? What's the UX of your admin tools like?
None
None
Encourage reporting. Don't blame anyone for a mistake. They're unlikely
to make it again.
Reward maintenance as well as firefighting It's easy to look
good when you ship broken and are always heroically fixing it.
None
In aviation, every rule is written in blood.
Software is not yet there. But we are getting closer.
Margaret Hamilton Her error detection code saved Apollo 11
Patriot Missile Floating-point bug killed 28
Therac-25 Killed 3, severely injured at least 3 more
Uber Autonomous Vehicle Saw a pedestrian and chose to hit
her
None
Hard failure Good alerting Find your limits Build for failure
Communicate well No blame culture
Thanks. Andrew Godwin @andrewgodwin aeracode.org