Been there. Bad memories.
Explain that the project will take longer than you thought because you have to trace what is happening to the data at each stage. As you figure it out, fix it and/or document it. You may be responsible for maintaining the code for a few years and might as well make your job easier from the start.
Of course, your boss knows you are only documenting and "applying a uniform format to the code" - not "fixing" what he wrote. "Optimizing" how your modifications interact with the original code comes later. (This will look a lot like a rewrite.)
I spent two frustrating years waiting to start a re-write that was always "two months off". During that time, the nasty code I inhereted just got bigger and more convoluted as we tried to work around the existing problems.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||