Something a good friend taught me that a mentor taught him: When faced with a question he'd often pause for a moment then ask, "What problem are you trying to solve?"
I'm on both sides. Sometimes questions are specific and warrant a specific answer. Other times you need to ask, "What problem are you trying to solve?" Often you can tell the latter type of question by the complete lack of context surrounding it.
Related tangent: I personally believe it's worth asking (maybe several times) the questioner to elaborate. Often by having to formalize a question in writing, the questioner arrives at the answer himself. It's the same reason programmers should provide high level docs. to their interfaces.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.