Code Review Best Practices

We know that Code Reviews are a Good Thing. We probably have our own personal lists of things we look for in the code we review, while also fearing what others might say about our code. How do we ensure that code reviews are actually benefiting the team, and the application? How do we decide who does the reviews? What does "done" look like? In this webinar recording, Trisha identifies some best practices to follow. She talks about what's really important in a code review and sets out some guidelines to follow in order to maximize the value of the code review and minimize the pain. 0:00 Introduction: Reading other people's code is hard 5:21 What to look for in a code review 6:37 Different code review workflows 8:42 One Size Does Not Fit All 9:01 Code Review anti-patterns 18:49 Why perform code reviews? 23:07 When do you review code? 24:37 Who is involved in the review? 26:39 Audience questions 31:36 Where do you perform the review? 36:53 What do you look for in a code review? 42:01 How do you perform the review? 51:26 Summary 53:40 Audience Questions About the Presenter Trisha Gee has developed Java applications for a range of industries, including finance, manufacturing, software and non-profit, for companies of all sizes. She has expertise in Java high performance systems, is passionate about enabling developer productivity, and dabbles with Open Source development. Trisha is a Java Champion and is a Developer Advocate for Upsource and IntelliJ IDEA.