[AM] Code reviews preventative?
"J. B. Rainsberger" <[email protected]>
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Message-ID | <[email protected]> |
Adrian Howard wrote: > On Friday, January 30, 2004, at 08:41 pm, Randy Miller wrote: > [snip] > >> Some activities, like code reviews, are >> clearly preventative. They keep people from making mistakes. With respect, code reviews are the exact /opposite/ of preventative: they are clearly post-mortem activities. A code review happens after the code has been written. By definition, it cannot be preventative. It can only hope to reduce the likelihood of a particular class of mistake /recurring/. Pair programming is preventative: it is a code review that occurs before the code is even compiled, at a stage when the participants are actually both willing and able to make changes. -- J. B. Rainsberger, Diaspar Software Services http://www.diasparsoftware.com :: +1 416 791-8603 Let's write software that people understand For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com --^---------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h Or send an email to: [email protected] TOPICA - Start your own email discussion group. FREE! http://www.topica.com/partner/tag02/create/index2.html --^----------------------------------------------------------------