Performing regular code reviews can be a real benefit to small and large development teams for several reasons. First, you can spot coding defects and logical errors before QA finds them. You’ll have a much easier (and quicker) time fixing a defect found via a code review than through testing. Second, it’s everyone’s opportunity to check that the new code meets whatever coding standards or naming conventions you’ve set for the team or project. Finally, there’s no easier way to rapidly educate the other developers on your code changes especially if you add some simple comments.Code reviews don’t have to be laborious or require meetings. I use Eclipse/CVS to help me with this task. Here is the basic process.

On checking in code

1. Use Eclipse’s Change Sets to define small atomic units of change. Try to keep the units small, but not meticulously small.
2. Write good check in comments. Ideally, develop a standard on what goes into these comments.

To do the code review

1. Open eclipse’s snchronize view.
2. Click synchronize to see the files that changed.
3. Enable Change sets and view the authors/comments of the checked in code.
4. Clicking on an individual file will open eclipse’s diff tool. From there, you can now see all the code segements that were modified.

That’s pretty much it. It’s not fancy, but it works!