One thing to look out for is making too many changes at once. You can usually get away with a little bit of refactoring at a time. (Well I was in there to fix this bug, and I had a devil's own time figuring out that the variable $aa was actually the base pay-rate and $aaa was the differential rate, so I made a mass change in addition to fixing the two lines that were broken.) People will be more accepting of several small changes spread out several days, rather than one large one. Over time, you will end up cleaning up a lot of dreck with a lot fewer complaints.

"One step at a time, I will walk around the world." -- Aral Vorkosigan

----
I Go Back to Sleep, Now.

OGB

In reply to Re: Dealing with sloppy code by Old_Gray_Bear
in thread Dealing with sloppy code by BMaximus

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.