When you're at the point where you look at the project and see a mess, it's best to distance yourself from it and work on a new design. You'll be able to design it better given the experience you've had so far. There will be the temptation to keep building on top of the mess in the interest in time, but unless you absolutely cannot afford to spend the extra time it's often wiser to rebuild. In a lot of cases, you'll find that it won't take as much time to rewrite as you thought.
If it's really the mess you say, you'll find that the cost of maintenance escalates. It'll be harder to find bugs, and that won't make you or your client happy. And 6 months later, when you client asks for some additions, it could be a headache wading through that mess again--especially since it's not fresh on your mind anymore. I've had this experience before, and it's not fun at all.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||