Part 3 Dealing with dilemmas

“This review will be at least a week; we only have one Senior Developer.”

“What’s the point of this process if Ralph doesn’t have to go through it?”

“Review? We don’t have time. This is an emergency!”

After a code review process has been established, these words have all been uttered in the years that followed. Teams change. Goals shift. Projects evolve. Through all the transformation, code reviews can become lackluster or morph into something you had never intended: an ineffective process your team no longer follows or enjoys. This part of the book talks about the very real dilemmas you might face once you’ve been using your code review process for some time.

Chapter 7 eases you into the types of code reviews you want to avoid. Chapter 8 talks specifically about lengthy code reviews; chapter 9 digs into process loopholes. Both chapters 8 and 9 guide you through the different conundrums your own team might face and what to do about them (or how to stop and prevent them entirely).