OK! So here is a list of questions for the test (do I need to add that these are a bit tongue-in-cheek? Probably!)

• I want to post some code so people can help me find an annoying bug:
  1. I cut and paste all 356 lines of code in the appropriate window, add a title like find th bug!!! and hit submit.
  2. I cut and paste my script in the form, wrap it in <code> before tags slap a title like "regexp" et voila!
  3. I extract the smallest chink of my code that causes the problem, run it (under strict and -w), wrap it in code tags, add a detailed description of the expected result and of the actual one, then use the preview to check the formatting of the post, and then finally hit submit.
• I have a problem involving flock:
  1. I type flock in the search box, thus getting the doc for the function staright out of perldoc
  2. I type flock toto in the search box, and get back a list of nodes including flock in their title, including the doc
  3. I invoque the Super Search and look for flock in the body of message, for an even longer list of nodes
  4. I try to think of a couple more keywords that would narrow down the search and I use them in Super Search for an hopefully better result
• I see a question for which I am quite sure I know the answer:
  1. I post as soon as I can a vague answer, so I don't risk making a mistake
  2. I type a proper answer, including untested code (with a warning), as fast as I can and hit submit, I know the first answer usually gets the most XPs, Yeah!
  3. I write a little piece of code showing the answer, I test it (under use strict and -w) then post it with the appropriate explanations. After all there is more in life than XP's and I don't like posting apologies (plus getting -5 rep on a post is not quite the result I hope for!)
  4. (10 000 XP and above) I state that the answer is given in one of my Web Techniques columns. I add a {grin} just in case.
• I have been downvoted 3 times in the last 5 minutes for a post I thought was uncontroversial:
  1. (10 000 XP and above) I grab the list of people on the site and post it, inevitably generating a lengthy list of rants, counter-rants and generally irrate posts, thus ensuring that a good time is had by all
  2. I suck it up like a man
  3. I downvote a bunch of loosers just to be sure I'm not the only one to be annoyed today
  4. I post a "I love Perl Monks" message to XP-whore the XP's I lost, and more
• A troll is posted, what should I do?
  1. Reply Go s***w yourself !@#$%^&* troll!, thus preventing the node to be automagically reaped
  2. (level 6 an up) Send the node to Nodes to consider do not forget to add my name to the reason, updatedownvote it (thanks arhuman), then go to the list and vote "delete" so the node can be reaped
  3. (level 5 and under) Do nothing

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.