A non-programmer, beginner's take on this...

1. Always use strict.
2. Always use warnings.
3. Always use diagnostics during development.
4. KISS.
5. Brute Force programming is not always a bad idea. Elegant code is often slower and harder to maintain.
6. White space is your friend.
7. Comments are an even better friend.
8. CPAN is the best friend you'll ever have.
9. When you've programmed yourself into a corner, sometimes the quickest fix is to trash everything and start from scratch.
10. Assume that the person who will have to maintain your code is even more of a NOOB than you are.

Jack

In reply to Re: top ten things every Perl hacker should know by jcoxen
in thread top ten things every Perl hacker should know by apotheon

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.