Showing posts with label Jim Butcher. Show all posts
Showing posts with label Jim Butcher. Show all posts

Thursday, August 4, 2011

Book Review: Ghost Story By Jim Butcher

SPOILER LEVEL: Medium
(Very mild spoilers for Ghost Story itself but major spoilers for all of the books that came before it in the series.)

Now this is my kind of ghost story. I guess it is not uncommon for the main character of a book to start off dead, but it is pretty rare in the books that I tend to read. Jim Butcher makes it work, however, and he does so in an inventive and entertaining roller-coaster ride of a way. 

When I finished reading the last book in The Dresden Files series, Changes, I was curled up in bed and it was rather late at night. I still got up an ran to my computer the second I closed the cover to make sure that it was not, in fact, the final book in the series. You can see where ending the story by killing off the main character, the character who is the narrator of the books, would make one worry. Imagine my great relief then, dear reader, as my trusted friend the internet told me that there would indeed be a next book. That it was available to pre-order on Amazon already, even. Phew. HUGE sigh of relief. I went to bed that night surprised and shaken, but reassured that my questions* would be answered in time.

The most pressing of those questions, of course, being a tie between "Is Harry really dead?!?" and "Who killed Harry Dresden?"

Ghost Story manages to eventually answer both of these questions, along with a slew of others that you might not have even thought to ask. That right there is the true genius of Jim Butcher. It starts out just after Changes left off--with Harry dying. He finds himself in the tunnel with the bright light, but from there things stop going where he was expecting them to go. He is informed that he is "Between" (as in between life and death) and has been brought there because the party responsible for his death somehow cheated. Harry must find his killer and set things right before he can move on. Being Harry, of course, he gets a bit belligerent and threatens to drag his heels. Until he is informed that if he doesn't complete this task, three people he cares about very much will die. 

Best way to convince Harry Dresden to get his butt in gear? Show him a threat to the people he loves and has sworn to protect.

Of course it isn't really that easy. This is Harry we're talking about, nothing is ever that easy. And nothing is what it seems either. As a spirit, Harry has to learn a new set of rules and seek out a different sort of ally than he is used to working with. By the time he does manage to track down the pals from his life, he is presented with a whole new set of problems that keep getting in the way of his mission. For starters, Harry has been gone for six months by the time his spirit gets back to Chicago. Quite a bit has gone down in that time, largely as a result of his destruction of the vampires of the Red Court just before his death. Not only does Harry have to learn the new status quo of being a spirit, he has to learn how to deal with the new status quo among the living, which presents its own challenges to getting both his mission done and to helping his friends with their own problems.

Going in to Ghost Story, most readers will have the expectation of a fairly obvious endgame (I know that I did). That being the restoration of Harry to his body, and as a result, his regular life. After all, Jim Butcher has gone on the record as stating that he expects there to be about twenty-three books in the series when all is said and done, and Ghost Story is only number thirteen. I am not going to tell you whether or not that happens. I will tell you this: There is no reset. The old status quo is gone, broken, crumbled into microscopic pieces and brushed away to make space for the new order. I can't wait to find out just what shape that new order takes on. 

As a book in The Dresden Files series, this is a top-notch entry. Harry is at once both at his most vulnerable and most badass. We've seen him beaten down before, at a huge disadvantage and about to go up against insurmountable odds. We've never seen him do it quite like this--completely out of his element in a way he could never have imagined he would be, alone even when surrounded by his friends. If you love watching Harry get creative in order to get himself out of a pickle, this book is right up your alley. Ghost Story is the kind of tale most writers of series can only hope to write to close out their worlds. This is just the middle of the series, and Butcher left me with every confidence that things are only going to keep getting better. I'd call that pretty damn impressive, myself.

