There's more than one way to do things | |
PerlMonks |
Re: Strategies for maintenance of horrible code? (Legacy Code References)by eyepopslikeamosquito (Archbishop) |
on Jul 12, 2006 at 08:30 UTC ( [id://560637]=note: print w/replies, xml ) | Need Help?? |
Yes, it would have been cheaper and faster to throw this code away and start overMaybe. For another point of view, see Joel Spolsky on not rewriting from scratch. I agree with adrianh. If a component is not broken, don't rewrite it. Rewrite a component when you find a number of bugs in it. But first write a regression test suite for the component. I've seen many folks over the years throw out old code, rewrite it ... and introduce a heap of new bugs in the process. If you come into a new company and introduce a swag of new bugs in previously working code, you will start to smell very badly. See also:
Legacy Code References Added Later
Bad Code References Added Later
Testing References Added Later
Updated: Added many extra references long after the original response was made.
In Section
Seekers of Perl Wisdom
|
|