Funnily enough the quote engine at the top of the page answered this in the way I feel is most important:
"Be consistant"
Recently I have spent quite a bit more time looking at other people's code than writing my own, so I've developed some pretty strong opinions about what makes good style. (I like subroutines to be less than about 40 lines long and I like them to have explicit return values). Nevertheless, the most important thing for me is consistency. Providing the style of code I'm reading holds throughout the whole program, I can adapt. If it changes for every subroutine with no discernable patter, I get s##tty
Ironically, consistency has to be very carefully balanced with actually
improving your style :)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.