Category: Book Report

I say lots of glowing things about Ed McBain and how his books are immortal, how he uses series business lightly to keep things moving along but never at the expense of pacing or plot, or how his passages are lyrical. His 87th Precinct series stands as an example of how to do things right. This book, on the other hand, shows what happens when you do everything wrong.

This book is part of the Alex Delaware series. I’ve never read any of the others, so I’m lost and don’t give a weevil’s willie about the two and a half chapters of series business that starts the book as Alex breaks up, almost, with his long time girlfriend. In the middle of chapter 3, the “action” begins when someone mails a book of crime scene photos to Delaware and he shares them with his police detective compatriot, who recognizes one photo among many as a case he never solved before a sudden transfer pulled him off of it. That’s the motivation, the driving factor. To solve a 20 year old cold case, with no threats of immediate repeats or contemporary peril.

Meanwhile, Kellerman writes like the Michael Douglas character in Wonder Boys; there’s no detail too miniscule to leave out, no scene worth cutting. When the main characters go to New Mexico to interview someone, we get pages covering the drive from the airport, including getting lost and asking for directions; when the main characters need food, we get paragraphs about what they eat; when one character has nothing better to do, he washes his car, and we get a long paragraph about his car. In lieu of investigation, we get lots of time with the characters talking out what might have happened.

What happened? Ultimately, a bunch of rich kids killed a stoned girl, and their parents covered it up; 20 years later, the rich kids are now rich adults, and they’re still covering up. The psychologist of the detective’s dead partner sent the book, and he kept Delaware and the detective pointed in the right direction. Except when the Chief of Police was pointing them in the right direction or trying to obstruct them. Finally, we get an absurd climax 360 pages into the novel and some denouement with nothing really gained. Someone, not the protagonists of the novel, kill the bad guys, and they read about the deaths.

Geez, once I started finding flaws with the book, I didn’t want to put it down because I wanted to see how bad it could be. Changing POV from first (Delaware) to third (the detective) for apparently no reason? Got it! Actually, it might have been to provide insight into the characters, but I didn’t care enough about either of them to want to know more. And hey, who the heck was logging into their computer and downloading Google in 2002. Downloading Google. Lord, love a duck.

Yes, that bad.

Do not buy this book or read it. I will go as far as to not read another Alex Delaware novel. I’m so down on it, if a good series with riveting characters and good pacing came out written by Ed McBain’s son Joe Hunt but the series featured Chris Connecticut, I’d stay away just because all characters named after states have been tainted.

But hey, if you don’t want to take my word for it, here’s the link to buy it on Amazon.

Books mentioned in this review:

I am currently reading Ed McBain novels in heavy rotation (see also Fat Ollie’s Book and Kiss). I guess that’s only three so far this year, so I’m not making much of a dent in the oeuvre that spans fifty years.

This book from the late 1990s deals with an old woman killed in her apartment in an apparent burglary. The old woman, a formerly world-reknowned pianist, leaves $100,000 cash for her granddaughter, a lounge singer who has taken up with two Italian tough guys. Amidst this main plot, three high school seniors from a well-to-do prep school kill a hooker, her pimp, and a smalltime drug dealer. Fat Ollie Weeks handles this subplot.

Because the cops use the same informant in this book as in Fat Ollie’s Book, one can easily spot recycled material in the description of the informant. But I find the continued consistently good writing in the novels even though they span 50 years almost incredible. With each book, McBain varies the formula somewhat, alters his narrative slightly, but the characters and the crimes remain fresh and interesting. Some writers hit a certain level of success and just phone it in, but McBain never seemed to reach that level.

Which is why I can read these books over and over again.

Books mentioned in this review:

At one of the book fairs last year, I bought a number of Ross MacDonald books because, although I have read many of them twice, I don’t have many of them on my shelves.

As one might expect if one has read Geherin, MacDonald represents a transitional author in the hard-boiled detective school. He still has his hard knock chops in Lew Archer and the Chandleresque plots, but they have a touch more touchy-feely exploration of intrafamily conflict. This book is no exception as it begins with a disturbed young man kidnapping a wealthy oilman with the help of one of his underling’s innocent daughters and then delves into several decades-old murders amid a family tree that intertwines like a oak and poison sumac. I don’t even know if those two things intertwine frequently, but the book compells one to try his hand at simile.

