I don't like the "If someone reviews your code, please review someone else's" part. People who don't know how to write good code and don't know how to benchmark shouldn't be "reviewing Perl code for style, efficiency, and so on."

These reviews for the Attempt module make me question the validity of all code reviews. How could you give a perfect rating to a module that only saves a few keystrokes of simple code, if any? What kind of programmer would have trouble creating Attempt's functionality within their own code? I'd never use a module like that, and I can't believe it was recommended to me and it hasn't received anything but perfect ratings.

In reply to Re: Peer Review For Perl Code by Wassercrats
in thread Peer Review For Perl Code by Limbic~Region

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.