Re: Re: Ambiguous Refactoring Solution
Olof Bjarnason <[email protected]>
| Newsgroups | gmane.comp.programming.refactoring |
|---|---|
| Message-ID | <[email protected]> |
2009/9/23 Ron Jeffries <[email protected]> > > > > Hello, Olof. On Wednesday, September 23, 2009, at 12:37:47 AM, > > you wrote: > > > OK maybe I should have been a little clearer. > > > When prioritizing things, improving "old code" should be lower on the > > list than fixing backlog / doing what the customer asks. > > > If the customer isn't asking something, or the backlog is clear - then > > why not improve the design of the code? > > Because the project is done? Sure, that's a good reason. But meetings/communication between team members is not always synchronized - the customer might not be available this day. People are sick, have children, are on short leaves etc. The iteration might have gone faster than expected (does happen, although not as often as one might hope). I'm still in the camp "don't refactor an area until the need arises". See my first post on this thread. > > Ron Jeffries > www.XProgramming.com > www.xprogramming.com/blog > If you want to garden, you have to bend down and touch the soil. > Gardening is a practice, not an idea. > -- Thich Nhat Hanh > > -- twitter.com/olofb olofb.wordpress.com olofb.wordpress.com/tag/english ------------------------------------ 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/