The Psychology of Code
summary
Survey finds 80% admit imposter syndrome; common failures are sunk‑cost attachment to prototypes and endless bike‑shedding over brackets, imports and naming. Practical fixes: embed formatting and checks in editor/CI, use OpenRewrite and IDE inspections to remove low‑value debates, invest in platform teams to unblock stream‑aligned teams and aim for 2‑pizza (~7) team size. Beware metric gaming: one codebase shows 87% coverage achieved by 2,000‑line test fakes, 67 mocks and zero asserts. Onboarding by pairing for months and scheduled “sharpen the axe” learning days work.
AI-written summary · about
chapters (20)
- 0:00Imposter syndrome in tech
- 4:26Code attachment and sunk cost
- 9:03Bike shedding pitfalls
- 11:10Continuous learning importance
- 14:23Junior to T-shaped developer
- 16:30Challenges of team lead
- 18:38Empathy for leadership
- 20:44Psychological safety culture
- 23:52Onboarding with pair programming
- 24:54Fear of failure and paralysis
- 26:40Legacy code morale
- 29:53Team size and communication
- 32:39Developer motivation drivers
- 34:03Team topologies and platforms
- 37:14Stream-aligned teams autonomy
- 40:23Feature vs component teams
- 43:32Architect roles: enforcer vs enabler
- 45:40Cobra effect in software
- 46:21Blind metrics dangers
- 48:11Recap and key takeaways
related talks
52mKeynote: The Psychology of Code
47mThe Psychology of Software Teams
43mKicking Imposter Syndrome in the Head
54mDev psychology: your own brain is your worst enemy
30mMaybe I shouldn't be a programmer
43mDebugger for developers
30mCode, Confidence & Conquering Self-Doubt: Breaking Impostor Syndrome in Tech
38mDebugger; for Developers