I agree with this completely. Since I starting forcing myself to over comment my code, my bebugging cycles have gotten much shorter. Not only does it mean less bugs get out the door, but it means if something is too ugly to admit I'm doing it that way, I can't just pretend it's not there; I have to admit it sucks, or do it right.
Also, it helps to _find_ bugs. Something may be obvious, but that doesn't mean a person should have to parse it all to find the stop they're looking for.
And since we all improve over time, what was obvious when I wrote the function might not be obvious at all when I'm debugging it. More like, "did I really do that?"

In reply to RE: Re: Over Programming by Aighearach
in thread Over Programming by little_mistress

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.