|Don't ask to ask, just ask|
How should you write a review?by dragonchild (Archbishop)
|on Sep 05, 2001 at 22:55 UTC||Need Help??|
Prior to saying anything at all, I will say that I had not heard of this book and will be checking it out next time I'm at a bookstore with a copy.
I will say that I voted this node down upon my initial reading of it primarily because the review, I felt, was very poorly done. I couldn't care less if someone said "Book A is better than Book B" ... so long as they backed it up in terms I can relate to.
Before any of that, however, I would refer kommesel to a spellchecker and a grammar book. If you're going to take the effort to write a usable review, at least make it something I can read.
I tried the Camel book, but being new to UNIX and to Perl, I couldn't understand the explanations, which were refrenced to something quiet obvious (not to me).
Fair enough. A lot of people have this objection with the Camel book. (Though, my question is now why didn't you look at the Llama book?)
I bought the Black Book, and found it to be very complete and easy to understand.
Examples? Complete how? What does it have over Camel? Where is Camel lacking?
The system guys in the company where I work, said that it contains more information on Perl than any other book they've seen.
Again, I don't care about the system guys where you work. I care about your experiences with the book. Did you read it all? What did you learn from it? Would you recommend it for a novice? Expert? Guru? Should this be on Larry Wall's or Damian Conway's or merlyn's shelf?
Yes, you told me about a resource you feel is excellent. Now, in a readable fashion, tell me why it's excellent. Sell me the book. Rave about it. Make me leave work right now and go buy it because my afternoon will be that much more productive.
Update: Fixed spelling/grammar errors that Sifmole kindly pointed out. ("refrenced" was quoted verbatim.)
Vote paco for President!