book review: "Heat Wave"
Feb. 15th, 2010 05:16 pmRichard Castle [1], Heat Wave
Hyperion, New York, NY.
So, yes, I bought the book.
What can I say? I really like the TV show. Aside from Nathan Fillion, who I could pretty much look at (AND listen to, how rare is that for an actor?) all day, I don't always see the ending coming, and hey, I enjoy the irony of procrastinating from writing by watching a TV show about a writer procrastinating from writing.
So, yes, yes, I bought the book. I made it as far as page 5.
No, really. Five. I would have been able to report that I'd bailed on it at page four, except I ate something that disagreed with my digestive system yesterday and I've made a few more trips to the bathroom than usual, and it was either read a little bit more of this book or read the back of the shampoo bottles again, and the shampoo bottles were all out of reach.
Okay. Here's the premise of the TV show, for those unfamiliar: Castle is a bestselling, very well-regarded mystery author with an entire "NY Times Best Selling" series behind him. He's become stuck in a rut, so he kills off the main character from that first series as a way of forcing himself to move on, and then finds inspiration for the next series in a chance encounter with a (hot) female NYC homicide detective, and he pulls strings with the Mayor (a fan) so he can tag around with her in the name of research. He's funny, she's good at her job, there's chemistry, the supporting cast is excellent, and the cases are interesting and sneaky and not obvious. Works for me.
During the course of the first season, Castle the fictional character finishes (and sees into print, breaking a land-speed record for publishing) the first novel of his new series with the new main character inspired by the hot detective. Being clever, ABC thought it would be cool to produce the actual book. And hey, I'm only somewhat embarrassed to admit I thought it was a clever idea too.
We have, if you will, three layers of reality at play here:
1) the real world, where you and I[1] are readers/viewers, and
2) the world of the TV show where Castle and Detective Beckett are real people, and the book is real, and
3) the fictional world inside the book itself.
Publishing an actual book takes an artifact from layer #2 and moves it in layer #1, and in so doing carries the characters/world of #2 along with it, giving them a "presence" in our world. So, as a reader, if I'm going to suspend disbelief and go with Castle being a real author, and this book he's written being a real book (which is essentially the whole point of the exercise) there's a couple of things I need:
1) If Richard Castle is real, and a well-regarded best-selling author, then I need to believe that he's a good writer, which means the writing shouldn't be skill-less crap that would have a hard time making it out of a slush pile. (Also, a multi-best-selling novelist who can crank out a book of only 196 pages? That stretches my credulity a bit right there.)
2) If Richard Castle is real, and a well-regarded best-selling author, then I need to believe that he knows what he's doing, in which case the first five pages of this book shouldn't be the most unsubtle, irritatingly stupid, borderline offensive, wall of MARYSUE I think I've ever had the misfortune to pick up. If Castle was the writer (and the person) that the TV show wants us to believe he is, he would NEVER be so unimaginative and incompetent as to insert such a thinly-disguised version of himself ("Jameson Rook") into the story where he behaves like an arrogant ass from the very first moment. It intrudes the author into the book in an incredibly ham-handed way, which all but the most woefully clueless writer-wannabes know enough not to do.
I get what ABC was thinking: it's like an episode of Castle with different names, where the main characters get to hook up (I skipped and read the last paragraph; hey, it wasn't like it was going to *spoil* the book!) It's cute. (I guess. Well, no, it's not cute, but it bears the trappings of something that somebody else thought might be. Cutesy, maybe.)
What I wanted was a good mystery book that stood on its own, where the author was present only in the form of their own voice, where the main character had subtle shades inspired by the "real" detective, and which added a little weight to the illusion of Richard Castle as a likable, talented, "real" author. If that had been managed, this would have been a fantastic addition to the overall mythology of the show. As it is, done as poorly as it has been, it manages to drag the show down a little.
Because next time I watch Castle, when I get enough into the story to suspend disbelief (if I do), I'm gonna be thinking: "this guy's really a shit author and an offensive jerk to boot." And I'm going to wonder why Detective Beckett, who has read the book in the show, hasn't just fucking shot him in the nads and claimed it was an accident. And that really spoils the whole damned thing for me.
--
[1] obviously not the real author's name. One expects the real author, should they ever go on to have an actual writing career, will look back with some gratitude at being able to plausibly deny any connection to this book.
[2] hopefully just me, as I would like to believe I was able to warn you in time.
Hyperion, New York, NY.
So, yes, I bought the book.
What can I say? I really like the TV show. Aside from Nathan Fillion, who I could pretty much look at (AND listen to, how rare is that for an actor?) all day, I don't always see the ending coming, and hey, I enjoy the irony of procrastinating from writing by watching a TV show about a writer procrastinating from writing.
So, yes, yes, I bought the book. I made it as far as page 5.
No, really. Five. I would have been able to report that I'd bailed on it at page four, except I ate something that disagreed with my digestive system yesterday and I've made a few more trips to the bathroom than usual, and it was either read a little bit more of this book or read the back of the shampoo bottles again, and the shampoo bottles were all out of reach.
Okay. Here's the premise of the TV show, for those unfamiliar: Castle is a bestselling, very well-regarded mystery author with an entire "NY Times Best Selling" series behind him. He's become stuck in a rut, so he kills off the main character from that first series as a way of forcing himself to move on, and then finds inspiration for the next series in a chance encounter with a (hot) female NYC homicide detective, and he pulls strings with the Mayor (a fan) so he can tag around with her in the name of research. He's funny, she's good at her job, there's chemistry, the supporting cast is excellent, and the cases are interesting and sneaky and not obvious. Works for me.
During the course of the first season, Castle the fictional character finishes (and sees into print, breaking a land-speed record for publishing) the first novel of his new series with the new main character inspired by the hot detective. Being clever, ABC thought it would be cool to produce the actual book. And hey, I'm only somewhat embarrassed to admit I thought it was a clever idea too.
We have, if you will, three layers of reality at play here:
1) the real world, where you and I[1] are readers/viewers, and
2) the world of the TV show where Castle and Detective Beckett are real people, and the book is real, and
3) the fictional world inside the book itself.
Publishing an actual book takes an artifact from layer #2 and moves it in layer #1, and in so doing carries the characters/world of #2 along with it, giving them a "presence" in our world. So, as a reader, if I'm going to suspend disbelief and go with Castle being a real author, and this book he's written being a real book (which is essentially the whole point of the exercise) there's a couple of things I need:
1) If Richard Castle is real, and a well-regarded best-selling author, then I need to believe that he's a good writer, which means the writing shouldn't be skill-less crap that would have a hard time making it out of a slush pile. (Also, a multi-best-selling novelist who can crank out a book of only 196 pages? That stretches my credulity a bit right there.)
2) If Richard Castle is real, and a well-regarded best-selling author, then I need to believe that he knows what he's doing, in which case the first five pages of this book shouldn't be the most unsubtle, irritatingly stupid, borderline offensive, wall of MARYSUE I think I've ever had the misfortune to pick up. If Castle was the writer (and the person) that the TV show wants us to believe he is, he would NEVER be so unimaginative and incompetent as to insert such a thinly-disguised version of himself ("Jameson Rook") into the story where he behaves like an arrogant ass from the very first moment. It intrudes the author into the book in an incredibly ham-handed way, which all but the most woefully clueless writer-wannabes know enough not to do.
I get what ABC was thinking: it's like an episode of Castle with different names, where the main characters get to hook up (I skipped and read the last paragraph; hey, it wasn't like it was going to *spoil* the book!) It's cute. (I guess. Well, no, it's not cute, but it bears the trappings of something that somebody else thought might be. Cutesy, maybe.)
What I wanted was a good mystery book that stood on its own, where the author was present only in the form of their own voice, where the main character had subtle shades inspired by the "real" detective, and which added a little weight to the illusion of Richard Castle as a likable, talented, "real" author. If that had been managed, this would have been a fantastic addition to the overall mythology of the show. As it is, done as poorly as it has been, it manages to drag the show down a little.
Because next time I watch Castle, when I get enough into the story to suspend disbelief (if I do), I'm gonna be thinking: "this guy's really a shit author and an offensive jerk to boot." And I'm going to wonder why Detective Beckett, who has read the book in the show, hasn't just fucking shot him in the nads and claimed it was an accident. And that really spoils the whole damned thing for me.
--
[1] obviously not the real author's name. One expects the real author, should they ever go on to have an actual writing career, will look back with some gratitude at being able to plausibly deny any connection to this book.
[2] hopefully just me, as I would like to believe I was able to warn you in time.