One Night in Bridgeport is a legal thriller that follows Jack McGee, a law student who is sent to Bridgeport, California to deliver some papers concerning the purchase of some land by a large corporation. While there, he decides to have a one-night stand with a local woman, Lea Rogers. (Who, though McGee doesn’t realize it at the time, is the daughter of the property owner.)
The next morning, McGee wakes up feeling overwhelmed with guilt and regret over cheating on his fianceé and leaves without speaking to the still-sleeping Rogers. She wakes up in time to see McGee’s car pulling out of the parking lot, and immediately feels angered and hurt by his caddish behavior.
Later, she discovers that McGee is handling the purchase of her mother’s property, and her anger only increases further. In a conversation with her friend and local lawyer, Butkus Sweet, she mentions sleeping with McGee and Sweet decides that it must have been rape. After he pressures her to do so, Rogers presses charges against McGee.
From this point, things go from bad to worse for McGee, beginning with his initial decision to tell the investigators he has never met Rogers, and continuing through his trial, where many other questionable aspects of his past come to light.
The book has an almost Rashomon-like quality to it, in that we see things from different characters’ points-of-view. In addition to McGee, Paxson also shows the perspectives of Rogers, Sweet, and the Judge. (Personally, I found the Judge and McGee’s determined-but-overworked defense attorney, Tammy, to be the most sympathetic characters in the story.)
The plot is well-paced, and the final twist that resolves the story is both set up well enough that it doesn’t feel like it came out of nowhere, but hidden well enough that you don’t see it coming. I also enjoyed the descriptions of McGee’s walks in the snow. At one point, Paxson alludes to the eerie, muffled silence that accompanies a new snowfall–I loved that, because to me it’s one of the most interesting things about snow, and not enough writers make mention of it.
My only real problem with the book was how unlikable McGee is, but I suspect that this is a pretty realistic depiction of this kind of case. Some readers might be alienated by his personality, but if you’re the type who needs someone to root for to feel engaged with a story, be patient–in the second half of the book, the Judge emerges as a very well-written, sympathetic and interesting character.
It’s the sort of book that I think can be perceived very differently by different readers, so before you read my last bit of analysis, I recommend you read it yourself and make up your own mind. I’m not only going to spoil some plot points below, but also say some subjective stuff that could color your perception of the characters. So, now’s your chance to bail if you don’t want spoilers.
The Seneca Scourge is a medical thriller with science-fiction elements. It follows Dr. Sydney McKnight as she finds herself in the midst of a seemingly incurable influenza pandemic. Aiding the staff at her hospital is the mysterious Dr. Casper Jones. As the pandemic spreads, Dr. McKnight notices Dr. Jones behaving oddly.
As she investigates in between treating the ever-growing patient population, Dr. McKnight gradually uncovers the shocking truth about Dr. Jones.
That’s the spoiler-free synopsis. If you don’t want to know the plot twist, don’t read after the asterisks below. My spoiler-free review is that it is a very well-paced thriller that successfully combines fairly plausible depictions of medicine and viruses in the first half with science-fiction elements in the second half. If you like either medical thrillers or science-fiction (and especially if you like both) I recommend it highly.
Now, if you want to know more detail, with spoilers, read on.
I rarely read murder-mystery or thriller-type novels, especially not those without supernatural elements to them. Stories with lots of non-supernaturally-motivated murders rarely appeal to me. So Eating Bullwas a bit of an adventure–not the sort of book I would normally read.
“Eating Bull” is the cruel nickname given to the novel’s protagonist, Jeremy–an overweight teenager who becomes the primary plaintiff in a lawsuit against fast-food companies in Ohio. He is supported by his good-hearted but overworked mother, Connie and his nurse, Sue–a determined woman with a strong sense of social justice.
Arrayed against Jeremy, Connie and Sue are school bullies, unsympathetic co-workers, and even Jeremy’s own grandfather–an agoraphobic Army veteran. Sue faces the additional difficulty of her loving but extremely protective husband, who dislikes her risking her own safety by courting the wrath of public opinion.
In addition to all of this, a serial killer calling himself “Darwin” commits a series of grisly murders–all of them targeting overweight people, whom he deems “sheep”.
I won’t go through the plot in too much detail and risk ruining the appeal of watching it unfold. I will say that all these elements are combined very well–each chapter is told from the perspective of either Jeremy, Sue or Darwin, and all of them balance out and keep an extremely gripping pace. For the final fifty pages or so, I couldn’t put the book down, and the ending is very emotionally satisfying.
Jeremy is very sympathetic and likeable, and Sue is an admirable portrayal of a heroic woman who nonetheless has a flaw–she tends to value her concern for Justice over the more immediate concerns for herself or her loved ones. This is well-done, because such a character could have easily become cloyingly saintly, and Rubin does a good job of making her seem heroic and also still human.
The Darwin chapters are naturally quite disturbing, and a good example of why I don’t normally read this genre. Not that they are badly-written–rather, that they are so well-written as to make me feel slightly sick just reading them. The portrayal of the killer’s mental state is quite sharply-drawn–among other things, it’s one of the best depictions of Obsessive-Compulsive Disorder that I have ever read.
These chapters are definitely heavy on gore, and that was a little tough for me–which is kind of funny, given that my own books have a fair amount of carnage in them. The parts with violence against women were especially hard to take. But again, these are my own tastes, and I suspect fans of thrillers will be used to this sort of thing.
All in all, I came away extremely impressed by Eating Bull. In spite of the violence, I enjoyed the characters and the pacing. And Rubin also has a real talent for clever descriptions and almost Chandleresque turns of phrase. There were a few hiccups here and there, but overall it stacks up well against the few modern thrillers I’ve read. (Stephen King’s 11/22/63 and Dan Brown’s TheDa Vinci Code, in particular.)
I was taken aback by how much I enjoyed the book, since thrillers are normally not my cup of tea. It was something I pondered for a while as I was reading Eating Bull: “Why am I enjoying this so much? It’s not like me.”
And then it hit me: there’s another side to the book, apart from the engaging plot.
Eating Bull‘s main theme is the problem of obesity–Jeremy is obese, Sue wants to cure the societal causes of obesity, and Darwin wants to exterminate obese people. All the minor characters, in some way or other, comment on Jeremy’s condition–some positively, some negatively–but it’s the central theme of the book.
Now, some would just use that as a cheap “hook” or gimmick to tie everything together. But Eating Bull goes to some lengths to explore the causes of obesity.
For example, there are several scenes where Connie gets some fast-food for Jeremy to eat after she returns from work. She knows this isn’t optimal, and is apologetic to Jeremy’s caregivers when asked about it, but explains that it’s cheaper and faster to get bad food–and as a single mother working two jobs, this is no small consideration.
There are many other examples of this throughout the book, all aimed at showing the various factors that contribute to obesity. At times, it raises some serious issues regarding how food is marketed, reminding me of the non-fiction book Fast Food Nation.
It’s very difficult to write a social problem novel that doesn’t come across as preachy and heavy-handed–the author has to balance all the mundane facts (and sometimes even figures) needed to make the social point with a compelling dramatic narrative that is interesting to read. (In The Jungle, Sinclair seems to simply give up towards the end, leading to entire chapters that are just lectures and Q&A sessions on Marxist theory.)
For the most part, Eating Bull avoids this pitfall, keeping the action going at a brisk pace while exploring the larger social theme through minor incidents and at well-chosen intervals. When some detailed sociological point needs to be made, Rubin wisely has it said by Sue, for whom it seems logical and in-character.
This social aspect was really what set Eating Bull apart for me–it was something more than just an interesting page-turner. Whereas most thrillers are normally easy to forget once you have learned How It All Works Out, this one gives you a bit more to think about.
One word of warning: if you enjoy eating chips or similar snacks while reading, well… you probably won’t while reading this one. You may decide to opt for a salad instead, but then of course it’s harder to eat a salad while reading. And that’s to say nothing of the Darwin chapters, after which you may not want to eat anything at all…
Stephenson is a very versatile writer. Each story has a distinct tone to it that is appropriate for the genre of each. Personally, I liked the war story “The Red Fox” best–though that is only a personal preference matter. As Mr. Prescott can attest, I tend to prefer war stories to romance. All the characters are very well drawn and differentiated in each story.
“The Red Fox” has the most complex narrative structure of the three stories, and I think it is the most effective. It begins with a military commander arriving to tell the Emperor about a bold gamble he has made, then flashing back to recount the events that precipitated it, and then concluding with the emperor’s response. It is well paced and I liked the plot.
The final story “Alexiad” may not work as well if the reader is familiar with the historical figures involved; but I found it to be a nicely done story of the evolution of a personality. That said, the ending felt slightly rushed. It seemed like there was a lot of a build-up for a payoff that, while satisfying, could have been taken more slowly. Of the three, I think “Alexiad” has the most potential to be expanded into a longer tale.
The only quibble I have is one quite common in historical fiction: the clash of esoteric terms with modern ones. Since most of Stephenson’s characters speak in modern English, it is jarring to occasionally have ancient words like “Exkoubitores” interspersed. Obviously, this is a necessary conceit of the genre, and Stephenson was wise to avoid adding pages of parenthetical definitions, but even so it has the effect of taking the reader out of the action.
The other slight problem is occasionally plot developments are conveyed by telling, rather than showing. This is particularly an issue in the middle of the second and the beginning of the third story. It’s a problem every writer faces at some point, and it’s especially hard to overcome in historical fiction, but I felt that certain things that could have been explained in dialogue were instead simply told in omniscient narration.
However, these are minor issues, and the book is extremely enjoyable on the whole. It is very carefully edited, which is a plus–many self-published books suffer from sloppy proofreading. Not this one.
I suspect someone with a more thorough knowledge of Byzantium would get more out of the book than I did, (though it may also ruin some of the surprises) but from my layman’s perspective, it was very good indeed.