I don't think programmers can be easily lumped into the analogies of mechanics and civil-engineers, but perhaps programming as a field is analogous to the field of construction.

Small projects, like adding on to your back deck, can be tackled by do-it-yourself-ers with a little guidance or alot of common sense. Plans can be drawn up in a evening and the job done in a weekend. As projects get larger, the job gets more complex. A mid-sized job might require a small construction crew, with the experience and tools necessary to do the job without alot of standing around while figuring things out. Building things like a bridge or sky-scraper require a large investment in detailed planning, to ensure that the materials and teams of (specialized) workers are in the right place at the right time.

Programming is no different. As the ambition of the project rises, so does the level of sophistication required to carry it out rise. But the do-it-yourself-ers and small construction crews are not going away simply because we can build bridges and sky-scrapers. There will always be need for projects of every size, and we'll always be best served by using the best people and tools for the job.


[TINPC@perlcabal.com shh]$ su real

In reply to Re: The future of software design by Felonious
in thread The future of software design by bprew

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.