As just another book, to those not familiar with the series itself? Well, I could be a bit biased, but I think that Ghost Story still holds up. The story itself is amazingly solid. Certainly it relies on all that came before it, but Butcher does a wonderful job of giving in explanations for things a new reader might not know (or an old reader might have forgotten) without interrupting the flow of the narrative and without being annoying to those of us who (theoretically) already know this stuff. You know those "previously, on" segments at the start of so many television shows these days? Yeah, it's nothing like that. I think someone who just happened to wander into a bookstore and pick up Ghost Story, or who received a copy as a gift, might be a little confused here and there, but not enough so to lose the thread of the story at all, the narrative does such a good job of moving forward and keeping the reader completely immersed and intrigued about what comes next. Would I recommend this book as a starting point for someone looking to pick up The Dresden Files? Hell no. But I do think that someone who just wandered into it first would still enjoy it, and would be quite likely to want to go back and check out the series from the beginning.

As I flew through this book (and make no mistake, fly I did, finishing it in four days, with the rest of my life still happening), there were only two things that bugged me at all. The first was, of course, that rather "obvious" conclusion that I assumed the book was heading towards. But I was curious enough about how Butcher would get us there (or even, after a certain point, if that was where it was headed after all) that I was more than willing to just go along for the ride and let the story unfold. The second was something that seemed like a glaring omission on the part of Butcher--a character that should have been mentioned or at least thought of by Harry almost from the start and who seemed to have been completely overlooked. I won't lie, I  was mad about that omission--until I got to the part where the omission was revealed to be quite deliberate and I was given the why of the matter, a very satisfying why, as it turned out. This is the kind of book where, if you are paying attention, you think you know exactly where it is headed, but don't mind reading on anyway to get there. Then, when you least expect it, you are rewarded with a sharp left turn that you totally didn't see coming. Even when my suspicions were on the right track, I really didn't know the half of it.

I can't imagine that someone who has been reading this series wouldn't want to pick this book up, at least not once they had gotten to Changes, but if you have been dithering, I promise you, you want to go get this book now. Right now. Go ahead, I'll wait....There. See? Totally worth it, wasn't it?

*The truly clever thing about Changes was that the manner in which it ended managed to completely distract me from asking or even thinking about one very important question in particular. I suspect most people also forgot to ask this question, or asked entirely the wrong question about this situation. Butcher is a sneaky bastard who did this on purpose, and wow, does it pay off at the end of Ghost Story.

Tuesday, November 16, 2010

Can Spoilers Go Too Far?

Don't forget to watch the all new episode of Stargate Universe, tonight on Syfy at 8 pm CST!!!!!

~*~*~*~

Also, check out the newest episode of Riese:  Kingdom Falling right here!

~*~*~*~

Warning:  This post is about spoilers.  It might therefore be reasonable to assume that it contains spoilers.  

 (Mostly for Stargate Universe, but also a little bit for the BBC show Luther.)

~*~*~*~

Spoilers, you say?

So, remember last week in my review of the SGU episode The Greater Good I said it pretty much looked like Ginn and Perry had been killed by Creepy Lucian Alliance guy? Then, the day after the episode aired, a bunch of people from the show (most notably David Blue and Joseph Mallozzi) went on the record telling us not to jump to conclusions, and we didn't know what we thought we know?

Sure, a couple of the trailers for tonight's episode have made it look pretty convincing that those characters are now ex-characters, but that could all just be down to editing.  Then, yesterday, I am perusing the weekly What to Watch article on io9, and imagine my surprise to find that this is the synopsis for tonight's episode:

Simeon makes his escape from Destiny after killing Ginn/Amanda Perry, sending Nicholas Rush on a vengeful mission. But Young and Greer attempt to retrieve Simeon unharmed.
Well.  That seems pretty darn definitive.  

Then, yesterday afternoon, I was catching up on Sunday's episode of Luther, which is a really fantastic miniseries that has been airing on BBC America for the last few weeks.  I was fast forwarding through the last commercial break of the episode and stopped when I got to what looked like the return of the show.

Except, that's not what it was. 

