How Sigmund Freud would perform a code review?
summary
Argues that code review fails from cognitive defense mechanisms and recommends concrete, testable practices: apply Kahneman’s system1/system2 and Valliant’s defense levels, avoid blaming language, and run a two-step review (author explains intent, reviewer does technical pass). Use avoid "you", use "we" phrasing, give quick show-and-tell snippets or links instead of terse comments, skip reviews on bad days, and resist cargo-cult or magpie suggestions. Notes over 30 defense mechanisms, reports gradual team improvement after two years of these changes.
AI-written summary · about
chapters (9)
- 0:00Start
- 14:53PERSONALITY DEFENCE MECHANISMS
- 17:30PATHOLOGICAL
- 18:57IMMATURE
- 21:01NEUROTIC
- 23:57WHAT TO DO?
- 28:15AND OTHER DIRTY ERISTIC STRATEGIES
- 41:47KEY TAKEOUTS
- 43:18BIBLIOGRAPHY
related talks
18mHow To Review Someone's Code While Not Being A Jerk!
19mUnlearning Toxic Behaviors in a Code Review Culture
20mConducting Humane Code Reviews
15mThe Risks of Code Review
43mVitaly Sharovatov: From Astrology to Code Reviews
45mCracking the Code Review
46mCode Review: We Didn't Come Here to Suffer!
01h 01mBetter Code Reviews FTW!
