Rewriting the whole code base from scratch is often very tempting when you're knee-deep in APIs that started out reasonable, got changed due to changing specs, got changed again because one programmer felt like it, then got changed again because another programmer realized that the API didn't actually work. And so on.
You say to yourself "Bah, I could rewrite this from scratch in a week and still have time to leave early on friday". You convince your boss and your colleagues that you can do it and they give you thumbs up. You sit down monday morning, pour a cup of coffee and start to type away. And then you're screwed.
The thing is, a lot of thought has gone into you existing code. It looks ugly, yes, but that's because it already contains the bug fixes, the workaraounds and the quick hacks that make the system run in your choosen production environment with all its limitations, known issues and bugs. If you start over, chances are that you're gonna have to reconstruct all this accumulated knowledge all over again.
That said, and with the java-bashing going on in this thread, I'd like to publicly state that I love java. Thank you.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||