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
420
3
Share
Learning to Fail
Talk about team culture, learning to fail and making it an asset to your team's goals.
sdehaan
January 27, 2012
Other Decks in Programming
See All in Programming
初めてのRubyKaigiはこう見えた
jellyfish700
0
400
技術記事、AIに書かせるか、自分で書くか? 〜それでも私が自分の手で書く理由〜 / #QiitaConference
jnchito
2
1.2k
正しくソフトウェアを作る、前提を疑うための認知の視点 / doubt-premise
minodriven
12
4.5k
Datadog × OpenTelemetry 入門と実践のあいだ
kn_to_maxpno
1
110
AI駆動開発勉強会 広島支部 第一回勉強会 AI駆動開発概要とワークショップ
hayatoshimiu
0
430
TypeSpec で繋ぐ複数プロダクトの型安全
maroon8021
1
310
権限チェックの一貫性を型で守る TypeScript による多層防御
mnch
4
1k
These Five Tricks Can Make Your Apps Greener, Cheaper, & Nicer
hollycummins
0
260
Modding RubyKaigi for Myself
yui_knk
0
860
CSC307 Lecture 17
javiergs
PRO
0
310
JJUG CCC 2026 Spring: JSpecify で実現する Kotlin フレンドリーな Java API 設計
ternbusty
1
130
「エンジニアインターン、どうやって取った?」準備のリアルを語るLT会 Progate BAR
akiomatic
0
110
Featured
See All Featured
Odyssey Design
rkendrick25
PRO
2
660
What’s in a name? Adding method to the madness
productmarketing
PRO
24
4.1k
GraphQLとの向き合い方2022年版
quramy
50
15k
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
aleyda
2
11k
Unlocking the hidden potential of vector embeddings in international SEO
frankvandijk
0
830
Jamie Indigo - Trashchat’s Guide to Black Boxes: Technical SEO Tactics for LLMs
techseoconnect
PRO
0
150
The Straight Up "How To Draw Better" Workshop
denniskardys
239
140k
sira's awesome portfolio website redesign presentation
elsirapls
0
270
Typedesign – Prime Four
hannesfritz
42
3.1k
Being A Developer After 40
akosma
91
590k
The #1 spot is gone: here's how to win anyway
tamaranovitovic
2
1.1k
Bridging the Design Gap: How Collaborative Modelling removes blockers to flow between stakeholders and teams @FastFlow conf
baasie
0
570
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