Might I recommend ... Code Complete and Writing Solid Code? They're a bit old now, but still just as true as ever, even if a bit C-oriented. The key is to:

  1. write clear code which is unambiguous
  2. write proper comments where you can't make the code more clear
  3. write proper documentation where you can't write proper comments
  4. redesign your code where you can't write proper documenation.
If you can't write it clearly, that's usually because you can't think it clearly. And if your thoughts are unclear, it makes it much more likely that your code is incomplete (missing boundary cases, etc.).

Of course, that's all easier said than done!

In reply to Re: Reading the same text and getting a different impression by Tanktalus
in thread Reading the same text and getting a different impression by fraktalisman

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.