You open a pull request. Ten comments later, you’re wondering whether the code is the problem… or the reviewer.

This talk is a set of real stories from Java teams working on long-lived codebases. Stories about reviews that went wrong: reviewers rewriting code they didn’t fully understand, endless debates about “best practices,” frustration over legacy decisions no one remembers making. Not because people were bad developers, but because working together on old code is hard.

More importantly, these stories show how things can get better. How teams learned to use code reviews to build trust instead of tension, to share context instead of blame, and to improve quality without burning people out.