Hi Russell,
Having little time to read the entire thread, here is
my two cents about this message:
>
> 3) Other members of the team (not necessarily this
> guy) are not used
> to refactoring at all, and would prefer to institute
> design reviews as
> a way to get to quality.
How about a live design review? Why not fishbowl the
code that corresponds to the design, and make changes
'live'? Do things like point out and remove
duplication, show how you could make a change with
more courage if a test was in place, and then put the
test in place and make the refactoring. Get the team
involved, make a day or two of it.
This would take some prep work on your part, but it
may do some good. Team mates may begin to see testing
and refactoring as something with business value, as
opposed to something that is foisted upon them.
Chris.
=====
---------------------------
C H R I S W H E E L E R
Extreme Programmer & Coach
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
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/
