Great post. Something like this probably qualifies as an axiom: "understand why you want to rewrite something, and understand what you may be rewriting".

Another issue that I haven't seen touched on yet is the new CTO's ego and political motivations. I would guess that if a new CTO just came in and shot par for the course by keeping the legacy system running well, that CTO wouldn't have much to add to their resumé. It seems like it makes more slimy political sense to say "Everything sucked until I came on board and made it better"; especially if it's not true.

---
"A Jedi uses the Force for knowledge and defense, never for attack."

In reply to Re: A Porting Horror Story by meonkeys
in thread A Porting Horror Story by stephen

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.