It was a preview for next week's episode, which for some reason BBCA decided to air before the episode was actually over.  In this preview, we see that Luther's wife Zoe has been murdered by his crooked cop pal and framed for the crime, and now Luther is on the run trying to prove his innocence.  My brain exploded a little bit.  When last I saw Zoe, before the break, she was alive and well.  After the preview, the episode wrapped up, giving us the big climactic scene wherein the crooked cop kills Zoe.  But the scene had lost all of the tension that the show had worked so carefully to create, because I had just seen an ad for next week and knew that Zoe didn't make it.  It really killed the end of the episode for me.  At least next week's ending won't be spoiled in the same way, since it's the final part of the series and there won't be any previews to show.  But still.

All of this got me thinking about spoilers and how they have wormed their way into the mainstream in the last few years.  Do television viewers truly not want any more mystery in their shows?  Is it just that the people who make the preview trailers aren't paying attention and put in something they think will grab viewers without realizing it gives away the ending of the episode?  

I really don't understand the thought process that went behind the programming decision to air the preview for the next week's episode before the episode had actually ended.  Granted, this series had already aired in its entirety across the pond in Britain earlier in the year.  Maybe somebody just figured that it was technically a rerun and spoilers were off the table? 

Then again, BBCA isn't the only network doing that, now that I think about it.  Psych on USA usually had their ad for next week before the last bit of the show as well.  Although usually the bit after the last break for that show is a wrap-up and all of the big reveals in the episode have happened already.

As far as preview trailers go, I know I've seen quite a few that have raised the ire of actors or writers from a given show.  They feel like they worked hard to make a really cool episode that would keep you guessing, and then someone with some editing tools somewhere went and cut together a teaser that doesn't tease but in fact totally gives it all away!  (The return of Carson Beckett in season four of Stargate Atlantis, anyone?)  What, then, is the point of bothering to watch the show?

The really good teasers do just that.  They hint at what the twist might be, and the best make you think it is something completely different from what it actually is, so that when you watch, you really get the full effect of the reveal.

I mean, I am all for spoilers for the most part.  I tend to see them as harmless fun that gets me excited for the new show.  I mean, heck, I read a daily article on io9 called Morning Spoilers after all.  But I very rarely read the whole thing.  I tend to skim, and only check out the entries for shows or movies that I like or am anticipating.  But if it's just an episode synopsis of, say, the sixth episode of the season that hasn't started airing yet, or an actual reveal about a big plot point, I try to skip it.  The spoilers I am usually looking for are casting scoops, or a general idea of where a show is headed for a season (as in, the vague overarching plot).

So, I guess when I say I like spoilers, I mean I like hints.  The problem is that the hints tend to get roped in with the really big ruiners and it can be hard to separate them without stumbling across some of the latter.  Sure, it's my own fault for reading the spoilers page in the first place, or the comments on a discussion thread or whatnot, but I do like to have a general idea of what could happen.  It's knowing that something is probably coming, but not knowing how it's gonna end up happening that makes it worth watching.

I have this problem with books a lot too, actually, because I read so many series.  I remember one of the first fantasy series I really dug into in college, I had read the first two books (out of six) and went to the store to pick up the rest of the series before I went out of town on a trip.  I read the back jacket of the fourth or fifth book, and it totally gave away the ending of the book I was reading at the time.  I was so appalled!  What made it worse was that it was a plot development I had seen coming and was really hoping would end up not happening.  So I was grumpy reading the whole rest of that book.  Now, I don't even look at the back cover (or inside flap) of books in a series unless it is the first book and I am trying to decide whether to pick up the series or not.  I realized the other day when putting away a book I had read multiple times that I had never read the story blurb on it.

But sometimes, even if you're someone who goes out of your way to avoid spoilers, you can't escape them.  Like when it's right there in the commercial before the show is over (and the networks are pushing you to watch things live), or when the usually spoiler free preview for next week instead gives away the big reveal at the end of the episode.  Heck, I love the author Jim Butcher, and as much as I enjoy The Dresden Files series, I completely adore his Codex Alera series so much more.  But once I read the first couple of books, and looked at the titles for the next few books, I realized that the actual titles of the books themselves are kind of a spoiler.  It's crazy!

