Certainly one can argue that facts for a book or module can be found elsewhere, but I think that the addition of this information is necessary for completion, as some of my examples indicate. Other examples: the reviewer claims that this book packs everything one needs to know about perl into it; I'd question that claim if the book is less than 100 pages long. alternatively, if a reviewer claims that the book is lacking and yet is 1000 pages long, I'd again question the reviewer.
Of course, as you state, there's no way to control the quality of reviews here on PM; we can only use the voting system to let reviewers know if it was acceptable or not. In my case, I don't plan to downgrade any reviews unless they are completely baseless ("The Camel book is completely worthless because I say so!"), and upgrade those that I find useful, but I'll take a neutral stance on reviews that seem so-so.
-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
It's not what you know, but knowing how to find it if you don't know that's important
-
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.
|