Part 1 Code review foundations

 

Hey there! You’re here either because (a) you want to learn about this thing called code reviews, (b) you’re in desperate need of redoing your existing process, or (c) you know your code reviews are OK but are looking to make them better, or (d) you really like to learn and have good taste in technical books figure—maybe you’re reason (e) and you just appreciate the awesome book title figure. Regardless of the reason, the first part of the book will make sure you have a good foundation on code reviews, at least the way we’ll be talking about them in this book!

Chapter 1 will introduce you to the importance of code reviews, why you should want them, how to convince your team to want them too, and lay out how the rest of this book is structured. Feel free to reference this chapter when you want to skip to certain topics.

Chapter 2 delves deeper into the basic components of the code review; by the end of this jam-packed chapter (that I encourage you to take in strides), you’ll understand what types of code review systems there are and what the main parts of a code review are, describe what a pull request is and how to create a fantastic one, and know who participates in the code review and what their specific obligations are.