The review is leading somewhere, so just wait for it…
Evil Kev and I had an argument this weekend, about whether or not Edison Force deserved a B or B minus rating. I was leaning for the B minus. For the most part I really enjoyed the movie. However, the problem was the same problem I have with most movies and television I watch these days: Holes.
Now, the movie stars quite the cast. Kevin Spacey. Morgan Freeman. Cary Elwes, of The Princess Bride and Kiss the Girls and Robin Hood: Men in Tights, if I’m not mistaken. (The guy has some range.) Dylan McDermott. LL Cool J. John Heard. And…
Justin Timberlake, who made his acting debut. Evil Kev almost didn’t rent the movie because of JT, but we were both pleasantly surprised. He did decently.
My main issue with the movie was the premise. (If you don’t like spoilers skip this paragraph.) After an elaborate, Hollywood shoot ‘em up to get us started we see Dylan McDermott and LL Cool J out to do a pick up. Rob some drug dealers. When they’re leaving one of the druggies says he’s going to find out who the cop is and complain to justice. So, Dylan McDermott’s character kills him and then pegs it on the other dealer. The real crux of it was, as the story unfolded you realized the corruption in the system went all the way to the top, including local businesses and the DA’s office. That money being taken from drug dealers was being used to fund political campaigns. It was being laundered through the police department. Would the word of one drug dealer have made an ounce of difference? No. And can you see it? “Yes, um, officer, I want to make a complaint. I’m a criminal and the money I make from my criminal dealings was stolen from me.” Ha ha ha, too bad, don’t let the door hit you on the way out.
Anyway, that was indicative of a few of the holes in the storyline. There were a couple other points where I said, “Okay, there’s no way they could reason out of this. It doesn’t make any sense.”
And all in all, I’d say it was too bad. The basic story (while not highly original) had potential. Of course, it also had some clichés. The journalist burned out, wanting to play it safe, being brought around by the young zealot (Timberlake) on the scent of a story. The bad-ass cop (McDermott) with his partner (LL Cool J) who still has a conscience. There were a few other things that just never would have happened in reality.
That said, McDermott did a good job in the role. He makes a good scumbag. And was handy with a stapler. I just hope he found Vancouver preferable to Calgary, which he thought was a hick town.
I bet most of you are wondering what I’m talking about. And if you click on the link, you’ll see some of us have long memories. After all this time I still remember. In fact, when we ID'd Vancouver as the place where they'd filmed the movie (so obvious from landmarks included) we actually had a chat about how Dylan had managed in this 'backwards' country of ours.
This brings me around to the topic of defending yourself. Now, it seems ironic that, after just so recently mentioning the frustrations over the review section with Spinetingler that this topic has exploded elsewhere.
The reason? Someone posted on DorothyL a rebuttal to a review. Except the review wasn’t posted on DorothyL – it was posted on Reviewing The Evidence. The rebuttal was written by the spouse of the author, and included calling the reviewer anal.
I think each and every one of us appreciates the desire to vindicate ourselves. Just this morning, when I dropped by the Bearded Wonderboy’s blog he, too, was expressing some frustration. In his case, with a reporter who misquoted him in print.
Now, why is it that I have no issue at all with what Stuart did but was bothered by the other incident?
There is a proper time and place. I’m of the opinion people can post pretty much whatever they want on their blog. Nobody is forced to read it. It doesn’t end up in people’s inboxes the way listserv posts do. It’s considerably less intrusive. Would it have been better if he’d complained to the publication? Maybe. But we all know retractions get squeezed into something similar to 6pt print size at the bottom of a page of solid grey so that nobody reads them anyway. The way I saw it, Stuart was getting it off his chest… and who can blame him?
When it comes to arguing with reviews, they are a question of taste, for one thing. Unless the reviewer makes a factual error with the book, arguing over points in a review is the equivalent of boxing in quicksand.
It’s pointless. Beyond that, most reviewers and review sources have policies about arguing with reviewers. Most will ban authors from being reviewed if they (or their spouse) argue over a review. We didn’t start off with that policy. We implemented it after I discussed issues with other reviewers and heard how they dealt with it.
Another thing: Most of these reviewers are volunteers. Abuse can lead to fewer people willing to do reviews.
I have no problem with people disagreeing with reviews they’ve received. I don’t even have a problem with someone discussing a review on their blog and saying why they disagreed with a remark, in general. I wouldn’t identify the reviewer, but if I was discussing something that had been commented on about my book I might say, “One reviewer felt that there wasn’t enough in the book that developed the setting” and then go on to discuss setting, blah blah blah.
To be honest with you, I learn from the reviews. I’ve learned from all the feedback. Yes, sometimes it hurts. Yes, sometimes it’s unfair. Can’t say I’m crazy about getting a review that reads like a personal attack, but when it happens do I really need to say anything? Readers can see it for what it is: A slam. For all I know there could be ten zillion bad reviews or scathing personal attacks out there I haven’t seen. I’m only aware of one, and I got emails from people who expressed venom for the reviewer. I didn’t need to say anything. If reviewers get personal they undermine their own credibility.
Flipping things around, as a reviewer there is one review I regret, and that’s my review of The Last Assassin by Barry Eisler. The reason I regret it is that there was an error in the book that I pointed out in my review. I didn’t cite it as an error, I stated I was confused. This was a case where I was very happy that Barry did explain what had happened – after he’d signed off on the book a typesetter changed a name in one scene. As a result, I thought the person being referred to was someone else… hence my confusion. It was corrected for subsequent issues (I had a first edition hardcover, not an ARC). It was 100% not Barry’s fault, and I felt horrid for him. Things like that, near the beginning of a book, can often do enough to keep you from full submersion, and while it was fair to be confused it was unfortunate I was assessing Barry’s work for an error he didn’t make. It was, otherwise, a great action book and those who like conflicted characters who don’t uphold the law should love the Rain series.
Anyway, this is just my opinion. I think there’s a time, and place. However, it’s also necessary to develop a thick skin. No matter how well you write there will always be people who don’t like your work. They may not be interested in the subject matter. They may prefer something darker or lighter. We all have our own preferences and shouldn’t feel the need to make apologies for them… and we shouldn’t expect others to apologize for theirs.
I’m far more casual about my comments on my blog, because the audience is narrow. I agonize over decisions about what to write in reviews in Spinetingler because those will reach a wider audience. I find no joy in making criticisms when a book falls short.
But this does reaffirm my personal policy – if someone doesn’t ask for feedback, don’t give it. Not unless you know them well enough to survive it. Criticizing how someone writes a book is bit like criticizing how they’re raising their children. The difference with reviews is that we seek them out, we need them to spread the word about our work. And we should just be damn thankful for the ones we get.