Showing posts with label Dresden. Show all posts
Showing posts with label Dresden. Show all posts

Friday, October 16, 2020

The Cuckoo's Calling (a book review post)

 

Let's get the issue of Rowling out of the way before I get into the actual book review. First of which is to say that I'm not going to discuss Rowling beyond saying that the fact that she doesn't know when to shut her mouth shows that having lots of money can affect the way that anyone views themselves and the world. She's at that stage where she believes that she, because she is who she is, is right and doesn't need to listen to other people, so she has continued to dig her hole bigger and bigger rather than just shutting up and keeping her opinions to herself. That she didn't shut up shows an amount of entitlement which is disappointing.

The other thing I want to say is that I started reading this book... well, so long ago that I don't remember when it was. I picked it up during some free promotion thing just to check it out and have been reading it in bits and pieces ever since. It's on my Kindle, and I don't really read from my Kindle all that often. I don't carry it places with me like I do physical books, so I lag a lot with books on there unless they are really engrossing. Which tells you that this book was not. Seriously, I've been working on it for over a year, maybe closer to two.

What this book has taught me is that I need to read some Agatha Christie, something I've been meaning to do for a long time and have never gotten around to. Maybe I don't like detective novels? I don't know. I like Butcher's Dresden books, but they're hardly detective novels after the first few. Beyond those, I can't recall any mystery novels I've ever really liked, including this one.

Which is not to say that I didn't like it, I just didn't much care for it. Rowling doesn't make it possible for the reader to really solve the mystery as they're reading, which seems to me to be the point of detective novels, because she doesn't reveal crucial information until the actual reveal at the end of the novel, and the reveal was one of the most contrived things I've ever read. And this is an ABSOLUTE SPOILER, so turn away now if you don't want to know who the killer is...

I'm waiting...

Still waiting, because I'm absolutely serious that I'm going to spoil the ending of this book. And let me just toss out there that I never spoil a book that I think you ought to read. If I spoil it, it's because I don't think it's really worth your trouble.

Having said that, the book itself was just fine. By that, I mean it's readable. Mostly engaging, though not engaging enough to prompt me to read it more quickly. It's... typical. Down on his luck private eye getting a high paying, juicy case which might just get him out of debt. Your basic story about an underachiever finally getting a break and getting to show the world who he really is. Honestly, after Harry Potter, I expected something less... cliché.

So the book goes along with our detective -- the son of a famous rock star, seriously? -- gathering up evidence about a case that is several months cold. And closed. But he's hired by the brother of the murdered woman because the brother believes it was a murder though the police ruled it a suicide. And this is the hitch and what I'm sure Rowling thought would make it a clever story: the brother is the murderer. So Strike is hired by the murderer to discover who the murderer is. The motivation for this is never explained adequately since the murderer had already gotten away with the crime.

