Re: Re: Ambiguous Refactoring Solution

Hello, Olof.  On Wednesday, September 23, 2009, at 4:33:23 AM, you
wrote:

> I'm still in the camp "don't refactor an area until the need arises".
> See my first post on this thread.

Yes, me too. It is interesting though to look at any code and think
"How might we improve this." And if there's time to practice,
practice is good.

I would expect that, faced with 600 lines of actual code, we'd see
many steps to take.

A solid refactoring tool might help us proceed without error. But I
would want to get some tests in place right away.

Maybe I'd extract this class into a project of its own ...

Ron Jeffries
www.XProgramming.com
www.xprogramming.com/blog
I once had a coworker who worked so hard that when I came in the
morning, he was already sitting there trying to fix the things he
broke after I left the day before ... -- Ilja Preuss.



------------------------------------

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/