Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
From a recent email exchange in one of the many mailing lists I follow:
One of the answerers: You asked one question when most people who use {product} know that's not the right question to answer.

Original questioner: Please don't second-guess my questions. If I wanted a different question answered, I would have asked a different question.

Yours truly: Uh, no. As a frequent question answerer, I tend to think as much about the context of the question I'm answering, as the answer I'm writing, just in case there's something missing. And I'm free to question the context as much as I am free to answer the original question.

If you had not wanted to be second-guessed, you would have stated more about the context of your question, so that we wouldn't have to wonder if you're doing something the hard way.

Every question is a piece of an answer to a larger question. Sometimes, it's worth backing up a step to ensure you haven't painted yourself into the corner.

To presume you've already solved the issue that led to your question in the best possible manner is to have an arrogance that will only irritate the people from whom you seek guidance. :) Remember, you've only solved that level to the best of your ability.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.


In reply to On Answering Questions by merlyn

Title:
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 or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (4)
As of 2021-10-23 10:47 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My first memorable Perl project was:







    Results (88 votes). Check out past polls.

    Notices?