Hmm,
People (such as myself) will be using your review as a guide. This is a bad review.
It offers no specifics (oh yeah - you're impressed. By what?)
And you haven't fully read or tried out the book.
PUH-LEESE:
1) Don't review anything too early (and this sounded like it was -- "Hey, great novel! I've read the first few chapters, and this is a great book!")
2) Don't use words like "fantastic" unless you back them up (you didn't)
3) You went through 17 hacks (no specifics) Then how'd you do with variations on Hack#10? I found it worked the first time, and then failed in unexplained, complex ways, such as when any tweak was used. Anyone who's tried #10 more than once, I expect has run into problems.
I read this book on a train without my computer. Lots of potentially nifty ideas highlighted & noted. But the first one I tried started screwing up almost immediately. (Thank you, Microsft) Second one worked.
Nasty note, eh? Well, this looks like a book that required a lot of work to produce. And the reviews should respect that.
Be specific about what was useful to you. Don't make generalizations you don't back up. Do finish the book before you comment on it.
I don't mean to be horrid, but I've read too many half-baked/sloppy evaluations laid upon the world at large by people who don't distinguish between chatting with pals and putting something out for the world. This ain't just talking to your dog; it's public.
No reply requested. And don't take this too personally. It's a standard problem.
-squerb
|
