|
A critical and often overlooked component of the
development process is the code review.
Conceptually, this is very simple - each developer has
their code reviewed by one or more other developers before
checking it in. Note that pair programming generally
eliminates the need to do this, since the two developers
will be reviewing code continuously.
There are several reasons for this process, the most
important of which is to root out bugs. Other
developers will often question and catch problems, from
simple error handling or missing if-then's to complex
design issues that don't seem "quite right."
Another important outcome of the review process is
enhanced adherence to coding standards, as developers
generally chide each other to follow the rules.
Finally, group review tends to keep everyone thinking
and learning more about the system and its design.
This enhances education and cross training, allowing more
flexibility with resources.
|
|
