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
Learning to Fail
Search
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
sdehaan
January 27, 2012
Programming
3
420
Learning to Fail
Talk about team culture, learning to fail and making it an asset to your team's goals.
sdehaan
January 27, 2012
Tweet
Share
Other Decks in Programming
See All in Programming
360° Signals in Angular: Signal Forms with SignalStore & Resources @ngLondon 01/2026
manfredsteyer
PRO
0
120
なぜSQLはAIぽく見えるのか/why does SQL look AI like
florets1
0
450
それ、本当に安全? ファイルアップロードで見落としがちなセキュリティリスクと対策
penpeen
7
2.4k
【卒業研究】会話ログ分析によるユーザーごとの関心に応じた話題提案手法
momok47
0
190
登壇資料を作る時に意識していること #登壇資料_findy
konifar
4
980
AI & Enginnering
codelynx
0
110
Basic Architectures
denyspoltorak
0
660
「ブロックテーマでは再現できない」は本当か?
inc2734
0
650
AI巻き込み型コードレビューのススメ
nealle
0
130
AWS re:Invent 2025参加 直前 Seattle-Tacoma Airport(SEA)におけるハードウェア紛失インシデントLT
tetutetu214
2
100
OCaml 5でモダンな並列プログラミングを Enjoyしよう!
haochenx
0
140
humanlayerのブログから学ぶ、良いCLAUDE.mdの書き方
tsukamoto1783
0
180
Featured
See All Featured
Marketing Yourself as an Engineer | Alaka | Gurzu
gurzu
0
130
世界の人気アプリ100個を分析して見えたペイウォール設計の心得
akihiro_kokubo
PRO
66
36k
Jamie Indigo - Trashchat’s Guide to Black Boxes: Technical SEO Tactics for LLMs
techseoconnect
PRO
0
55
A Tale of Four Properties
chriscoyier
162
24k
Designing for humans not robots
tammielis
254
26k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
508
140k
GraphQLの誤解/rethinking-graphql
sonatard
74
11k
The Organizational Zoo: Understanding Human Behavior Agility Through Metaphoric Constructive Conversations (based on the works of Arthur Shelley, Ph.D)
kimpetersen
PRO
0
240
Code Review Best Practice
trishagee
74
20k
Speed Design
sergeychernyshev
33
1.5k
Claude Code どこまでも/ Claude Code Everywhere
nwiizo
61
52k
Making Projects Easy
brettharned
120
6.6k
Transcript
Learning to Fail Friday, January 27, 2012
Open source software to improve the lives of people living
in poverty. Friday, January 27, 2012
— Friday, January 27, 2012
Africa 1 billion people 500 million phones Friday, January 27,
2012
25 Botswana 26 Zwaziland 18 South Africa 24 Lesotho Africa
People hardest hit by HIV/AIDS are also those least likely to have access to relevant information. Friday, January 27, 2012
Friday, January 27, 2012
FAIL Friday, January 27, 2012
Hindsight is a luxury. Friday, January 27, 2012
5 years of growing pains. Friday, January 27, 2012
0 6 12 18 24 30 36 Patients Not Returning
Before After Friday, January 27, 2012
How hard can it be? Friday, January 27, 2012
Deceptively simple. Lack of ownership. Being too clever. Friday, January
27, 2012
What is it we’re building? Friday, January 27, 2012
Friday, January 27, 2012
One hammer to rule them all. Friday, January 27, 2012
Hit scaling issues hard & fast. Friday, January 27, 2012
Commitment issues. Friday, January 27, 2012
800,000+ Uniques Friday, January 27, 2012
0 25000 50000 75000 100000 June 2010 October 2010 May
July Sept Nov Friday, January 27, 2012
Architecture prevented efficient caching. Friday, January 27, 2012
Metrics killed the site. Friday, January 27, 2012
Mild tunnel vision. Slight frameworkitis. Friday, January 27, 2012
Everything breaks at scale. Friday, January 27, 2012
Team Culture Implications Friday, January 27, 2012
You reproduce what you are. Friday, January 27, 2012
“Organizations which design systems are constrained to produce designs which
are copies of the communication structures of these organizations” – Melvin Conway Friday, January 27, 2012
A software system will reflect the social structure of the
organization that produced it. Friday, January 27, 2012
Failures are to be expected. Friday, January 27, 2012
Focus on small teams, few organizational layers. Friday, January 27,
2012
Introduce small changes. Minimize risk. Friday, January 27, 2012
Ship all the time. Friday, January 27, 2012
Avoid organizational silos, reduce bus factors. Friday, January 27, 2012
Trust, Cooperation & Transparency. Friday, January 27, 2012
Emphasize learning, code reviews & shared responsibility Friday, January 27,
2012
Team communication tools are vital. Friday, January 27, 2012
Kill your darlings. Embrace change. Friday, January 27, 2012
Broken gets fixed but shitty lasts forever. Friday, January 27,
2012
Technical Implications Friday, January 27, 2012
Queue everything and delight everyone. Friday, January 27, 2012
Automate everything. Friday, January 27, 2012
Continuous Integration Friday, January 27, 2012
Code reviews. Friday, January 27, 2012
Make deploys easy. Friday, January 27, 2012
Metrics should be cheap. Friday, January 27, 2012
Failing adds value. Friday, January 27, 2012
Thanks. Friday, January 27, 2012
Thanks. Friday, January 27, 2012
@smn http://github.com/praekelt Friday, January 27, 2012