>

>“The purpose of a code review is not, as you might first assume,
>to find bugs. That’s what Quality Assurance does. A code review
>performs three other functions:
>
>Sharing techniques between developers
>Encourage proper coding practices
>Encourage developers to write maintainable code”
>- Whil Hentzen
>The 1999 Software Developer’s Guide
>

>
>Take a look at this book. It has some guidelines on how to do code reviews. In general each team does them different, depending on a lot of factors.
>
>We don't review all code on each project. We pick relevant pieces of each system and put them through code review. For example, a complex form or report, the main calculate process in a system, and so on.
>
>Code reviews are great for novice and senior developers. It's amazin how much people learn they didn't know during a code review. More than once we've had developers say to each other "Why did you write these 100 lines of code when there is a function in VFP/VMP/Other that does the the job?!" :)
>


Thanks we have this book I haven't read it yet, but will look at that chapter.