--- In [EMAIL PROTECTED], "amr_samadisy" <[EMAIL PROTECTED]>
wrote:
>
> I knew if I could get a response from Ron he would give me enough
> questions for 2 or 3 theses topics :)
>
> <[EMAIL PROTECTED]> wrote:
>
> > > 2) Does the constant refactoring really make up for the
> 'rework' done
> > > - or is it sometimes better to do BDUF - if so when?
> >
> > Precursor questions: To what extent in ED is refactoring "rework"?
>
> Don't know. There is *some* rework. Personally - I would guess a
> very small percentage unless we are in a large refactoring situation
> (which happens sometimes ;) ).
"Rework" is work that you could *reasonably* expect
to have done right the first time. For example,
when I put in a couple of lines of code, and the
compiler complains because I misspelled "if",
then the correction is rework.
Refactoring is generally not rework: you normally
don't know what you're going to refactor until you
see the code.
This is why "rework" is usually a manufacturing
production concept: manufacturing is about reducing
variability, while developement is about embedding
learning acquired during the project into a product.
John Roth
>
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
