Blog

Why Do Code Review and What Does It Actually Find? From Bug Hunting to Knowledge Sharing

The main output of code review is not bugs but code that stays understandable and knowledge that spreads through the team: only 14 percent of 570 review comments studied at Microsoft were about defects, and the largest group was code improvements. The post covers the Microsoft and Google studies, the four goals of review, alternatives such as pair programming and Ship/Show/Ask, and the Bookstore team's review agreement kept in the repository.