I haven't really thought this through, so I'm open for arguments here.
What's bad (really bad) here, is that not only are the books that are being ranked highly absolute crap, but they are crap in different categories. I.E. A "book" on swift, that was apparently "written", in a few hours, shoved onto Amazon, falsely ranked up - now ranks ahead of a 700 page opus on Perl, in the Perl category.
That's a total fail on Amazon's part, and really, really disappointing.
When it comes to reviews, the correct answer is that every user should have their tastes profiled and compared against the tastes of other users, with only users whose tastes in other areas counting strongly. I could easily imagine that this sort of thing might be difficult for Amazon to implement, though, depending on their infrastructure.
The bogus reviews had one or more of these aspects:
- bad reviews from reviewers with no other reviews
- mentions of the same competing book in my bad reviews
- 5 star ratings of that mentioned competing book (and no other reviews beyond those)
- 1-star reviews of another random book. This one was interesting, there was another book (Service Oriented Architecture for Dummies) that is entirely unrelated. But 2 of the reviewers also gave shitty reviews to that book as well as mine. There's no logical reason that the same people badmouthing my book would have also read, reviewed, and badmouthed that other book (totally different topic) within a few days. So they were clearly hired for a number of books at once.
So yeah, you'd think some of those patterns would be easy to automatically detect. Although I assume it's constantly a game of cat and mouse.
One thing I do like about their system is that you can click a link to read the reviews they consider "not recommended."
Here's what they say about it publicly: http://officialblog.yelp.com/2013/11/yelp-recommended-review...
This may not be the best place to bash Yelp, but if you're reading this, please don't pay Yelp for their exorbitantly-priced business service. It is absolute garbage.
And frankly, I don't have seem to have a lot of tastes in common with the hardcore Yelp users.
Maybe I was too generous by saying their system works "decently well"; though I don't think I'd say "complete crap"--unless my business had been burned by fake bad reviews, which it sounds like happened to you.
Perhaps this illustrates how subtle/difficult this problem is.
From sponsored "impartial" reviews to niche items with way too many reviews and a mismatched helpful/not helpful or Q&A area, Amazon reviews are starting to lose their value.
There are a few legitimate reviews that indicate this book doesn't really have much content, and then 2+ dozen fake 5-star reviews praising the book highly and saying how much better it is than Munroe's book. If you look at the review history for any of the 5-star reviewers, they all seem to be reviewing the same products, and often they are reviewing 3-5 books per day.
I reported the reviews via feedback, but never received a response. Ultimately it's just disappointing to see this kind of thing happening.
I.e. improving your resume, looking prestigious to potential consulting clients, or landing paid speaking gigs.
The way it works is simple. Publishers hope to sell about 5,000 or so copies of your typical tech book. That's enough to keep the publisher going, but not enough to really make money for them. The publisher keeps those "filler" books going to keep up street cred and hopes to sometimes land the "killer" book that makes them a nice profit.
I can't share the sales info for my book, but let's just say that I think the book is doing better than one might expect for its category.
If you want to write a tech book, you want to go with O'Reillly. My advance was much larger than what O'Reilly would offer, but they sell more tech books in the long run. However, O'Reilly's Perl book section is saturated and they generally don't take new authors.
What I did to reposition my book was a strategy I wish more tech books would take: I focused on jobs. Instead of teaching every esoteric niche of a language (though I covered it well), I focused very heavily on skills that employers look for. I've been doing this for a long, long time and am very familiar with employer needs, so I was well-positioned to do this. That has led to my book doing better than expected: here's what you need for a job!
I now have a successful Perl consulting firm (http://www.allaroundtheworld.fr/) and that book, while I can't prove it helped, definitely didn't hurt.
Oh, and my publisher has spoken to an Amazon rep and a contact I have in Amazon tells me that they're aware of the situation and are looking into it. I don't have much hope, but who knows?