Re: [AM] Code reviews preventative?

"Scott E. Preece" <[email protected]>
Newsgroups gmane.comp.programming.modeling.agile
Message-ID <[email protected]>
| From: "J. B. Rainsberger" <[email protected]>
| 
| Scott E. Preece wrote:
| > Presumably pair programming similarly doesn't keep defects from being
| > written, it just identifies them faster (the person typing is still
| > going to type the error before the person reading can see what was
| > typed). [I recognize that in some cases the pair will recognize the
| > defect in discussion before typing, but that kind of incidental save is
| > no more preventative than a single programmer re-reading her code before
| > submitting it for testing - some defects simply don't live long enough
| > to reach the metrics.]
| 
| Agreed: it's just a question of where we find the defect. I placed the 
| dividing line at "did we integrate yet?" which is releasing to the rest 
| of the team. You placed the dividing line at "did we release to the 
| customer yet?" I think there's a considerable difference between the two.
---

I'm missing what you're trying to say here - inspections would normally
be done before integration (that is, before the code branch switches
from private to public).

scott
-- 
scott preece
motorola urbana design center (il67), 1800 s. oak st., champaign, il  61820  
e-mail:	[email protected]	fax:	217-384-8550
phone:	217-384-8589	cell: 217-433-6114	pager: [email protected]

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
--^----------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.