My best advise would be to develop the systems separately (in different namespaces/machines whatever). Run unit tests on the new code (as we always should), and also compare the complete output of the both when ran over the same inputs to make sure that the results of the new are at least as good as the old (or why else would you make the new?).

When you are sure that the new system is complete and good, then replace the old system in its entirety.

To be more precise:

1. Make a copy of the old program and call it the new program.
2. Rewrite all of your classes/modules.
3. Test
4. Modify
5. Replace the old program with the new program.
6. Sit back and have a cigar knowing that you have done well.

In reply to Re: Clean code transition - how? by scmason
in thread Clean code transition - how? by shemp

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.