It's Dangerous to Go Alone: Battling the Invisible Monsters in Tech
summary
Claim: imposter syndrome makes competent developers underestimate themselves, causing missed jobs, avoided talks and open source, poor pairing, and burnout. Evidence: recruiter outreach after five lost years, nine months at Google after a long delay, a year and a half of unsustainable overwork and a month-long recovery with support. Concrete tools: build a party for honest feedback, track measurable progress and swap subjective doubts for data, fake it till you make it with small public steps, and avoid hostile geniuses who undermine confidence.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:47Design patterns Software craftsmanship
- 2:19SELECT- 1. ISSUES 2. TOOLS
- 2:53coding involves regular failure
- 3:45Impostor Syndrome can impact anyone
- 5:03I'm not a good programmer
- 12:55BURNOUT
- 15:33Track Measurable Progress
related talks
46mImposter Syndrome: Overcoming Self-Doubt in Success
33mKeynote: Julie Pagano
55mImposter Syndrome: Overcoming Self-Doubt in Success
51mImpostor syndrome in Tech
38mTips to Fight Impostor Syndrome
30mCode, Confidence & Conquering Self-Doubt: Breaking Impostor Syndrome in Tech
19mFeeling like a better developer (AKA overcoming impostor syndrome)
47mImposter Syndrome: Overcoming Self-Doubt in Success