This is a post-apocalyptic zombie book. I should state up front: I’ve never really cared for the whole zombie genre. I saw Night of the Living Dead as a teenager and it didn’t seem remotely scary. I’ve played many video games with zombie-like enemies, but I never relish the levels that involve fighting hordes of the undead. They just seem gross to me, not scary.

“Okay, Berthold; then why did you read this book?”

Well, I’ll tell you. But, as usual, in my own time. First, let’s meet some of the characters.

As you might surmise, one of the major characters is named Zach. Zach is a former marine who lost his wife early in the outbreak of the zombie apocalypse. Shortly after that, he rescued a young girl named Abby from a zombie attack, and took her under his protection. Zach and Abby make a decent home for themselves in a cabin, but it soon comes under attack, forcing them to flee.

This leads to an episode that was rather tough for me. I don’t want to spoil it, even though it only occurs about a quarter of the way into the book, but it involved a trope that drives me nuts. Let’s just say it’s a hallmark of the post-apocalyptic zombie genre. Which, I guess, is probably one reason why I don’t read more post-apocalyptic zombie books. I don’t want to knock the book too much for this, since it may be a genre convention as much as anything.

Another reason I don’t read many post-apocalyptic zombie books is the intense violence. That’s not a criticism of the book, to be clear–I knew what I was letting myself in for by picking up a zombie apocalypse book–but some of the scenes were still pretty hard to take. I particularly don’t enjoy violence involving female characters, and there were some very brutal scenes of exactly that.

The first quarter of the book was tough going for me, but I stuck with it, and I’m glad I did, because I enjoyed what followed: first comes an extremely tense and well-paced episode at a military base, followed by Zach, Abby, and some new comrades they’ve met along the way discovering a town called “Little America,” which is seemingly a safe haven from the zombies and the gangs roving the wilderness.

Life is almost normal in Little America, and Zach and Abby find themselves living in near-peace. Abby starts going to school and making friends her own age, Zach makes a living as leader of the town militia. And both of them even find time for a little bit of romance–a boy from school for Abby, and for Zach, a woman named Amber, one of the people they met while trekking across the zombie-haunted wilds.

Up until Little America, His Name Was Zach is mostly a straightforward zombie story, but then there are three moments that stick out as unusual. 

The first is a scene where Zach sees a statue of George Washington and finds himself imagining a whole Revolutionary War battle going on around him. Some readers might find this passage a bit odd, but personally I loved it. First, because it’s offbeat and unexpected, which automatically makes it interesting, and second because I think it gives us a window into both Zach’s deep immersion in a timeless warrior ethos and his PTSD. It’s like it triggers a flashback to a war he wasn’t even in, but he feels a bond with those who fought in it all the same.

Actually, that’s something worth noting about this book: there’s a strange dissonance produced by the episodes of horrific violence–some of which is committed by Zach himself–and the serene, almost Andy Griffith-like wholesomeness of Little America, and Zach and Abby’s father-daughter relationship. It’s downright uncanny to conceive of a world that can contain sweet, beautiful things as well as disturbing, monstrous things. Yet, we know that the world–the actual, real-world, I mean–does in fact contain both, but our minds can’t really reconcile the two.

There have been books that I have abandoned because they are too relentlessly violent, too consistently bleak. Yet, in a strange way, unified bleakness is almost easier to think about than the jarring switch from soul-crushing horror to a world where things are, basically, all right. There were moments while reading His Name Was Zach that the letters “DNF” flashed across my mind, but it would always revert back to a more normal, almost pleasant tone–I say “almost” because the gnawing feeling of the horror lurking on the fringe would never quite go away.

This mirrors the personality of Zach himself. He describes it as a demon chained up within him, and when he is angered, that demon yanks at its chains and is capable of pushing him to terrifying extremes–but the rest of the time, he seems like any other normal guy, just trying to protect his loved ones and do his duty.

Speaking of which: eventually, Zach is sent outside of town on a mission, along with a group of the militia, in which they encounter one of the gangs, led by one of the most fascinating characters in the book–a drug-addled psychopath named Edmund, who is something of a cross between the Joker and Anton Chigurh.

And now, I’ll tell you why I read this book despite it being outside my reading comfort zone.

