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
610
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
310
Django Through The Years
andrewgodwin
0
200
Writing Maintainable Software At Scale
andrewgodwin
0
430
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
350
Async, Python, and the Future
andrewgodwin
2
650
How To Break Django: With Async
andrewgodwin
1
720
Taking Django's ORM Async
andrewgodwin
0
720
The Long Road To Asynchrony
andrewgodwin
0
650
The Scientist & The Engineer
andrewgodwin
1
750
Other Decks in Programming
See All in Programming
ドメインモデリングにおける抽象の役割、tagless-finalによるDSL構築、そして型安全な最適化
knih
4
1.2k
単体テストの始め方/作り方
toms74209200
0
360
Interface vs Types ~型推論が過多推論~
hirokiomote
1
240
統一感のある Go コードを生成 AI の力で手にいれる
otakakot
0
1.5k
Haskell でアルゴリズムを抽象化する / 関数型言語で競技プログラミング
naoya
10
1.3k
実はすごいスピードで進化しているCSS
hayato_yokoyama
0
100
TypeScript LSP の今までとこれから
quramy
1
460
Cursor Meetup Tokyo ゲノミクスとCursor: 進化と制約のあいだ
koido
2
870
〜可視化からアクセス制御まで〜 BigQuery×Looker Studioで コスト管理とデータソース認証制御する方法
cuebic9bic
3
310
人には人それぞれのサービス層がある
shimabox
3
630
Rails産でないDBを Railsに引っ越すHACK - Omotesando.rb #110
lnit
1
150
機械学習って何? 5分で解説頑張ってみる
kuroneko2828
0
180
Featured
See All Featured
Bash Introduction
62gerente
614
210k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.6k
A designer walks into a library…
pauljervisheath
205
24k
How STYLIGHT went responsive
nonsquared
100
5.6k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
137
34k
The Language of Interfaces
destraynor
158
25k
Stop Working from a Prison Cell
hatefulcrawdad
269
20k
Scaling GitHub
holman
459
140k
The Power of CSS Pseudo Elements
geoffreycrofte
76
5.8k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
657
60k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
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