I think this also needs a successor "How to write useful answers".
- Listen (Read) intently
- Test your Code, or mark it as untested
- If you want to foster a community, don't be a prick.
- RTFM is nice, RTFM or STFW with links is better
- Be informative, remember, archives are eternal.
- A well written response might become a S result on TFW, or, to quote "What we do in life, echoes in eternity" --Maximus, Gladiator
( Aside: Of course, sometimes I, too, become frustrated at an ignorant post, and lean more toward "At my signal, unleash hell")
I'm by no means suggesting a level of hand holding greater than now occurs (well, maybe a bit), but I think we can show others what is expected of them if we lead by example. Besides, responses that are dense with information and solid (read: Tested) examples begin to create a repository of highly useful, and crossed referenced material, and isn't that what we are after? ( Aside: Hmm, new discussion node there...A count of the number of internal nodes referencing a particular node. This might be a good quick reference on a particular nodes usefulness, excluding manpages, etc...)
C-.
-
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.
|
