Code reviews continue to be a point of contention in our industry. Some teams have adopted code reviews wholeheartedly while others have nearly outlawed the practice. Other teams think they "should" do reviews, but they treat them as a formality or a rubber-stamp.

But we have great data that show code reviews work. So what is the gap?

I believe it's because most engineers were never taught how to effectively review code.

Even more so, many teams don't know how to manage the process to know if they are actually getting value or if they are just rubber-stamping code.

This book will help engineers and teams build the skills necessary to become code review champions!