It only *seems* skewed, because there are two factors which haven't yet reached an upper bound -- the number of regular users of the site, and the number of available votes a good post can receive. As those increase (the second somewhat dependent upon the first), so will the number of points awarded to the best nodes.

It would be nice if voters dug through the archives to find some underappreciated gems (there are a couple of Snippets I'm incredibly proud of, as they're good technical hacks) instead of hitting up the newest ones.

Of course, as the number of votes available to J. Random Regular increases, unless the total number of really good posts (as opposed to mediocre) will have to increase, or he'll vote up posts that are less deserving than before. When you only have five votes per day, and thirty new posts, you'll save your votes for the gems. When you have 25 votes per day and 30 new posts, you can afford to be less discriminating.

Perhaps the act of voting shouldn't grant experience -- and being voted up should grant more.

---

---

• 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.