What the novel mostly does, as most mystery shows do (I don't know about mystery novels, as I said, but I have watched a lot of detective shows) is to show that everyone had a motive for killing the victim. Rowling walks us through the suspects over and over again almost always strengthening the case for why each person might have wanted Lulu dead. In fact, the only person not shown to have a motive, not until the very end of the book, basically not until just before the reveal, is the actual murderer. Of course, the motive is money, but we don't get to find out the murderer's money issues until Strike is sitting alone in a room with the murderer revealing all the things the murderer already knows.

The reveal was clumsy and contrived. The fact that Bristow (the murderer) sits through Strike's walkthrough of the entire crime is, frankly, unbelievable. The fact that Bristow then attacks Strike is even more unbelievable considering that Strike is a bear of a man and ex-boxer while Bristow is your very stereotypical account type, even though he's a lawyer, not an account, a "gag" that is run into the ground over the course of the book.

I want to say that Rowling's strength as a writer is her characters but, as I'm thinking of this now, she has no real strength in that, either. Her character's tend toward the stereotype, including pretty much all of the characters in Harry Potter. In Harry Potter, we're able to overlook that, though, because the world is so new and interesting, but this world, the world of C. B. Strike, is not new or interesting so the fact that all of the characters are two dimensional really stands out. The most real character in the book is Strike's temporary secretary, Robin, and she's really just a pale reflection of Hermione Granger.

Also, the title of this book is stupid. It's just tossed in somewhere over the halfway mark of the book that "Cuckoo" is a nickname of the murdered woman that only one character in the book ever called her. It's a throwaway excuse to have "Cuckoo" in the title. Without that very vague reason, the title of the book is meaningless.

So, yeah, I suppose I am actually disappointed with this book and don't really understand all the praise for it. Again, maybe I just don't really like detective novels; I don't know. This book doesn't inspire me to try more, though.

Thursday, October 25, 2018

Skin Game (a book review post)

Am I all caught up now? I think I'm all caught up now.
Actually, I know I am, because I checked. I'm so caught up there's not even a release date for the next book. And, my goodness, there are a lot of these now!
Butcher seems to be playing quite the long game with the series at this point, each book moving the over-arching story a few inches closer to wherever it is he's going with all of this, which may be feet or may be miles away.

My biggest criticism about this book remains the issue of Dresden and his association with pop culture. I get that it's part of Butcher's schtick with Dresden, but it's gotten beyond the stage where it makes any sense, if it ever made sense. I mean, come on, Dresden has been stuck on an island in a cave for a year (at least) when this book starts but, yet, Dresden is still up to date on the latest pop culture references. And, yeah, it's funny (to an extent) but, now that I've noticed that Dresden shouldn't be aware of any of this, I can't get it out of my head as I read. Plus, in this one, the parkour joke ran on a bit far. Running jokes should be more related to sprints than to marathons.

So, yeah, that's the biggest fault I found with this book. In fact, this is the first book in a while where I felt Butcher was really hitting his stride (and we all know how long Dresden's legs are, so that's saying something), again, with Dresden, pop culture aside. Maybe it was dealing with the Nicodemus and the Denarians again or, maybe, it was having Michael back. Maybe, Butcher was just hitting the right beats. Maybe it was the absence of vampires, not that I don't like Thomas, but there have been a lot of vampires for a lot of while in these books, and there wasn't anything like that this time. No stuff with the council, either.

Oh, wait, there was one other thing:
A clever author will hide a twist in a story in plain view by giving you the pieces of the puzzle but in such a way that you don't really know what you're seeing or how to put them together. A good example of this is The Sixth Sense. When the reveal happens, you kick yourself and realize you should have seen it the whole time.
A not so clever author hide the twist by hiding the pieces so that you can't figure it out at all. Sure, I suppose you could guess the twist, but that's just guessing. A good example of this is The Illusionist, a movie which has, like, 10 minutes of flashbacks during the reveal to show you all of the things it didn't show you during the movie.
And that's what Butcher does here, stops and almost literally says, "Oh, here's what I didn't tell you about that happened earlier in the story." There are ways you can make that work but probably not in a first person narration where the narrator is the one holding stuff behind his back.

Anyway... I suppose I got over that bit fairly easily because I almost forgot to include it at all despite the fact that I was quite annoyed at that point in the book.

This book feels like it has a lot of significant events in it. Little events. Not huge things like when Dresden died or when Dresden became the Winter Knight but lots of little things, all of which would be spoilery, so I'm not going to mention them. And there's one thing that happened that the un-happening of is never mentioned, though it's kind of implied that the un-happening happened, but that also seems like it should be more significant than to mention that it happened, or un-happened, and I don't know if it's significant or not! And it's kind of niggling at me and I want to know what it means!

Damn you, Butcher!

Well, as I'm sure I've said before, if you're a fan of the Dresden books, you're almost sure to like this one. If you're not a fan, it's probably because you haven't read any of the books. Or... well, I'll just say it: There's probably something wrong with you.

Wednesday, August 13, 2014

An Exploration in Fantasy -- Part Four: The Darkest Hour (an IWM post)

Along our fantastic fantasy journey, so far, we've learned that we're special and could be the prophesied one, among other things. We've met a mentor and found some friends. We've also gone on a journey, probably in search of something. Hopefully, it's a been a learning experience, and we're fully prepared to meet the final challenge. It's a dark time for the rebellion, after all.

From the initial list I made (which you can see here), we need to cover three more points:

* * *

And, like always, to find out what those three more points are, you will need to hop over to Indie Writers Monthly. This one is all about technology and dark lords. Go read!

Monday, August 4, 2014

An Exploration in Fantasy -- Part Three: Who's Gonna Learn Ya? (an IWM post)

There's no teaser, today, for part three of my exploration into the origins of the modern fantasy arc. If you want to read it, you'll just have to go right over to Indie Writers Monthly and do that. And you totally should.
Today, we really get into what's Tolkien and what's not.

Go, now, and read THE POST!

Thursday, January 23, 2014

Turn Coat (a book review post)

Turn Coat by Jim Butcher may be the first of his Dresden novels that I am truly ambivalent about. On the one hand, I really enjoyed reading it. On the other... let's just say it has some problems. And this is going to be spoilery. Be warned.


The easy stuff:
The editor needs to go back to editing school. The comma usage was distracting. Not everywhere but enough that they frequently made me stop and say, "Why is there a comma here in the middle of this sentence?" To write that as it would probably appear in Turn Coat: "Why is there a comma, here in the middle of this sentence?" or "Why is there a comma here in the middle, of this sentence?" I shouldn't be stopped by oddly placed commas. Just sayin'.
[And, yeah, I know; most people will not be stopped or even slowed down by the commas, but I kept tripping on them, and that was annoying.]
Anyway...

As with all of the Dresden books, I found this one an enjoyable read. I mean, I found the reading of it enjoyable. I find the character of Dresden enjoyable, and I really want to see where Butcher is taking us on this meta-plot he has running. However, whenever I stopped to think about this one, I would become annoyed.

As the title may indicate, this book deals with the idea of a traitor. Specifically, there is a traitor in the White Council. Okay, fine, I can deal with that. The issue here is that for the story to have any meaning, any impact on the reader, it really needs to be a character we've already met. For it to really mean something to the reader, it needs to be a character we like, even if it's a minor character. Yes, that would mean that Butcher would have to mess up the life of one of his characters, but that's what writers do, right? Evidently, that was too much to ask of Butcher because, about 1/4 of the way through the book, we're introduced to a completely unlikable character that Dresden immediately has issues with. The astute reader knows at that moment that that is the traitor. So, yeah, at not quite 25% of the way through the book, I knew where it was going, so there was this pervasive disappoint as I read. I just kept hoping that maybe I was wrong and it would actually be someone like Ebenezer and we'd all be shocked, but I knew that it wasn't going to be anyone like that.

So, you know, great, Butcher introduced a character that we didn't like just to kill him off. No emotional payoff at all.

There are some other things that don't make a lot of sense, either:
1. Why in the heck is the skinwalker working for Peabody? The skinwalker is some ancient evil creature; why does it care at all about what Peabody wants? [Granted, this may become more clear as the scope of the Black Council is revealed, but it felt more like Butcher just needing to up his game from the previous bad guys Dresden has had to fight.]
2. Why does the skinwalker kidnap Thomas? This doesn't actually make any sense within the context of the story or the skinwalkers behavior throughout the rest of the book. He just shows up and takes Thomas and leaves. What the heck? Sure, I get that Butcher wants this traumatic event to happen to Thomas to get him to embrace his vampire ways, but none of what happened felt genuine.

Also, there's the issue of the Black Council. This is probably not an issue for other readers so much, but it reminds me too much of the Black Aes Sadai (I think that's what they were called; something like that, anyway) from Wheel of Time and the black whatever they were from Sword of Truth. I'm not saying that he copied the idea, but it just feels like the same concept going on, and I find that particular thing annoying.

On the other hand, there is the ending where Dresden actually lives up to the title of the book, a thing which I'm not going to explain, but, at least, the whole turn coat thing wasn't just about Peabody. That said, I think what I need from Butcher with these books is for them not to keep feeling like Butcher is screwing with Dresden for the sake of screwing with Dresden. The thing with Thomas just feels like one of those things where they have a good relationship and, so, you have to screw it up, because the main character isn't allowed to have good relationships, and Butcher had to contrive a way for that to happen. A way that felt contrived. The same with the stuff with Anastasia.

So... I enjoyed the read but am annoyed by the book overall. I'd say it probably comes in at a C+ for me.

Thursday, September 27, 2012

Taking Out the Trash ( a further reflection on objectivity)

The ability to separate the subjective from the objective is something that most people cannot do. Okay, maybe "cannot" is the wrong word, but "do not" is certainly accurate. Actually, I think "cannot" is accurate, but I think it's only accurate in that most people have never learned to do it. Studies tend to indicate that many people simply cannot learn the skill, though, but I'm not sure if I'm willing to go that far. At any rate, for our purposes here (or my purposes, at any rate) "cannot" is the applicable word.

When doing reviews and making suggestions, I think this is something that's invaluable and something that needs to be distinguished. There is a difference between "I like this" and "this is good." Good, in this sense, being a qualitative, objective measure.

Most people don't see it that way, though. For most people, if they arrive at "I like this" it also means "this is good" and, likewise, "I don't like this" means "this is bad." This is why "everything is subjective" has become such an important mantra for writers and, well, all the arts. It's just not that easy, though, and people really do need to learn how to tell the difference between what is good and what they like.

Michael Offutt often talks about all the trashy TV he likes to watch. He kind of even glories in it sometimes. One of the things I really appreciate about him is his ability to say, "Hey, this is trash, but I like it anyway." That's an amazing thing that you just don't see a lot of people doing. You don't see people doing it, because, if they like it, they, for whatever reason, need to defend it and elevate it above trash. As my wife says, "It's okay to like trash as long as you acknowledge that it's trash."

Sir Peter Stothard, the chair for this year's Man Booker Prize, says, "It is wonderful that there are so many blogs and websites devoted to books, but to be a critic is to be importantly different than those sharing their own taste... Not everyone's opinion is worth the same." He adds, "As much as one would like to think that many bloggers opinions are as good as others, it just ain't so." As snobby and elitist as it may sound, I agree with him.

After all, there is a reason we go to a doctor when we're sick and not the grandmother down the street.

There is a reason we talk to astrophysicists about the origin of the universe and not the backyard astronomer next door.

Not everyone's opinion is worth the same.

Sure, only you can decide what you like, but you liking it doesn't somehow make it better than it is. A turd is still a turd even if you paint it gold.

No, all of this doesn't take away a degree of subjectivity that hangs around any artistic endeavor, but it's not all subjective, and people kind of need to own up to that.

For instance, even if you don't like The Lord of the Rings, you can't actually deny that it is a great work. Well, you can try, but that's sort of like trying to deny that 2+2=4. This is not a subjective view. Tolkien did something in creating Middle Earth that has never been equaled. The scope of his creation is staggering, the writing is intricate and wonderfully descriptive, the tale is timeless. I get that it might bore some of you, but your personal reaction to it doesn't make it "bad" as much as you might like or want to think so.

Also, as much as you might like The Hunger Games or Fifty Shades of Grey, it doesn't make it "good." It's kind of like eating candy or smoking; just because you like it doesn't mean you should try to fool yourself into thinking that it's good for you. Just own it. "This is bad, and I like it."

All of this brings me to the point, which is something I've said before, but I want to make clear again: my basic way of evaluating books. I say basic because it is a little more complex than this, because not everything breaks easily into good or bad or like or dislike, but I'm sure you can get the idea. So here is how I look at a book as I'm reading it and, then, reviewing it:

  1. This is good, and I like it.
  2. This is good, but I don't like it.
  3. This is bad, and I don't like it.
  4. This is bad, but I do like it.
This is important because, as I said back at the beginning, most people can't differentiate like this. Most people see "like=good" and "dislike=bad," and those things are not necessarily the truth. Yes, it is true that most often, if something is good, I will like it, and, if something is bad, I won't like it. BUT
As my wife says, I like the Dresden books, and it's debatable as to whether those fall into the "good" category. They are decidedly pulp fiction, that's how they're written, and many people consider that a lower art form, which goes back to subjectivity, but they're well written pulp fiction, and Butcher does deal with important issues. His problem is that he can get preachy about them and go on for pages, and, then, it falls into the category of bad, because he's stepped outside of his story so that he, the author, can lecture us. But, see, I like them anyway. My wife does not. They are my junk food books when I just need something fun to read. But, see, I know that, and I'm not trying to make them into more than they are.

The complication of all of this is that good and bad are opposite ends of a spectrum as are like and dislike, so it can all get kind of muddled. However, it is important to at least make the attempt to separate your subjectivity of an experience from the objective reality of it. Like being scared of a roller coaster. Subjectively, you may be so scared you're peeing your pants, but, objectively, you can look at the thousands and thousands of people riding and not dying and know that the chance of you dying is actually pretty small.

Sunday, September 23, 2012

What Makes a Favorite Author?

When I was younger, a favorite author was all about favorite books. That seems like a natural thing, right? You have some favorite book, so the author of that book is your favorite author. It was all dependent upon the book.

