RE: Code reviews

["Parten, Martie" <martie.parten@corp.bellsouth.net>]

The answer, IMHO, is a resounding YES!

I've seen too many unmaintainable incomprehensible conglomerates of lousy
code done by a single programmer. It doesn't take an in depth knowledge of a
project to detect bad coding standards and if someone else can't follow the
logic of the code, then there's probably a problem. Anyone who doesn't want
a code review is the person who needs it most.

-----Original Message-----
From: Minor, Eric [mailto:Enm6@cdc.gov]
Sent: Tuesday, August 14, 2001 6:24 PM
To: ajug-members@www.ajug.org
Subject: Code reviews



 This question is directed towards Project Managers, Team team leaders, but
all input is welcome.

First off, I realize the importance of doing code reviews for quality
assurance and  code efficiency.

But when is it warranted? Should programmers working on different projects
who have absolutely no clue 
as to the logic, design of someone else's project review the code for that
project? 

Would it be necessary for very small projects that requires only one
developer?

Certainly, it is a benefit for large scale projects with 3 or more
programmers.


Eric D. Minor
System Analyst III
404-498-0692