Back to feed
Dev.to
Dev.to
6/18/2026
Code Review Gone Wrong

Code Review Gone Wrong

Short summary

An engineer shares a turning point: moving from harsh code reviews to constructive feedback. Key techniques: sandwich method (positive-constructive-positive), critiquing behavior not the person, and regular follow-up. Psychological safety and ongoing dialogue drive team morale and outcomes.

  • Harsh feedback without context created defensiveness and team friction
  • Sandwich method plus behavior-focused critique builds psychological safety
  • Treating feedback as ongoing dialogue, not one-time events, strengthens collaboration

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more