Until they learn how to do effective code reviews, many developers write programs as fast as they can and immediately compile and test them.
///The compiler then leads them from one problem to the next.
//When programs have compile defects they almost certainly have test defects.
//If the first test doesn't find defects, the developers will likely declare victory and ship.
// Then all of the program's remaining defects must still be found, either in system testing or by the user.
//That is when finding defects becomes truly expensive.
//Reviewing a program is like reviewing a draft paper.
//Professional writers will tell you that the secret of good writing is rewriting.
//Writing good program is much the same.
//Few programmers can write a perfect program on the first try.
//Many waste a lot of time compiling and testing a defect-prone first draft.
//Even after all this work, they still produce program with numerous patches and many remaining defects.