Thanks for the suggestions (and the stories). The versioning system made sense as a way to approach this particular problem. On my side was the fact that management and my fellow coders agreed that the code in question was ugly, rushed, and unmaintainable. (Of course, it isn't too hard to persuade a coder that someone else's code is horrible.)

Our site does have separate development and test systems to fool with code before it goes live. I was able to procure some test data to run through the old scripts, index the results, and use them to make sure my modified produced identical results.

I'm up to revision 6 now, with the main script rewritten as Perl, and only two shells left to convert to functions. Thanks for everyone's input.

In reply to Re: Refactor and simplify by delirium
in thread Refactor and simplify by delirium

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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, details, 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, summary, 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.