Re: Ambiguous Refactoring Solution

And, I just said that I don't recommend you do it that way, but I
suspect "you" (or whoever) will do it however you do it.

I suggest that you cover what you are going to refactor with automated
tests, preferably by writing them in the first place (Not
controversial. You referenced Feathers yourself, and this is precisely
what he has recommended.) At the very least I recommend that you watch
out for CRAPpy code
(http://blog.objectmentor.com/articles/2009/05/20/clean-code-and-battle-scarred-architecture)

I am especially unmoved by "people have been doing this for a long
time" arguments. There is a whole lot of stuff that people do. If the
answer were, "do whatever you want (or whatever you did before) and
call it refactoring," there would be no point in having this list (nor
the term "refactoring" I suspect.)

On Wed, Sep 23, 2009 at 3:48 PM, Richard <[email protected]> wrote:
>
>
>
> I didn't say "don't test it after you refactor", I'm merely pointing
> out that people have been doing the manual testing refactoring for
> decades before it was called refactoring.
>
> Perspective: use it or lose it.
>
> --
> "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
> <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
>
> Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
> 


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

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/