On the surface, the idea of code review is a no-brainer: why *wouldn't* we want a second set of eyes on our code, especially before deploying to production?

As we peel back the layers, however, we find that the topic of code review is much more nuanced. How detailed should the review be? Who is qualified to perform the review (hint: it's not just senior developers)? Can we afford to take another developer away from their project to review this one? What steps can we take to ensure reviews are constructive, rather than demoralizing?

Attendees will gain deeper insight into some of the arguments for and against systemic, peer code review, as well as pick up some useful tools to make code review a natural part of their teams' workflow.

Comments

Please login to leave a comment

Great talk and full of good ideas/options to bring back to my team.

Thanks for the talk. I love the idea of "Atomic PRs".

s w at 22:38 on 22 May 2025

Fabulous talk. The tips shared are incredibly valuable for any team looking to improve cohesiveness for contributors and good conduct that means everything at the end of the day.