My heuristic would be simpler, and less prescriptive than those I've seen suggested.

It is based upon the somewhat naive, but egalitarian ideal that everyones opinion is as valid as the next.

It is: No change in the number of votes per level; just simply that everyone can, if they have a vote remaining, vote (upvote*) twice on any node they consider worthy of special merit. That additional vote decrements their existing tally in the usual way.

I see no reason to restrict this to any given level:

Why is the opinion of someone new to programming; or even an experienced programmer new to Perl; or even experienced with Perl but new to this site; lesser than someone who has hung around on the periphery of this place accumulating attendance votes and the occasional "what have you tried" or "read the formatting guidelines" or "etiquette demands that you announce your cross-posting" or "X-Y problem" replies?

*I'd also allow double down-voting -- I consider the condemnation of bad posts as, if not more important as the commendation of good posts -- but I am aware that could be controversial in some quarters. (For those quarters, think of it this way: you'd have had double the potential to put me in my place!)

Whilst I am quite sure that there will be small cliques of monks that will arrange to double upvote each others posts; I am naive enough to believe that they will be more than offset by the: "I vote on those posts that surprise, delight or educate me" majority.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^6: RFC: Better Best Answers by BrowserUk
in thread RFC: Better Best Answers by jdporter

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.