I’ve been very impressed by posts I’ve read on Martuneac’s blog. Like this one, where he argues that the reason Bilbo Baggins has such excellent luck in The Hobbit is because that’s how Tolkien saw life. Tolkien had survived World War I thanks to sheer luck, and so he had no problem having his characters survive due to the same.

I generally dislike plot contrivances that hinge on miraculous luck for the hero. But, Martuneac makes a strong case for them in that post. So much of life really is determined by chance, so why not have it be so in fiction as well? Fatalism born of seeing the random violence of war.

Edmund essentially embodies this concept. His encounter with Zach piles one strange coincidence on top of another. And I’ll admit, it’s the sort of thing I would complain about in fiction, but together with Martuneac’s reading of Tolkien, it takes on a nearly allegorical quality. It’s a statement about the bizarre, weird, freakish stuff that happens in life.

And that’s why I picked up this book: I’ve enjoyed reading the author’s blog, because of insights like this one. When I find a writing blog I like, it’s generally only a matter of time before I try one of the author’s books, even if they are outside my usual genres.

The third moment that stood out to me comes about three-quarters in, when the authorial tone briefly changes to directly address the reader. The entire story is in third-person, but only once does it actually turn into the voice of someone conscious that they are telling a story. The omniscient narrator tells us not only that this is a story, but, broadly, what’s going to happen next.

I found this interesting, because it’s a call-back to a much older, and currently unfashionable, form of storytelling. Readers may love or hate it. I wouldn’t say I loved it, but it was different, and I like that.

There is one more section after that which I want to discuss: a part where Zach is forced to make a very difficult choice, It’s the sort of thing that veterans of Role-Playing Games will recognize, where one has to make a snap decision and either way will be forced to sacrifice something.

The amount of “time” spent on this was a little excessive. By “time,” I mean the way the scene was “paused” to allow the reader to read Zach’s internal monologue thinking through the implications of each choice.

Now, of course, as authors it’s our prerogative to mess with time in our stories however we like. We can make years go by in a single sentence, or spend a whole chapter on one single minute of existence.

My problem with this scene was that the consequences were already quite clear without needing to have spelled them out. I was sufficiently invested in the characters that I knew how serious the problem was without being told. And it happens in the middle of an action sequence, so it felt a bit jarring.

Finally, the end of the book. Again, I’m trying not to spoil anything, so I’ll just say this: I guessed where it was going before it got there, but despite this, it still produced the effect the author was going for. Now, I am perhaps the most easily-manipulated reader in the world, so maybe that’s not saying that much. But, for what it’s worth, it worked on me even though I saw it coming.

This is the first book in a series, and the ending does a good job at simultaneously being a satisfying ending point while also setting up the next book. 

One technical note: the dialogue was at times a bit clunky–characters would say things that sounded more like speeches than spoken dialogue. I found myself wondering if the story could have been told with less dialogue, in keeping with the older style of omniscient storytelling that I alluded to above. (H.P. Lovecraft’s stories, for example, contain very little dialogue, often summarizing conversations instead of quoting them.) On the other hand, that might be just too weird for most modern readers.

And now, a word about zombies. 

I was actually pleased by how little the zombies featured in the story–they are mostly a “background menace,” used sparingly and for maximum effect. I liked this, but then since I am not a zombie fan, I would. People who just can’t get enough zombies may be disappointed. 

Also, for the record, they are the fast-moving, predatory zombies; not the the slow, shambling kind. They also have one curious trait I’ve not seen in other zombie stories, in that they are somewhat capable of responding to Pavlovian conditioning. 

I mention these things only because I know there are people out there who care deeply about the quality of their literary zombies, and connoisseurs will be upset if they find themselves reading a zombie book that features the wrong kind of walking corpses.

Wow, I really am going on, aren’t I? Normally when I write a post this long, it’s to complain about a Star Wars movie. But I have to say one more thing in closing, which is that His Name Was Zach isn’t really about the plot, or even the setting. This is a character-driven book, plain and simple, and it really all hinges on how the reader feels about Zach and Abby. The dynamic between them is what “makes” the story.

It’s probably not a book for everyone, in particular not the squeamish. Then again, it may be that there are no readers more squeamish than I am, and even I made it through. But if you can handle the violence, it’s worth a look, and Martuneac is a promising author. I’ll definitely be reading more of his work.