NorDevCon2020 Day 2 - Part 8 - James Seconde
summary
Argues that tool shaming (mocking languages, frameworks or IDEs) damages hiring, retention and cross-team collaboration, with concrete examples: being told “WordPress developers aren’t developers,” Zend → Symfony → Laravel churn on one developer’s path, and a GitHub star disparity (Fabien 22,800 vs an anonymous critic ~7) used to show unequal weight of critique. Quantifies waste: a three‑hour tabs‑vs‑spaces fight costs roughly £200–£300 in developer time. Proposes pragmatic fixes like nudge theory (opt‑out defaults) and kinder, tool-focused — not person-focused — feedback.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 5:15Impostor Syndrome
- 8:30Quote of the Day
- 10:47Tech Elitism
- 12:46Imposter Syndrome
- 14:35What contribution have they given back
- 17:28What isnt too shaming
- 18:32What problems does it cause
- 20:04Limit your talent
- 22:12Talk shaming
- 24:12What can be done
- 27:42The math
- 28:39Who cares
