the iterative try/fail/fix cycle, driven more by intuition than by design

Yes but there is a great advantage to doing it that way....you uncover unexpected bugs in a step-by-step process. Whearas the CS approach of designing, can leave bugs deeply nested, only to be discovered later.....which then forces you to "rewrite-and -debug" stepwise....basically doing it twice. It's probably why Java takes so long to develope stuff compared to Perl.

Nature and evolution use the iterative try/fail/fix cycle, so maybe the "evolutionary approach to design" isn't so bad after all.

I'm not really a human, but I play one on earth. flash japh

In reply to Re: brilliance or... easy erasure? by zentara
in thread brilliance or... easy erasure? by samizdat

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.