Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
A few people have asked me about my .sig. It all comes from the talk Why Perl Advocacy is a Bad Idea that I gave a couple of times last year. Thanks to chip for the whole "Perl Club" idea.

I've now come up with a complete set of rules:

The First Rule of Perl Club
You do not talk about Perl Club

The Second Rule of Perl Club
You do not talk about Perl Club

Third Rule of Perl Club
A laptop crashes, breaks, runs down. The hack is over

Fourth Rule of Perl Club
Only two programmers to a pair

Fifth Rule of Perl Club
One bug at a time

Sixth Rule of Perl Club
No Java, no VB

Seventh Rule of Perl Club
Hacks will go on as long as they have to

Eighth, and Final Rule of Perl Club
If this is your first night at Perl Club, you have to hack


"The first rule of Perl club is you do not talk about Perl club."
-- Chip Salzenberg

In reply to The Rules of Perl Club by davorg

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.