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

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I share your sentiments but I don't think being able to give multiple votes is the answer.

I agree that sending a message to the poster is an excellent idea and will encourage them to post more in the same vein.

But perhaps there are other things you can do. For instance, if it is a root node (question, meditation etc.) you can Front Page it. This often helps with the XP.

You could also reply to the post you are impressed with explaining why you believe it is particularly useful. It maybe that with a little rejigging it would be suitable for another part of the monestary. Perhaps as a separate (front pageable) meditation, a tutorial, cool uses for perl, snippet, Q&A etc.. This would help raise it's prominence (which wouldn't hurt the old XP!) and would almost certainly generate more discussion which would help improve it even more.

You never know, if enough people agree with you it could even eventually make it into the FAQs.

I believe that keeping an eye out for the gems that may otherwise quickly slip out of view can only help build Perls documentation in general and the monastaries contribution in particular.

Hubris comes to mind :-)

So, I think you're wrong about the votes! But you've provoked an interesting discussion. :-)

jbrugger++


In reply to Re: Double voting (to get better answers as well?) by wfsp
in thread Double voting (to get better answers as well?) by jbrugger

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 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?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (5)
As of 2024-04-24 00:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found