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
- Use Eclipse's Change Sets to define small atomic units of change. Try to keep the units small, but not meticulously small.
- Write good check in comments. Ideally, develop a standard on what goes into these comments.
- Open eclipse's snchronize view.
- Click synchronize to see the files that changed.
- Enable Change sets and view the authors/comments of the checked in code.
- 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!
One part of code review is giving the feedback.
ReplyDeleteWould be great if you are willing to share how you do that.
I rarely find code reviews useful and the only one I consider beneficial are informal one, but I do prefer paring with teammates. The formal review tends to focus on a stuff, that can could be done automatically with a continuous integration, the same applies to coding standard. Much better, faster and cheaper :D
ReplyDelete