- All rules are guidelines, including this one;
- Always use strict and use warnings;
- use constant is your friend;
- Regexes are bad, you can often use another way to do it;
- While there are many ways to do it, most of them are wrong;
- Anyone listing rules for programmers is wrong;
- Documentation is for users, comments for developers. You will be a user of your own code, so selfishness compels you to write both;
- Tests aren't as necessary as the testing cabal would have you believe;
- Tea is the one true source of caffeine;
- It's OK to reinvent the wheel sometimes;
- There will always be last-minute additions
My second rule is really just a variation on "turn on the fascism options in your compiler; and if the compiler emits warnings that's because your code is broken".
My third rule is a special case of general good practice regarding naming conventions.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
