In addition to the excellent tips above, I also find chromatic's journal of his Refactoring Everything project a pleasure to read. The main points I take home from it are 1) security and 2) fun. Having a source control system and a good set of tests makes coding much more relaxed, because you can always revert your changes (because of svn), and you'll know when you break something (and where) because your tests will tell you. That means you can stop worrying, and focus on writing good, workable code that you can be proud of as well. I find it exciting to see a master at work, so to speak :)

In reply to Re: Unit testing -- module, book, and website suggestions wanted by rhesa
in thread Unit testing -- module, book, and website suggestions wanted by Sifmole

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.