I have really struggled with this in my reviews of the Star Wars Republic Commando series that I have been doing on this blog.  I've tried to discuss the primary plot of each book without giving away any of the really cool stuff that actually happens in the story.  For example, there's one plot line throughout the series which I totally left out of my review, as much as I wanted to expand upon it, because I just felt it would not be doing right by the readers to tell them that it happened before they read the book. 

I'm just left wondering, can spoilers actually go too far?  It's right there in the name, isn't it?  Spoilers.  If you're looking at something labeled "spoilers" aren't you asking to find more than you're probably looking for?  I do know that it's not fair to inflict spoilers on someone who isn't suspecting them.

I know, I know, life isn't fair.  Sigh.  But don't you kind of wish it was?

Anyway, I don't really have any answers on this topic, it has just been on my mind, and I wondered if anyone else hangs out in the middle of spoiler-land like I do.  I'll just be floating around, trying to figure out the best way to cope without letting all of my fun get ruined, I suppose.

No word count update today.  I did a lot of world-building yesterday but no actual writing, sadly.  On the other hand, I now know exactly what the paper is made of in the various countries in my story.  I also know what kind of fabric they use and what they eat, and how their language evolved.  Whee!  In that sense, my word count from yesterday is huge, because I added to my notes like crazy, but nothing in the story sad to stay.  Still, I am right about on track, and I think at this point it's very important to get my ducks all in a row in the notes so that I don't have to stop to look things up when I really get into the wrapping-up part of things.

Ta ta for now, folks.  Join me tomorrow, when we'll find out if Ginn and Perry really are dead or not.  (And you'll get to see me express my rage or amazement about how it was pulled off if they really are still alive.)

Monday, October 11, 2010

Monday Tidbits

Well, while I actually had a lovely weekend, I am really just not feeling it today.  Between the arrival of Fall kicking up my allergies and the cold my husband had last weekend, I am now in the hacking up my lungs stage of my own cold.  Whee.  I went ahead and gave in to the siren song of DayQuil, and while this is mostly good news for the alleviation of my congestion, it does mean I am nowhere near coherent enough to write anything of substance today.

So, I offer you up a few random tidbits for your perusal and enjoyment today.

Here is the finished blanket I was working on last week.  Now that its been given to the recipients I can share it with you.

Cocoa Waves by Cori 2010.

Pattern:  Hi-Five Towel by Sarah C





And yeah, you're reading that second caption correctly.  I did use a dish towel pattern for this blanket.  It is just a really awesome pattern, and after making a few towels with it, I wanted to see how it looked in a bigger piece.  I am really really pleased with how this one came out.

Yesterday I finished the birthday gift I was working on, so I'll have photos of that after it's been given.  My crochet plan for this week is to make my sister's October swap squares and that is it.  I think I am going to take a mini-hiatus from crochet for the rest of the week at least.

For the Star Wars fans out there, I stumbled across a couple of cool links over the weekend.  First, a little insight into what we can expect for the third Robot Chicken Star Wars special.   Color me excited about that.  Also, io9 got hold of some interesting behind the scenes trivia from the original trilogy.  It's a fun little read.  I certainly didn't know that Yoda was originally intended to be played by a monkey in a mask.  Though I am very glad that they ended up bringing in Frank Oz instead, to be sure. 

Also, the New York City Comic Con happened this past weekend.  One of Tor.com's writers attended a panel of science fiction and fantasy authors and did an awesome write-up on it.  Be warned, this is a very long article, but well worth the read.  It features, among others, Jim Butcher (The Dresden Files, Codex Alera), Naomi Novik (Temeraire), and Brandon Sanderson (who is finishing up the Wheel of Time series). 

And on a slightly more serious note, looks like Congress is entertaining a bill that would give the Attorney General power to shut down any website that he thinks infringes on any sort of copyright.  The bill gives a very broad definition of infringement and not only would sites be shut down but their creators would be permanently blacklisted from creating internet content.  Sylvia Bond over at Pink Raygun has a write-up that goes into how this will affect the online presence of fandom across the web, as well as just Joe Schmoe net users.  If you're interested in signing the petition against the bill, you can do so here.  It looks like the bill has been delayed for now, but it doesn't hurt to sign the petition if this is something you care about.