Admitting that hard problems are hard
summary
Admitting ignorance carries measurable career costs: identical resumes with female names get 6–14% fewer interview invites, and resumes with Black-sounding names receive roughly 50% fewer callbacks; women also receive 1.4× more subjective criticism. Teams adopt hype tech for resumes (Kubernetes, SRE) rather than fit. Google’s multi-year study finds psychological safety — safe risk-taking and blamelessness — predicts the most effective teams. Leaders model admitting mistakes, use blameless postmortems, and cultivate a growth mindset to reduce hidden failure risk.
AI-written summary · about
chapters (23)
- 0:00Introduction and personal story
- 1:25The CTO’s impossible architecture
- 2:51Cost of admitting ignorance
- 3:56Resume driven development
- 5:43Corporate buzzword bingo
- 7:28Distributed systems aren’t easy
- 9:15Burden of understanding
- 9:59Speaker’s background
- 11:46Stereotypes and heuristics
- 13:14Systemic bias in hiring
- 14:45Stereotypes against men
- 15:51History of gender bias
- 16:55Unconscious bias in everyone
- 18:20Bias in machine learning
- 19:28Dance break
- 20:08Why speak up about ignorance
- 21:10Cost of unchecked complexity
- 22:16Software for everyone
- 23:22Psychological safety matters
- 26:33Fostering psychological safety
- 28:44Admit you don’t know
- 29:05Growth mindset over proving
- 30:27These are hard problems
related talks
01h 01mHolding Your Own: How to Overcome Gender Bias and Thrive in Tech
53mSwearing, Nudity and Other Vulnerable Positions
28mIt's Dangerous to Go Alone: Battling the Invisible Monsters in Tech
33mKeynote: Julie Pagano
41mDiversity and Inclusion in SRE: A Postmortem
44mAvoiding The “Oh S***” Moment Through Purposeful Team Building
47mCosts of the Cult of Expertise
30mYou Are Your Own Worst Critic