comment on

Yes, it would have been cheaper and faster to throw this code away and start over

Maybe. 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:

Swallowing an elephant in 10 easy steps by ELISHEVA (Describes how she tackles big problems to keep moving forward rather than going around in circles)
Dealing with sloppy code
Becoming familiar with a too-big codebase?
Analyzing large Perl code base.
Perl Medic: Transforming Legacy Code by Peter J. Scott
Working Effectively with Legacy Code by Michael Feathers
Object-oriented Reengineering Patterns book now available as a free download

Nobody Expects the Agile Imposition (Part VI): Architecture (discusses refactoring vs rewriting of very large code bases)
The Boy Scout Rule (apply the Boy Scout rule of "leave the campground cleaner than when you found it" to your code)
Unix shell versus Perl (explains why Perl is a better choice for large code bases than Unix shell)
Re: Moving from scripting to programming (tips for writing industrial strength code that lasts a long time)

Update: Legacy Code References Added Later

Update: Testing References Added Later

Updated: Added many extra references long after the original response was made.

In reply to Re: Strategies for maintenance of horrible code? by eyepopslikeamosquito
in thread Strategies for maintenance of horrible code? by converter

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


Welcome to the Monastery
	PerlMonks