Project Fear
summary
Defines “project fear” as imposter feelings plus loss of control, illustrated by a migration that integrates 15 APIs on a tight budget and a late QA crunch with 18 outstanding items, causing near–job hunting panic. Diagnoses causes: onboarding ambiguity, too much or too little autonomy, stress, and competence stages; gives benchmarks—three months to be competent, six months a milestone, year for mastery—and costs turnover at about $50,000. Prescribes concrete fixes: mentorship, written documentation, show-your-work retrospectives, share responsibility, and “fake it till you make it.”
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:02FEARnet
- 3:05Starting an Instrument
- 3:49Imposter Syndrome
- 7:37Whos affected
- 9:03Can you relate
- 10:02How it manifests
- 11:33Low value work
- 12:46Job hopping
- 14:40Onboarding
- 16:55Stages of Competence
- 19:24Too Much Autonomy
- 20:03Stress
- 21:43Project Life Cycle
- 23:03Lightbulb Moment
- 24:30Coping
- 25:34Empathy Spectrum
- 27:01Show Your Work
- 30:07Peers
- 30:43Empathy
- 31:33Pump yourself up
related talks
46mImposter Syndrome: Overcoming Self-Doubt in Success
25mFear and (Self) Loathing in IT...
31mImposter No More...
28mIt's Dangerous to Go Alone: Battling the Invisible Monsters in Tech
48mImposter Syndrome: Overcoming Self-Doubt in Success
44mFear of Programming
09mThe industry of imposters
18mImposter Syndrome