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

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
A monk who knows the answer to the question and comes across an obviously incorrect answer has four options:
  • Ignore it
  • Downvote it
  • Reply and correct it
  • Send the poster a message with a correction

Two of those give *useful* feedback to the poster. A downvote doesn't -- it's a one-bit message that doesn't communicate very much. Posting a followup allows for more room to explore and to explain the reason why it's wrong. Also, it'll enter the archives forever attached to its parent.

Sending a message works in cases where the poster just missed the boat and presumably knows better. People misread questions. It happens.

Now the poster of an incorrect node also has several options:

  • Ignore it
  • Reply to it
  • Censor it
  • Update it

Two of those leave useful information in the database. One of those potentially notifies the user who posted the original question.

In my opinion, it's better to reply, whether by writeup or message, to an incorrect post. This gives the poster the chance to correct it (if by /msg) or attaches a correct answer to an incorrect answer. A downvote doesn't accomplish much, but it has the chance of attracting the poster's attention to possibly incorrect data. It doesn't tell what's incorrect, though, and it doesn't put any data in the archive, though it may prevent an incorrect node from sticking around.

Far better to be explicit. If it's wrong, explain why it's wrong. Give people a chance to correct it.


In reply to Re: Pummeling Monks for Misconceptions? by chromatic
in thread Pummeling Monks for Misconceptions? by Sherlock

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 meditating upon the Monastery: (5)
As of 2022-01-19 17:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:












    Results (55 votes). Check out past polls.

    Notices?