in reply to Reviews Quest

Hmm... I have a book I'd love to do a review on: "Perl and CGI for the World Wide Web" by Elizabeth Castro. However, the review would be, amongst other things, a warning with examples as to why it should be avoided. The Quest is a review "for your favorite module, book," etc. I think a review of a poorly done work, if handled properly, would be appropriate. I assume that no one objects?

The link Reviews Section actually heads to a post requesting that a Reviews (that's the good link) area be set up.

Oh, I see from rereading the Quest that I can post a review about my favorite PM user. I wonder how much I can write about me before the contest deadline :)

Update: I see that vroom has noted that it's okay to write a negative review if we feel the need (I wonder if that was up there before and I simply missed it?). Also, I've noticed that my review of Castro's book is going on longer than I intended. I think it's going to turn into my largest post of all time if I'm not careful with the editing :(

Update #2: I have finished the review (work was a bit slow today). You can find it at this link.

Cheers,
Ovid

Replies are listed 'Best First'.
RE: RE: Reviews Quest
by spectre (Scribe) on Jul 07, 2000 at 20:14 UTC
    I think that a review of something to be avoided would be very helpful, actually.
    I dont know what other people feel, but I personally see either a good or bad review as being worthwhile to read - I wouldnt want to buy a lame book, and if I saw a well written post about why book A is bad, I would be very grateful
    Regards,
    spectre