Re: Using refactoring to make code more testable Re: [refactoring] Using refactoring to make code more testable

In article <[email protected]>,
    Adam Sroka <[email protected]>  writes:

> On Sun, Oct 11, 2009 at 12:48 PM, Richard <[email protected]> wrote:
> > The three rules of programming apply:
> >
> > 1. Don't do it.
> > 2. Don't do it again.
> > 3. When all else fails, break rule 1.
> >
> 
> I don't know where that comes from. It's cute, but makes no practical
> sense to me.

Rule 1 is essentially XP's YAGNI.
Rule 2 is avoid duplication.
Rule 3 is write code when you can't find code that already does it
(Build, not buy).
-- 
"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/