So, in high school, my favorite authors were Tolkien, David Eddings, and Piers Anthony. Tolkien is probably self-evident enough that I don't need to explain him, but, even if not, I'm not going to explain him. I started reading Anthony during middle school. A friend of mine gave me one of his books, Split Infinity (a great title), as a birthday present, and I started reading everything he'd written. I followed him for years. I didn't quit reading his books because I quit liking him; there was just always something else I wanted to read more, because, well, it, whatever "it" was, was better. Eventually, I quit buying his books, and I haven't read anything new by him in nearly 20 years. Why? Because, honestly, his books just aren't all that good. At one point, I tried going back and reading some of the ones I'd loved as a teenager, and it made me wonder about myself. I mean, what was I thinking?

And then there was Eddings...
Eddings is the reason this post came into being, but that post is actually going to be the next post, because it made me think of this post instead. Eddings is all because of The Belgariad. I love The Belgariad; it's one of my favorite series ever, and, for a long time, I gave credit to Eddings as being one of my favorite authors based on my love for that series. But, you know, that's really all he has, and there came a time when I gave up on his books, too, and not just because there were other things I wanted to read more.

The whole "favorite" thing is tricky, which is why I don't have any favorites lists, but you can pop up to my "Of Significance..." tab to find out more about that.

Anyway... I remember when I realized that I couldn't claim Eddings as a favorite author anymore, not that I remember when it happened, but I remember it happening. I still loved The Belgariad, but I also realized that nothing else he did was ever going to be that good, or, even, close to that good, and I felt kind of betrayed. How could I love this one series so much and the author not be one of my favorite authors?

I had separation anxiety. Author/book separation anxiety to be exact. But that's really the point, an author is not the same as his work. That can be a hard thing to understand as a fan and as an author as so often we take someone's displeasure of our work as a personal attack. Well, sometimes that does happen, but, mostly, it's about the work.

These days, I'd say my top three favorite authors are Tolkien, Mary Doria Russel, and Neil Gaiman (yeah, I know, Tolkien hasn't changed and isn't likely to). I should probably make that four and include Stephen Lawhead. The interesting thing? There's not a book by Gaiman that I would point to as one of my favorite books ever. However, I love his style, and, pretty much, I will read whatever he puts out. Right now, anyway. The same with Lawhead, overall, although that could change after his Bright Empires series (you can read the review of the first one here). I wouldn't say any of Lawhead's books are among my favorite books ever, either.

And, then, there's Richard Adams and Watership Down. Watership Down has been one of my most beloved books for 30 years, and I know it is, because the only book I've read more than it is The Hobbit, but I've never considered Adams one of my favorite authors. He just wrote a book that I love.

I suppose what I'm getting at here is knowing how to separate what is a book you love from who is an author you love. What makes someone an author you love? For people that don't read much, it can really just come down to the author of their favorite book, like, right now, I bet there are women all over the place that would call that James woman their favorite author. But, for those of us that do read a lot, and read authors that write a lot, how do you deal with the disappointment of a bad book or string of books from an author you want to call your favorite? Do you cling desperately to calling that author your favorite even though s/he is writing stuff you hate, or do you toss that author aside in favor of some new shiny author that hasn't had the chance to disillusion you yet?

I'm not even sure that "favorite" is a term I can adequately use anymore. There's Jim Butcher and his Dresden books, and I love those. That's my "favorite" series fiction at the moment, and, when I was younger, that would have meant that Butcher made my favorite author list, but not anymore. His books are my popcorn, and, though I love popcorn, I don't want to live off of it. I need stuff with a little more substance and a little more to say as my regular diet.

Anyway... where I am now, my "favorites" are the authors that I read and think "wow! I want to write something that good some day. I want to write like that." However, I will never write like Tolkien. I'm not sure anyone ever will again. What I'm saying is that the author doesn't have to write my favorite story, s/he just has to write excellently. Sometimes, it's difficult to separate those things. At some point, maybe Gaiman will write a book that affects me like The Sparrow did, but it's not something he needs to do for me to look at the way he writes and really admire it. I might love The Belgariad, but I don't want to write like Eddings.

I don't normally do the whole question at the end of the post thing, but I am this time, because I'm curious as to how this works for you guys. Are your favorite authors just the writers of your favorite stories? Do you have favorite authors that have not written any of your favorite books? What do you do when a favorite author falls off the author wagon (starts producing the same old crap over and over again)? Who are your "favorite" authors/books and do they match up?