Be the best You - One developers journey to fight the Imposter Syndrome
summary
Claims that impostor syndrome hits everyone and that progress comes from practice not pep talks; concrete prescriptions include studying acronyms, pairing, writing tests first (TDD), automating repetitive work and deleting unused code. Examples name getify and Sean Larkin, cite 15,000 hours (≈5.1 years) to master a tool, and map a four stages of competence path from clueless to ninja. Practical tool mentions include webpack and Docker, Codewars and cyber-dojo exercises, and measurable wins like launched meetups, books published and speaking internationally.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:40DEVELOPERS COME IN ALL SHAPES AND SIZES
- 5:07LET'S TALK ABOUT USERS :
- 7:53Punchline learn who your users and let that guide your software
- 8:13OUR JOB IS HARD
- 16:52BE MINDFUL OF BURNOUT
- 18:53WHAT IS THE IMPOSTER SYNDROM?
- 21:35BATTLING THE IMPOSTER SYNDROM
- 21:48THE FOUR STAGES OF COMPETENCE
- 25:12Ask for feedback on code and written pieces
- 26:13HOW DO I PRACTICE?
- 28:08Caution, don't become an EXPERT BEGINNER.
- 28:48Deepen your knowledge, learn something new everytime you practice
- 29:51THINK BEFORE YOU CODE
- 31:58Code is simpler than people, who agrees?
- 34:41You have to believe you can learn anything
- 34:55You have to believe you can solve any problem
related talks
38mOne developers journey to fight the Imposter Syndrome
38mTips to Fight Impostor Syndrome
37mTips To Fight Impostor Syndrome
19mFeeling like a better developer (AKA overcoming impostor syndrome)
30mCode, Confidence & Conquering Self-Doubt: Breaking Impostor Syndrome in Tech
25mOvercoming imposter syndrome
39mOvercoming imposter syndrome
24mImpostor syndrome, am I suffering enough to talk about it?