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
sdehaan
January 27, 2012
Programming
3
410
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
PHPコードの実行モデルを理解する / Understanding-the-PHP-Execution-Model
shin1x1
0
880
仕様と実装で学ぶOpenTelemetry
drumato
2
230
Open standards for building event-driven applications in the cloud
meteatamel
0
210
How to improve maintainability and readability of your automated tests? ( #scrumniigata )
teyamagu
PRO
1
120
Effectで作る堅牢でスケーラブルなAPIゲートウェイ / Robust and Scalable API Gateway Built on Effect
yasaichi
7
1.2k
Going beyond Apache Parquet's default settings
xhochy
0
150
TypeScriptの型とパフォーマンス (TSKaigi 2024)
ypresto
13
4.2k
Exploring Type-Informed Lint Rules in Rust based TypeScript Linters
unvalley
3
610
Try creating your own orderedmap
kazamori
1
280
Ruby on Fails - effective error handling with Rails conventions
talyssonoc
0
280
TCAとKMPを用いた新規動画配信アプリ 「ABEMA Live」の設計
tomu28
2
140
Direct Style Effect Systems The Print[A] ExampleA Comprehension Aid
philipschwarz
PRO
0
400
Featured
See All Featured
Embracing the Ebb and Flow
colly
80
4.2k
What the flash - Photography Introduction
edds
64
11k
Statistics for Hackers
jakevdp
790
220k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
221
21k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
188
16k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
323
20k
Agile that works and the tools we love
rasmusluckow
325
20k
How to train your dragon (web standard)
notwaldorf
75
5.2k
How to Ace a Technical Interview
jacobian
273
22k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
34
8.9k
Testing 201, or: Great Expectations
jmmastey
30
6.4k
No one is an island. Learnings from fostering a developers community.
thoeni
16
2.1k
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