a decent amount of code and call another developer over to have a look at it. The other developer sits there while the first one explains what he did, line by line. Through this narrative, the original developer notices some of his own mistakes and fixes them, and the OTS developer notices others, pointing them out to the first. They also share opinions on solutions to certain problems which the original developer will sometimes redo after the review process is done, calling for a review once again. This can also be easily done with screen sharing software and voice chat if the developers are remote. Tool-Assisted Review -- there are various tools both online and offline to assist with code review. While a detailed look at the various tools on offer is outside the scope of this article, we can generalize and say there are paid versions ( Atlassian Crucible , CodeCollaborator ), free versions ( Review Board ) or, if you're solo developer, the community version ( Stack Exchange Code Review ). Regardless of the tool used, each serves pretty much the same purpose -- it retrieves the most recent changes to source code and flags them as needing review. A peer -- that means a developer of equal or greater skill -- then reviews the code, flags it as reviewed or marks any errors that were found and makes suggestions, and either finishes or reinitiates the process by sending it back to the originating developer. It is also