Re: Using refactoring to make code more testable Re: [refactoring] Using refactoring to make code more testable
Steven Gordon <[email protected]>
| Newsgroups | gmane.comp.programming.refactoring |
|---|---|
| Message-ID | <[email protected]> |
Better than either commanding or showing is finding a way to let the team think it was their idea. Look for issues during an iteration to bring up in the retrospective that might help the team decide to address by trying TDD. Maybe plant a seed in conversation with the alpha developer on the team. No retrospectives? I am afraid that might practice have to be commanded or at least strongly suggested. Still most teams find imposing short retrospectives over beer late Friday afternoon much less like telling them how to do their jobs than imposing TDD would be. On Tue, Oct 13, 2009 at 4:40 PM, Schrecht <[email protected]> wrote: > > > > > Adrian Howard, responding to me, wrote: > > > If the former, obviously, you can command them. > > > > Curiously enough I rarely find this works. You still need to do your > > option 2 > > We work in different environments, I suspect. That used to be true, but > In the places I've been for the past ten years or so, what I see is that > people who don't conform to commands get disciplined. > > Still, leading by example is far better, in every way. > > Cheers, > Cornelius > > > [Non-text portions of this message have been removed] ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/refactoring/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/refactoring/join (Yahoo! ID required) <*> To change settings via email: mailto:[email protected] mailto:[email protected] <*> 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/