Although OO was invented to prevent it, there is no principle which stops OO code from degenerating into a Big Ball of Mud when sufficiently ill-managed.
It's pretty well documented that when code is both sour and essential, essential is what counts. You have to keep it working because it's a critical node in your business. A ten year history suggests that that is the case.
Spaghetti code is usually untangled by refactoring procedures. I think that wild OO code should be tamed by reducing data structures. Having not seen your code, I have no assurance I'm right.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.