Effective Code Review Requires Annotation and Documentation

10 May 2022 by Phillip JohnstonA common developer complaint regarding code reviews is “I spend a lot more time figuring out what the code is supposed to be doing instead of finding actual defects.” This statement is a bit ironic, because it is one of the primary things we focus on as reviewers – especially as consultants who are hopping in and out of code bases that we are unfamiliar with. If a reviewer cannot figure out what a piece of code is supposed to be doing during a review, that is a defect! Anyone on the team should be …

To access this content, you must purchase a Membership - check out the different options here. If you're a member, log in.