(not really a perl thing, but...)

just fixing the one error that the compiler spat out was often shortsighted, as there could easily be more examples of the same error in other locations, or that error could have been caused by an earlier error, or perhaps a more fundamental logic problem.

I have to disagree on that one, the first lesson I learned the hard way in my first CS class was not to get bogged down by compiler errors. The prof had given us some C code, and our assignment consisted of two parts:

  1. fix the code so it compiled and ran
  2. modifiy it so it did something slightly different.

As provided, the code generated about 42 compiler errors/warnings ... people (like me) who tried to fix more then one error at a time, or fix the later errors first, spent forever on the assignment. Had we started at the first error, and then recompiled, about 3/4s of the errors went away. Fixing the next (now first) errors made the rest go away.

Moral: start at the begining, and proceed in sequence. At each step make sure that what you've done has fixed the first bug, and reduced the total number of bugs.

In reply to Re: Re: Programming Mantras by hossman
in thread Programming Mantras by dws

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.