You implied it in your reply about C.

If you write an API for your code, expandability is a lot easier. Hell, if you develop patterns and single points of change, expanding it a lot easier. That is planning.

And if you put no infraastucture in, then you wind up with a lot of duplication and lot of badly implimented "stuff", such as redundancies or odd chains of method calls.

With a well written program, an implied infrastucture evolves. Writing your programs as a bunch of one offs, as if the last program written didn't exist, then you have no expandability. Writing with the idea of what you'll be doing in the future, then you won't shoot yourself in the foot, nearly as hard.

In reply to Re: Re^9: Best way to 'add modules' to web app? by Anonymous Monk
in thread Best way to 'add modules' to web app? by BUU

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.