Must Have 10+ Years People Experience
summary
Claim: interpersonal problems beat technical ones for messiness, so a list of eight failure modes maps to concrete fixes like empty your cup, the wide game question routine, and a set of Hacker School rules (no well actually, no backseat driving). Examples: a sponsored cohort reaches about 40% women; a year‑long OneUp practice produces dozens of open source releases and sustained contribution rhythms. Also taught: say sorry (acknowledge, apologize, learn), offer to help, and tweet a thank you.
AI-written summary · about
chapters (49)
- 0:00Intro
- 0:41How many people are in here
- 1:17About the Ruby community
- 1:46Manifesto for Software Craftsmanship
- 2:00Meeting People
- 2:23Working Hours
- 3:00WorkLife Balance
- 3:34Problem Solving
- 6:13River Community
- 7:17Apprenticeship Patterns
- 8:40Beginners Mind
- 9:29Lessons Learned
- 10:34Why Did This
- 11:11Ask Questions
- 11:35Empathy
- 12:30Missed Idea
- 12:59Ask Genuine Questions
- 13:34Rules
- 13:54No Saying Well
- 14:15No Painting
- 14:25Backseat Driving
- 14:36No Sexism
- 15:01Listening
- 15:26Talking
- 16:25People are bad
- 17:00Interruptions
- 17:33Respect
- 18:29Community
- 19:56Camp
- 20:34Disrespect
- 21:29Helping Others
- 21:59Mistakes
- 22:49Intention
- 23:31What people fail gracefully
- 23:59Some things cant be fixed
- 24:29Its like making ice
- 24:47Im sorry
- 24:58Make amends
- 25:26Audience Participation
- 25:38Thank You
- 27:36Only One More
- 28:16Gene Is Hard
- 30:01Bear With Me
- 30:31Poop Icons
- 30:44Mentoring
- 31:21Community Response
- 31:49Mentor
- 32:53Hacker School
- 33:26Big Day
related talks
40mCorporate Success: The Unwritten Curriculum
24mHow to Fail Successfully
31mFail Early, Fail Often, Fail Well
37mFailing Well: A Practical Guide to Growth for Technical Writers
10mThe Success of Failure
22mChoosing Failure
44mBridging the Gap
42mKeynote: Five Skills to Force Multiply Your Technical Talent