Maybe I shouldn't be a programmer
summary
Imposter syndrome shows up as concrete failures and environment friction: theory != application, unfamiliar stacks (Node promises and testing promises), and complex daily setup like Vagrant+Elasticsearch+Redis+Cassandra plus VPN, AWS and manual SQS messages. Code review dynamics, git mistakes (learned the hard way: rebase vs force push), and missing small on‑site rituals cause despair; one developer contemplates quitting for weeks, another with 15 years leaves after tooling mismatch. Solutions: mentors, meetups, Slack, OSS and conferences to rebuild confidence.
AI-written summary · about
chapters (20)
- 0:00Intro
- 4:00Learning vs Work
- 4:43Work Environment
- 7:55Work Workflow
- 9:38Learning Opportunities
- 10:27Picking on me
- 12:35Code reviews
- 15:00Flaws
- 16:09How could I be better
- 16:50Find a mentor
- 18:21Work with senior developers
- 19:09Regular feedback meetings
- 19:20Finding mentors
- 20:14Meetups
- 21:17Conferences
- 22:37Slack IRC
- 23:32Write a blog
- 24:17Contribute to open source projects
- 25:54Be part of the community
- 28:37You can be anonymous
related talks
38mOne developers journey to fight the Imposter Syndrome
28mIt's Dangerous to Go Alone: Battling the Invisible Monsters in Tech
46mImposter Syndrome: Overcoming Self-Doubt in Success
51mThe Psychology of Code
32mImposter Syndrome Ain't Just a River in Egypt- 38mBe the best You - One developers journey to fight the Imposter Syndrome
27mImposter syndrome, overworking, and working environments
39mOvercoming imposter syndrome