This book and others that I’m revisiting on occasion remind me of why I wanted to be a writer, or at least what made me think I could get away with it. Somewhere, though, my voice varied from these pieces, but it’s good to come home once in a while.

Books mentioned in this review:

This book follows Winter Prey, so it’s obvious that I’m getting these books all out of order. Davenport’s in love with Winter, and they’ve moved in together. Meanwhile, an invisible man–that’s what the book flap calls him–is picking up women in art galleries and bookstores and is killing them.

It’s a fairly standard plot, well handled. However, the twist is reminiscent of Broken Prey, and frankly, I am probably reading these Davenport novels too quickly to remain absolutely glowing about each. But I like them and will hit the others on my shelf sometime in the near future.

Books mentioned in this review:

I bought this book at a book fair because I was binging. Probably the Carondolet YMCA last time. I mean, it’s an ex-library book, a movie tie-in, and I paid a buck for it. But you know what? It wasn’t bad.

The book relies on the narrative set in Terminator 3: Rise of the Machines. Instead of the past trying to change the future through action, which is the core of the movies, this book involves John Connor ca 2039 finding that one of the people on his team was a software developer programming on the Terminator project and that this software developer can communicate with his past self through his dreams. The developer, though, cannot remember anything beyond Judgement Day.

A good quick read, although I’d be interested to see how the series would turn if it didn’t rely so much on the cross-time thing, if it weren’t so important to have something happening in the present day. Apparently this author has another book based on Terminator 3 out, so that might be worth reading if it comes to my attention at one of the various book fairs coming up.

Books mentioned in this review:

Wow, who knew? I found my initial Alistair MacLean books back in the old Community Library, a volunteer and donation operation that operated out of a strip mall in High Ridge until it got its own tax levy and became the Northwest Jefferson County Library or whatever. It was more homey and plucky before it became a government-funded bureaucracy, something shared between those of us who enjoyed books before it became a burden to the taxpayers who didn’t. In the intervening years, my appreciation for Alistair MacLean has waned somewhat, too.

MacLean’s books about World War II and the early cold war period are enjoyable because they’re slightly exotic in tone and style as they are intricate in plot. MacLean, of course, was British, so his heroes are often British with their stiff upper lips mimicked in his slightly stuffy and distant prose. But more contemporary works (The Golden Gate and Floodgate come to mind) don’t work for me because they’re contemporary–in those decades I can somewhat remember.

This book deals with an American bomber carrying nukes that crashes into the Mediterranean. A British frigate investigates and finds a Greek shipping maganate who might have caused the sabotuage of the bomber so he could recover the nukes. The British naval officers on the frigate must outwit the mastermind and handle the armed and dangerous nuclear weapons at the same time.

250 pages, roughly, so it’s a quick read. Paragraph-based dialog makes it easy to skim, and the action does move along quickly, but the characters are pretty superficial and the book lacks the twists that characterize the best of MacLean’s plot-driven work.

But I bought it for a quarter, so it’s worth my time and money at that.

Books mentioned in this review:

This book, written only a couple of books before Fiddlers, focuses on a lesser character from the 87th Precinct novels: Fat Ollie Weeks. This is appropriate, that is a lesser character, as he works in the 88th Precinct, but he’s been known to participate in the boys’ criminal investigations from time to time, ah, yes. When a councilman is shot before a campaign event, Ollie is the first man up, but he involves Carella and Co. because the vic lived in the 87th. During the course of his initial crime scene inspection, Weeks discovers that his car has been broken into, and someone has made off with the case containing the book he’s very proud to have written.

