Code Reviews: That's a Great Idea!

We all know that code reviews are beneficial. We’ve been told time and time again that they should be part of our development process. But – like most best practices – a practical implementation is challenging (and time consuming). Your team is convinced they are a great idea. You’ll have an opportunity to squash bugs in the least costly of development times, learn new things from your talented teammates, and build a stronger foundation of trust. Awesome. Everyone is on board. But now what? What tools are out there? What are you actually looking for? How often should the reviews happen? What about bias?

In this talk, you’ll get a practical guide to making code reviews effective. Whether you’re the reviewer or reviewee: there are ways to make sure this really is a great idea.

Comments

Comments are closed.

Kristen Kinnear-Ohlmann at 14:48 on 9 Mar 2019 (via Web2 LIVE)

Loved this talk - thoroughly covered the human aspects of code reviews. I feel confident to try this!

Eugen Neuber at 14:56 on 9 Mar 2019 (via Web2 LIVE)

A very good guide to introduce code reviews into a team!
I'd like to share this talk with colleagues and friends. Also your thoughts about "General Negative/Positive Feedback" made me think...

Steve Grunwell at 15:02 on 9 Mar 2019 (via Web2 LIVE)

Another fantastic talk, full of great, actionable advice for implementing effective code reviews on your team. I lol'd. I cried. I lolcried.

Ashley Ohlrogge at 15:35 on 9 Mar 2019 (via Web2 LIVE)

Great speaker, lots of good ideas and suggestions for starting to do code reviews.

Michael Lehmkuhl at 21:48 on 9 Mar 2019 (via Web2 LIVE)

I appreciated the coverage of potential best practices and pitfalls in the realm of code reviews, especially among a tight knit and passionate team.

Thanks for delving into the nuance and avoiding a one-size-fits-all prescription.

Ian Littman at 23:02 on 9 Mar 2019 (via Web2 LIVE)

lgtm, ship it

In all seriousness, the detailed, actionable information that you packed this talk with validated my experiences on one hand and called to mind a few things that I hadn't properly considered before when doing, or receiving, code reviews. Nicely done.