"Does the job". Requirements always change.
Yeah, but you either know what's going to change (and then do it right the first time), or you don't (and then, how do you anticipate?)
Maintainability lends agility to code
Eh, no. That's quite the opposite. Doing stuff now that isn't required is not agile. It's overhead. From The Agile Manifesto: Simplicity--the art of maximizing the amount of work not done--is essential. Anticipating to unknown future requirements does not lead to simpler code. Nor to less amount of work now.
Only maintainable, flexible code has any chance at all of being delivered on time while requirements keep changing.
Wait. By doing more work now, it's going to be finished sooner? How does that work? In the same way that paying more taxes increases my spending power?
Only maintainable code can be easily tuned and adjusted to suit performance or resource constraints. Non-maintainable code locks in specific algorithms and inflexible use-cases.
You got any data to back that up? Basically, you are saying it's impossible to write code that's fast enough, while it's not maintainable. So, code that's running fast enough, but of which the sources get lost (a real downer on its maintainability) suddenly slows down?
Poorly written code is just poorly written code.
Sure. "X == X" statements (even if one does rephrase the second X -- which you don't even bother to) are known as tautologies. They are a rhetoric device, and actually contribute nothing to the discussion.

In reply to Re^5: Legacy Code: "Dominoes = Bad" by JavaFan
in thread Legacy Code: "Dominoes = Bad" by locked_user sundialsvc4

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.