The effects of destructive criticism in code review
summary
Study uses an online questionnaire with vignette-style code-review scenarios and compares constructive versus destructive wording. Main claim: destructive criticism is often judged valid but not helpful, it lowers motivation to continue on the task or project and harms retention — women report larger drops and less-experienced developers are likelier to apologize. Survey finds 22% received inconsiderate feedback in the last year while 1% admitted giving it, suggesting awareness gaps and a need for feedback pathways and context-sensitive review norms.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:20Software Code Review
- 1:13Method - Online Questionnaire
- 2:00Perceptions of criticism
- 2:59Motivation to continue working
- 3:59Demographic differences
- 5:20Frequency of Destructive Criticism
- 6:08General opinions on destructive criticism
- 7:33Implications
related talks
19mUnlearning Toxic Behaviors in a Code Review Culture
15mCorrections and Constructive Criticism
30mCode Reviews Using Art Critique Principles
22mThe truth about code reviews
09mThe Art of Giving and Receiving Code Reviews Gracefully
15mThe Risks of Code Review
45mCracking the Code Review
41mSelf-critique of the Kind Code Review
