-
Be the first to like this
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
This phrase can stir up a lot of emotions for people. For some, it's aggravation because they're a waste of time, for others, it's stressful because it feels like you're getting a review. However, for some, it's a great learning experience that leads to the team improving. Do you want to be in the latter group? Then this talk is for you!
In this presentation, I'll first show you the benefits of code review and the business case for why they should happen. Next, I'll show some of the most common mistakes that teams make during the review process and how to mitigate them. After talking about the bad, we'll talk about what to look for in your code review process. Finally, I'll wrap things up by showing the game plan I use for code reviews.
Intended for developers of all levels, attendees will leave understanding the reasons why we should have code reviews, signs of bad reviews, signs of good reviews, and have a starting template.
Be the first to like this
Be the first to comment