The book lightly interweaves three plots: the investigation into the councilman’s death, Weeks’s investigation into the theft of his book, and the crook who stole his book’s interpretation of the book, entitled Report to the Commissioner. McBain even includes the text of the 36 page “book” written by Weeks, poorly, throughout the book. Remarkable that he (McBain) could write something bad enough to represent the amateur detective/First Grade’s work. I mean, I remember when I wrote that poorly, but I’m not sure I could do it now one cue (although perhaps I do it perpetually, which is why I lean away from fiction these days, thank you very much.

Also, as the book focuses on a bigoted character used mostly as comic relief throughout the other books, it gives McBain a chance to do some extra characterization to make Weeks’s character sympathetic.

I liked it. I bought it for a buck at a book fair. It’s worth more than that, but I’m cheap.

Books mentioned in this review:

This book precedes the last book I read (Broken Prey), so I put them in the wrong order when I lined them up on my bookshelf. As I’ve mentioned before, the events in Lucas Davenport’s life are background material, and the plots of the books are the important things within the novels.

This one differs from the rest, which differ from each other pleasingly. Davenport looks into the murder of a Russian sailor who formerly worked for the KGB. Was it a Russian mafia thing? A spy thing? Or could it be a hidden sleeper cell within the northern reaches of Minnesota?

Two things detracted from the book:

• A Russian security operative, Nadya, who is sent to oversee the investigation. No problem. Overreliance upon her saying, “What is this (insert American idiom)?” That can be a problem when overused. As a matter of fact, it was a problem.
• 2 typographical errors: an extra space before a comma and the misspelling of Del’s name as Dell. Come on, guys, you gotta try harder.

Also, I’ve nticed that Sandford’s novels have common pacing: 250-275 pages of chasing herrings and investigating followed by 50-75 pages of manic chase the real criminal action. As such, the climaxes often are forced and kinda rush past you. This book is no exception.

Books mentioned in this review:

This book represents one of Ed McBain’s last books, and it was published posthumously; the About the Author bit on the back flap is in the past tense, which startles me. Cotton Hawes gives his age as 34 in this book, too, which bothered me a little, too. For most of my life, he’s been older than I am, and suddenly I’m older than many of the detectives in the 87th Precinct. That’s the meta about this book. Also, let it be known that Ed McBain did not support the war in Iraq. I don’t have a vivid impression of whether his contemporaneous books from the Vietnam era were as down on it, or even his Korean War-era books were as down on it, but it’s noticeable in these last books (see also Hark!). Now, onto the story.

Someone is shooting seemingly-unrelated late middle-aged people very quickly, and the 87th Precinct has to find the perp before he can do another vic. Meanwhile, Kling’s broken up with the black doctor following Hark!, Cotton Hawes finds himself falling for an older woman, and Carella’s daughter (now 14 after 30 years) is hanging out with a bad seed. That’s all it takes to craft a good, readable book. Like Perry Mason, McBain’s books age well, so this will be a fine read decades from now.

I was a little disappointed with how long it took the police to figure out what was going on, but I guess McBain had a minimum length to meet.

Books mentioned in this review:

This is a three act play retelling an Arthurian legend (particularly the Lancelot and Guinevere thing). Published in 1927, this piece is now 80 years old, but it reads older than that. Set in the 10th century in England, the characters all speak Middle Englishesque, which is not historically accurate (Middle English started in the next century, and it certainly wasn’t spoken in 1927 on the east coast of America). As it’s not a direct retelling of the legend of Lancelot, the suspense kept me moving even through the stilted prose.

I read most of my Millay in early college, and my structured poetry of the time reflects her influence. Casting love poetry and whatnot into Middle English turns of phrase and relying upon iconic imagery of the period. I later moved a bit beyond it, but I still appreciate it enough that I enjoy Millay more than McKuen.

Books mentioned in this review:

This book contains not only the titular Perry Mason novel, but two other novellas featuring the sleuth. Theses stories are almost sixty years old, but Perry Mason stories are almost timeless. As a matter of fact, I used them as an example in the the March/April issue of The Writer’s Journal:

Are you writing a story with a short shelf life, or an allegory on human nature for all time? Regardless of what you intend to write, the details you include might inadvertently determine whether you’re an Erle Stanley Gardner; whose Perry Mason novels remain accessible and relevant decades after he wrote them, or a Justin Thyme, whose works connect with this year’s audience but will seem as dated as a Baltimore Orioles world championship in ten years….

How timeless are they? One of the suspects is an inventor:

“What does he invent?”
“Oh, lots of little gadgets. He’s made money out of some them.”
“What sorts of gadgets?”
“Well, right now he’s working on something in connection with infra-red rays. Before that, he worked out a device that opens and closes doors and does things like that.”
“What do you mean?”
“It works with invisible light, what I think they call black light. A beam runs across the room and as soon as some object corsses that beam it closes a circuit and does things–oh, for instance, like making electrical contacts so that the minute you walk into the house the elextric stove clicks on and starts cooking, the radio turns on, and lights come on, and … I don’t know, Mr. Mason, I think it’s just a gadget. So many of his things are scientifically fine, but impractical when you want to work on them.”

That’s not so far-fetched now, is it? We still don’t have those things commonly in homes, but they’re available and feasible. The language itself is more archaic than the plots or the characters, with all the talk of infra-red rays, black light, and lots of Gosh!

The stories are more whodunit than the most whodunit of the Lucas Davenport novels (recently reviewed here and here), but sometimes the plots have to be a bit contrived to get there. Within the brevity of these stories, it’s good.

A quick rundown of plots:

• “The Case of the Cautious Coquette”: A simple hit and run tort case turns dangerous when two people “come clean” as the hit and run driver, and a woman named as a witness has her first husband inconveniently die of a gunshot wound in her garage.
• “The Crimson Kiss”: A friend from Della’s hometown is going to be married, but is implicated in a murder of another Lothario.
• “The Crimson Swallow”: A wealthy client comes to Mason to hire him to protect his new wife from whatever made her flee. A jewelry theft muddies the waters, as does the death of a potential blackmailer.

One thing these novels seem to indicate is divorce is bad for you. Ex-husbands die a lot.

Books mentioned in this review:

As some of you know, I consider myself something of a Sweepstakes Bodhisattva. I’ve seen this book in different places since its inception, and when I saw it again on the table at one of last week’s book fairs, I knew I had to have it, if only to compare my knowledge to its.

This book was written in 1980 by the head of one of the independent judging organizations. He doesn’t hide it, but he does want to offer some insight into the fundamental honesty of the process as well as offering tips on how that sweepstakes contestants can take advantage of that process to have a slightly better shot at winning.

The book takes on sweepstakes, contests, lotteries, and bingo, with about half the book (it seemed) going to lotteries and bingo. There aren’t many ways to shade winning the latter, so there’s a bunch of history to pad the book out from pamphlet size.

Essentially, the tips are enter often and follow the rules. But if you’re interested in contests and sweepstakes, it’s worth a quick glance. It weighs in at 128 paperback pages, and I read the book in about an hour or so.

Books mentioned in this review:

My wife bought this book for Christmas last year (that is, Christmas 2005) because I’d liked Odd Thomas. As with the preceding book, the narrative voice of Thomas is exceedingly conversational, but this book at this time struck me as too much so. Odd Thomas, who sees silent dead people, gets a visit from the recently dead father of a friend. Someone has killed the father and has taken the son. Although early signs point to the first husband of the boy’s mother (and his birth father), it looks as though the boy is actually bait for the one person who can find him… Odd Thomas.

The book was a quick enough read and pretty engaging; however, some of the narrative voice seems like fluff, and I have to wonder whether this and its 2006 counterpart Brother Odd are merely one story stretched over two books; the ending of the book sure seems like a setup. That’s poor form.

Books mentioned in this review:

 

After reading Winter Prey, I flashed forward 12 years in Lucas Davenport’s future. He’s married to the woman he met in Winter Prey, and their children and she are in London, leaving Davenport a psuedobachelor. Instead of watching movies all night, he has to deal with a serial killer who appears to mock the MOs of three serial killers institionalized in a single Minnesota hospital. Early indicators point to a recently-released inmate, but that wouldn’t have made a 300 page novel, would it?

I figured out whodunit pretty early, but I rode along with Davenport and his team as they went down one blind alley after another. But it’s the journey, not the destination, for the most part. I’ve got a couple more prey books on the shelves, and I should get through them and get my complete list together since Prey books are plentiful at book fairs.

Books mentioned in this review:

All it took as one mention in a Kim du Toit post to help me determine what to read next. Heather, knowing I’ve spoken fondly of John Sandford before (here, here, here, here, and here), gave me a number of Sandford’s books for Christmas, so I cracked into another one. Simply because I saw the author’s name in a blog post. Sometimes, I pick books for the slightest of reasons.

This one dials the clock back to 1993, early in the series, before Lucas Davenport was where he is today both in his personal and professional life (in Mortal Prey, for example, he’s getting married to the woman he meets in this novel; in between, they went steady, broke up, and then came together again). However, Sandford’s books are written so the current plot is central and the ongoing story of Lucas Davenport and crew are secondary, much like Ed McBain’s 87th Precinct series. You can read them in any order and enjoy them independently.

Unlike the 87th Precinct, though, Davenport is an investigator with a team, so some of the action is executive in nature. Somehow, that works.

In this book, Davenport is at his cabin in Wisconsin when the local sheriff needs help with a brutal triple murder. It’s northern Wisconsin in winter, with heavy snowfall choking the roads a snowmobile and snow shoes in every garage. Man, it made me homesick. Before it’s done, there are a number of brutal killings of innocents but Davenport gets his person.

A good page turner, and I’ve already segued a decade and a half almost into Davenport’s future with my current reading, which you’ll read about in a couple days.

Also, like Mortal Prey, which took place in St. Louis, this book features talk and visits to Milwaukee, my home town, so I got to play spot-the-inaccuracies. Just one obvious gaffe.

Books mentioned in this review:

 

This 1959 booklet (third printing in 1961) discusses Hemingway’s work from a time when he was very contemporary and explores how Hemingway’s prototypical hero evolved from the 1920s to the 1950s as Hemingway’s life progressed. Weighing in at 40 pages total, it’s a nice short refresher on Papa and almost makes me want to read The Sun Also Rises again. But that’s already on my read shelves, and I have hundreds of unread books to read first.

Books mentioned in this review:

As many of you know, I am something of a Larry Niven fan (other reports: N Space, Rainbow Mars). I read Ringworld in high school, and I was awed. I like the stories that start out with a sense of wonder (see also Alan Dean Foster’s The Dig).

But this book is ultimately not that satisfying. Perhaps it’s been too long since I’ve read The Ringworld Throne, but that’s only fair, since it came out 16 years after the first sequel (The Ringworld Engineers, 1980). But this book isn’t the best of the lot. The first parts of the story are paced okay as more exploration and learning goes on, but the pacing of the end is too rapid and jump cut to really hold my interest. It’s a collage, nay, a kaleidoscope of scenes that end in a rapid denouement whose meaning is clear only when Louis Wu explains it and the magic of hastily conceived and underexplained science fix everything.

I can see why. The first part, Niven’s introduction, explains how classes and scientists have been working the Ringworld over for almost 40 years and have prompted him to write the sequels to explain the inaccuracies plausibly. But that drive to explain everything is what eventually diminishes the impact of the original and why he rushes through this book and takes care of the Ringworld in such a fashion as he’ll never have to write about it in Known Space again.

The book didn’t end as badly as the Rama series did, though, so it’s not dead to me.

Books mentioned in this review:

 

 

 

 

 

Written in 1995, this book takes a recent current event as a starting point and reimagines it humorously, much like Lucky You. In this case, it’s a devastating hurricane (unnamed) that ravages southern Florida and brings together a motley bunch of characters around a crime or two.

The subplots: A woman on her honeymoon begins to doubt the wisdom of her marriage when her husband decides to drive from Disney World to the Miami area so he can take video of the damage and heartbreak; a crazy ex-governor gone native kidnaps him; a pair of unlikely conspirators decide to pose as a homeowning couple to participate in an insurance scam; the son of a woman killed in the storm seeks revenge upon those who sold her a shoddy mobile home; and a crooked former home inspector makes sacrifices to a voodoo god and tries to get some of his grift on.

So there’s a crime involved, but it doesn’t really carry the story. Hiaasen jump cuts the subplots and the characters interact, but the inevitable climax on a key comes too early, the denouement runs a bit long, and the book lacks some of the rush that his others bring.

So it’s somewhere between Lucky You and Nature Girl (which I didn’t like so much). Still, it’s a readable and enjoyable book, just not one of Hiaasen’s best.

Books mentioned in this review:

I bought this book at St. Michael’s book fair earlier this year; between Great Tales of Mystery & Suspense, my reading pace for the year is shot.

This book runs 574 pages and comes from the pages of Reader’s Digest magazine from the first half of the last century. It collects murder mysteries, a couple of ghost stories, and a long piece on the Alger Hiss espionage (starring Congressman Richard Nixon as the hero, which explains why former Vice-President Nixon offered a blurb on the back).

Some of the stories overlap with The World’s Most Infamous Crimes and Criminals, but they’re told with a punchier (partially digested) style. Also, overall, this book was not as depressing as The World’s Most Infamous Crimes and Criminals as it didn’t have matter-of-fact accounts of genocide.

Worth the buck, except for the part where it made me spend a week or so reading it. Looks like I’ll be reporting on coloring books for the next couple of weeks so I can get my average up.

Books mentioned in this review: