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
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
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
なるべく楽してバックエンドに型をつけたい!(楽とは言ってない)
hibiki_cube
0
140
ThorVG Viewer In VS Code
nors
0
760
MDN Web Docs に日本語翻訳でコントリビュート
ohmori_yusuke
0
640
インターン生でもAuth0で認証基盤刷新が出来るのか
taku271
0
190
AIによるイベントストーミング図からのコード生成 / AI-powered code generation from Event Storming diagrams
nrslib
2
1.8k
OSSとなったswift-buildで Xcodeのビルドを差し替えられるため 自分でXcodeを直せる時代になっている ダイアモンド問題編
yimajo
3
610
Data-Centric Kaggle
isax1015
2
760
LLM Observabilityによる 対話型音声AIアプリケーションの安定運用
gekko0114
2
420
フロントエンド開発の勘所 -複数事業を経験して見えた判断軸の違い-
heimusu
7
2.8k
そのAIレビュー、レビューしてますか? / Are you reviewing those AI reviews?
rkaga
6
4.5k
15年続くIoTサービスのSREエンジニアが挑む分散トレーシング導入
melonps
2
170
QAフローを最適化し、品質水準を満たしながらリリースまでの期間を最短化する #RSGT2026
shibayu36
2
4.3k
Featured
See All Featured
New Earth Scene 8
popppiees
1
1.5k
Reality Check: Gamification 10 Years Later
codingconduct
0
2k
Speed Design
sergeychernyshev
33
1.5k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
130k
4 Signs Your Business is Dying
shpigford
187
22k
Navigating the moral maze — ethical principles for Al-driven product design
skipperchong
2
240
The Hidden Cost of Media on the Web [PixelPalooza 2025]
tammyeverts
2
170
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
359
30k
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
aleyda
2
9.5k
The innovator’s Mindset - Leading Through an Era of Exponential Change - McGill University 2025
jdejongh
PRO
1
88
My Coaching Mixtape
mlcsv
0
46
Exploring the relationship between traditional SERPs and Gen AI search
raygrieselhuber
PRO
2
3.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