Code reviews are not about catching bugs; code reviews are tools for your entire team to understand the changes being made to your codebase. This talk will cover some best practices on when code reviews should be done (spoiler alert: always!), what the author should be providing in the code review, and what you can do to make sure that both you and the author get the most out of the review. Finally we'll discuss things that aren't part of the review process.

Comments

Please login to leave a comment

Ralf Jahr at 12:41 on 26 Oct 2024

Thanks for the great talk. This was a good overview of the topic and I would like to show these slides to my team. Also thanks for moderating the discussion
afterwards, also very interesting.

Great talk with good discussion at the end. Presented well, and covered the tricky aspects around Code Reviews. Good opinions sprinkled around.

Ian Littman at 14:42 on 26 Oct 2024

Would be a 5* if it had hit 45 minute length. Material was solid, and you provided further context when answering questions that comes from experience of actually doing the work. For future editions of this talk building answers to those questions into the slides should land this at just about the right length, so I figure this will hit 5* the next time I see it.

Lane Staples at 13:38 on 27 Oct 2024

Really valuable talk. The tail end turned into a bit of a round-table discussion, which I think is valuable, but also I think could've been better if either intentionally incorporated into the flow of the talk or intentionally side-stepped by expanding the talk with more anecdotes from personal experience. Regardless, great talk that provides solid benefit for tech teams.