The earlier advice from others re
writing tests and re-factoring is sound.
You are, however, most unlikely to be given enough
time to do it all, so you must choose wisely which
code to clean up first.
How to choose? i) write tests for all recent (and new)
bugs; ii) focus on modules you consider to be most
vital and highest risk; iii) Go through the user manual and write a test (and refactor where appropriate) for each example given there (i.e. focus on client view of the system).
Perhaps more important is to ensure that all new
code is developed test-first and with a solid test suite.
I've been (and am still going) through something similar as mentioned in What is the best way to add tests to existing code?. As expected,
and despite earlier assurances, I did not get anywhere
near the time and resources I would have liked.
Bottom line: this sort of code cleanup, while strategically
sound in the longer term,
does not bring in immediate revenue.
Update: You might pick up some good ideas
from the book
by Peter Scott. Ditto from the node starting to write automated tests.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||