One developers journey to fight the Imposter Syndrome
summary
Starts a local meetup to force learning, then moves countries, publishes books and organizes ngVikings; uses concrete practices like Codewars, Cyber Dojo and doing project-based play to gain skill. Calls out tooling and concepts (webpack, Docker, regex trainers), quantifies mastery as roughly 15,000 hours, and recommends automation, TDD mindset and the Boy Scout rule for code hygiene. Counsels pacing to avoid burnout, practicing communication and code review, and treating impostor feelings by tracking competence stages and being deliberately kind to oneself.
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
38mBe the best You - One developers journey to fight the Imposter Syndrome
37mTips To Fight Impostor Syndrome
30mMaybe I shouldn't be a programmer
48mFrom Zero to Hero with several years of Anguish - Bursting through barriers
30mCode, Confidence & Conquering Self-Doubt: Breaking Impostor Syndrome in Tech
38mTips to Fight Impostor Syndrome
19mFeeling like a better developer (AKA overcoming impostor syndrome)
28mIt's Dangerous to Go Alone: Battling the Invisible Monsters in Tech