#REVIEW: Innamorata, by Ava Reid

Warning, maybe: reading this will make you reread Gormenghast.

Innamorata, and in case you’re wondering, no, I don’t know why the title is misspelled, is the fourth of Ava Reid’s books I’ve read. I actually own five of them; the fifth is the sequel to one of the other ones, bought at roughly the same time, and I think I read the first one and didn’t like it very much so I never got around to reading Book Two. Typically, once I own five of an author’s books, I’ve graduated to big fan of that author, or at least fan, and Reid, frustratingly, still hasn’t quite written a book that completely hit for me. And to be honest, I only bought this one because there was a ton of stupid BookTok drama and backlash against it that I’m not going to get into, and it pissed me off so I bought the book, striking back with my hard-earned money against the opinions of people I will never meet who similarly do not know I exist or that I bought this book to spite them and their unreasonable ideas.

Anyway.

Have you read Mervyn Peake’s Gormenghast books? If you have, knowing that Ava Reid begins this book with a quote from Gormenghast and that the castle that the main character lives in at the start of the book is called Castle Peake is probably enough to get you to pick this up. If you have not read any of Mervyn Peake’s Gormenghast books, you should go read them, then come back to this post.

The book begins with a funeral, the funeral for an old woman known as the Mistress of Teeth, and her funeral is attended by representatives for the Master of Blood, the Master of Eyes, the Master of Lungs, the Master of Bones, and the Master of Flesh, and the first several Masters take their parts from the corpse before the Master of Flesh stomps the flaccid, shredded sack of meat that remains into the mud, thus ensuring that the Mistress cannot rise from the dead. The former Mistress of Teeth’s teeth are made into a necklace for the new Mistress of Teeth, and I’m given to understand that the necklace contains teeth from several previous holders of that title. The book ends– this is technically a spoiler, but I think I can get away with it– with something “stirring” in a murdered woman’s womb, a murdered woman who was very much not pregnant when she was killed.

This is Gothic body horror, a lot of it, and it is deeply fucked up, and here I allude to the controversy in that you should completely ignore the marketing text that tries real hard to pretend this is a romantasy, because it is very much not a fucking romantasy, although I will admit it has some elements of same, including some, well, fucking. If you read books for atmosphere and mood and language, and the notion of reading something that is very much like a modern take on Peake appeals to you, jump at it. If you read books for other reasons … maybe not. The book is 532 pages long; I put it down, somewhat unwillingly, with about 80 pages left last night, having read all of the rest of it during my road trip. I got home from work today and read those last 80 pages, and I kind of feel like at some point the actual plot collapsed under its own weight. There is some interesting character development throughout, but that character development is going to involve someone completely abandoning every personality trait and motivation and goal that she had at the beginning of the book, and some of that stuff sounded pretty interesting! Lady Agnes wanted to follow in her grandmother’s footsteps– that’s grandma getting stomped into the mud in the first few pages– and restore necromancy to the creepy-ass island she lives on. That’s automatically cool!

She decides not to, basically because she gets distracted, and you’re going to have to be okay with that if you’re going to have a good time with this. And that was hellishly disappointing, even if a lot of the other stuff that happens was, again, cool and atmospheric and creepy and another part of the controversy was about trigger warnings, and I’m just going to tell you a lot of fucked up shit happens and has already happened, and there is so, so, so much blood in this book, and some spectacularly poor parenting, and I eventually turned that into four stars, but the sequel is going to get read right after it comes out, even if I’m kind of hoping it digs itself out of a bit of a hole.

Let’s call that a cautious and conditional recommendation for Innamorata, and you should definitely read Mervyn Peake.

#REVIEW: Our Sister’s Keeper, by Jasmine Holmes

I feel like I haven’t started a review with “Man, look at that awesome cover” in a while, but look at that awesome cover.

I had planned to review an entirely different book tonight, and I have a couple of movies to talk about as well, and I can already tell I’m going to have to review the book I’m reading now, and tomorrow and Saturday already have the traditional first-and-last-of-the-month book posts planned, so expect a flurry of review talk around here for the next few days. I picked this up last night specifically because I thought I could finish it by the end of the month; I was once again taken by surprise by an Aardvark book, basically not putting it down other than for sleep until I finished it, and at just over 300 pages, it’s a quick read.

Did you see Get Out? You should have. I don’t appear to have reviewed it here, but it’s a great movie.

Imagine that Get Out was a book.

(If it was a book, tell me, because I didn’t know that and I want to read it.)

Imagine that Get Out was more about feminism than racism.

Now imagine that Get Out was about feminism and set in a fictional Black free town in Mississippi in 1927, just a few years after the massacres that destroyed the Black communities in Rosewood, Florida and Tulsa, Oklahoma.

And buckle the fuck in, because this one is a hell of a ride, with a fantastic twist toward the end– hell, a couple of them– and I don’t know what the hell is going on with July right now, because I’ve had too many DNFs and too many six-star reads for a single month. I’m not even gonna give you any details beyond the setting. Go in blind. Just trust me. And damn, somebody shove Jasmine Holmes a huge pile of money and make a movie out of this. Jordan Peele? You out there? This is your next project.

#REVIEW: There Is No Antimemetics Division, by QNTM

I liked this book so much, I’m willing to forgive the author for wanting me to call him QNTM. I don’t know why, but I have a weird visceral reaction to authors using their Internet handles on their books. It’s made even weirder when you remember that “Luther Siler” is a pen name. I don’t know a single thing about QNTM other than that he wrote this book (and, I guess, that he’s a he, judging from his author picture) but if he’s going to keep writing books this good I’ll call him whatever the hell he wants.

This is one of the most original books I’ve ever read. I can imagine China Miéville writing something like it, which is not to say that Miéville has written anything like it yet. I’m not sure who or what else to compare it to. This is going to be a fairly short review, first because I don’t want to indulge in any spoilers, and second because beyond describing the premise, I’m really not sure how the hell to talk about this book. So I’m going to give you the basics, and I’m already telling you you need to read this if you’ve ever enjoyed science fiction that was smarter than you were, and that is going to have to be enough.

The main character of the book is Marie Quinn, who is in charge of the Antimemetics Division of something called the Unknown Organization. Her division is responsible for tracking, categorizing and occasionally keeping captive entities and objects that have the property of erasing themselves from memory. That’s what an antimeme is; it’s something that you view or interact with or occasionally get messily killed by and the very moment you’re not interacting with it you forget it exists. Some can erase specific kinds of memories (the book is generally not funny, but one entity that feeds on the very specific memory of knowing how to ride a bike has a fe pages dedicated to it) and some have the capability of also erasing notes, videos and recordings that reference their existence as well.

So, given that, and given that the potential threat these types of entities pose to civilization should be immediately clear, let me ask you two questions:

  1. How do you fight against these things, if you forget they exist the moment you turn away from them?
  2. How the hell do you write a book about fighting against something like that?

This is a short book; at under 300 pages it can be read in a day easily, and somehow, despite the complexity of the premise, it’s impressively clearly written. You would think this would be a mess to read, and in a lesser author’s hands, it would be; I certainly couldn’t have written this book. I almost read it twice in a row, and there’s a very good chance I’m going to read it again before the month is up. It’s an incredible achievement, both as a story and as a piece of craft. I know I’ve been super positive in my reviews lately (and I have read some amazing books in 2026) but once again I need to tell you that you absolutely have to read this one. Go grab it, right now, before you forget.

#REVIEW: The Caretaker, by Marcus Kliewer

This is one of those books that you finish, put down, and then mutter “Fuuuuuck…” under your breath.

Marcus Kliewer has, I believe, written two books. I read his debut, We Used to Live Here, and reviewed it here. My review was a little on the mixed side; WUtLH features a really unreliable narrator, a literary trick I generally don’t get along with very well, and its genre is mindfuck. One thing that I’m noticing as I’m rereading the review, though, is that I finished the book in one sitting.

I also finished The Caretaker in one sitting, and I did not have “read an entire book cover to cover” on my to-do list for today. Now, granted, this isn’t a terribly long book, coming in under 300 pages and with a largish font on top of that, but I genuinely did not put it down once while I was reading it. This means that Marcus Kliewer has written two books, I have read them both, and I didn’t put either of them down while I was reading them.

That’s … really impressive.

The Caretaker is also a mindfuck, although not as intensely so as WUtLH. The main character, Macy Mullins, is a twenty-something and a bit of a fuck-up, with a doozy of an anxiety issue on top of that. She’s the parental figure for her younger sister Jenna, a seventeen-year-old with a penchant for casual shoplifting. Macy is broke and jobless, and the sisters are about to be evicted from their apartment when Macy happens to spot a want ad for a temporary caretaker position. She interviews and discovers that she’s being offered nine thousand dollars, a life-changing amount of money, for the simple task of three days of house-sitting. The house is old and isolated, buried deep in the wilderness off the coast of Oregon, but despite her sister’s reservations she jumps at it.

Oh, and there are some minor things you need to do while you’re house-sitting. No big deal. The former owner had some, uh, quirks, and maybe some OCD, and maybe a lot of OCD, and his wife promised him that as long as she lived in the house she’d keep up his little rituals that he thought literally kept the world safe. A promise is a promise, though, right? Here’s the list. Again, no big deal. Simple stuff.

You might not be surprised to learn that things don’t go well. Otherwise this isn’t that much of a book, right? Macy babysits the house and makes sure none of the lights turn on in the middle of the night. She makes a ton of money, buys a used car, and gets her and her sister back on track now that she can get to work. The end!

Nah.

Full disclosure: I got sucked directly into this book and it dragged me along at a breakneck pace until I was done with it, and it might be the kind of book I wake up tomorrow and find a dozen huge plot holes in. The three major book services I use for ratings– Amazon, Goodreads and Storygraph– all have it at under 4 stars, which isn’t alarming, necessarily, but it means the book isn’t exactly garnering universal acclaim. But oh, man, the ride it takes you on is great. It’s creepy as hell and the main character makes nothing but bad decisions from start to finish and if I could have found a way to cover my eyes and read the whole book through the cracks in my fingers I might have, except I haven’t found a way to turn pages or hold a book while I’m doing that. But I’m keeping a close eye on this Kliewer fellow from now on; I actually picked this one up from Aardvark without immediately realizing it was the We Used to Live Here guy. I will not be forgetting his name again.

Give it a read. Just make sure you have a few hours set aside before you do.

#REVIEW: Trad Wife, by Saratoga Schaefer

I’ve been suffering through a little bit of a book drought lately— of the seven books I’ve read in March, I’ve only ranked two of them above three stars, and if you’ve paid any attention to my Goodreads or Storygraph accounts (Follow me! I want friends!) you know that I tend to rate generously, as I don’t often buy books I don’t expect to like.

My wife was a little startled to see that I’d picked up Trad Wife, though, which probably doesn’t look like something I’d usually read, especially if you don’t happen to notice that clawed hand on the cover. I own this because of my Aardvark book box subscription; it’s pretty easy to get me to take a risk on a hardcover if it’s only $10, and the club in general has had a pretty good record for horror novels for me.

Because, yeah, this is a horror novel. It’s Rosemary’s Baby crossed with Nightbitch for the TikTok/Instagram generation, which was not a thing I ever expected to type. Main character Camille Deming is an aspiring Instagram influencer and “trad wife” person, meaning she stays at home and cooks and cleans and constantly posts pictures and videos of her perfect house and her perfect lifestyle. The problem is that she doesn’t have a baby, and she feels like her social media is never really going to take off (I feel you, sister) unless she manages to get herself knocked up. The problem is it keeps not happening, and her husband seems to be losing interest in her.

So obviously she’s gonna fuck the first demon who invades her dreams to promise her a child. I mean, really, who wouldn’t? And if the baby doesn’t turn out … quite like she expected, well. Do it for the ‘gram. Or something. I feel like young people at least used to say that.

I actually posted a review of this to GR/SG, and it read, in full, “Absolutely deranged. I loved it.”

A few hours later, this is probably going to be one of those books that declines a bit in my esteem with the passage of time, but its strength is that it’s a fast, propulsive read (only 300 pages) that you will probably finish far too quickly to think about it too much. Once you sit down and think about it— and, to be clear, this is something that I don’t recommendit’s gonna develop a couple of holes here and there, and a couple of things about the setting are going to feel like they were contrived specifically so that the plot would work. Camille and her husband have just moved to a new home in a new town, for example, away from family and friends. Camille has no one other than her husband and an infuriatingly persistent and nosy neighbor who she’d rather do without, and she kind of has to be isolated for the plot to work— if she even had one good girlfriend the book would not have been able to unfold the way it did.

The book doesn’t actually really address her lack of friends; I assume it’s because she’s decided to dedicate herself solely to her husband; you’re gonna have to roll with it if you want to have a good time. Similarly, if her husband was even vaguely interested in being a good husband or a good father— either! it doesn’t have to be both!— a whole lot would have gone very differently. You will be annoyed by things like this if things like this generally annoy you. Do you want to like your main characters? You may not like Camille very much. I’m not certain you’re supposed to; I’m not sure the author likes her very much. But Trad Wife succeeds at being a creepy page-turner for the few hours you’ll spend with it, and sometimes that’s enough. I needed something I could dive into and enjoy, and it filled that role nicely.

It’s cold outside so I’m reading

It’s cold as fuck outside and I’ve got an upset stomach, so I read all 700 pages of this today. I’m not sure that it’s a good book in an objective sort of sense but it was absolutely what I was looking for.

Now I have to read a Wheel of Time book, so I’m going to be miserable for a few days.

Two books with the same problem

Pretty covers though, right? At least they have that going for them.

There have been a couple of wins so far in January as far as my reading goes, but on the whole I feel like the misses have well outweighed the hits. And I’m writing this particular piece not to shit on these two books but because the way they didn’t work for me felt very similar: in both cases, I feel like the author never bothered to clearly define some kind of fundamental aspects about how the world of the books worked.

The Bookshop Below, as you might guess, is about a magical bookshop. The book is set in the real world, more or less, but there are these bookstores scattered around — it’s not clear exactly how many there are, but they feel a bit too important for the number of them to be limited to the few we hear about in the book. At any rate, the stores are sort of sentient, and so are the books in them, and they only allow the people they want to find and enter them, and a lot of the time when people buy books from the bookstore they’ll trade a personal memento or a tooth or a lock of hair or, in what feels like a bit of an escalation, a firstborn child for the book they walk out with. The main character is a high-end book thief who ends up owning one of these bookstores, and the story goes from there.

I am not someone who demands that magic be rigorously defined in the books I read. Brandon Sanderson is kind of the king of the meticulously crafted magic system, where he can end his books with charts and diagrams of the twelve different schools of magic that exist and how they interact and blah blah blah. Tolkien, on the other hand? Gandalf and Saruman and Radagast are wizards, and shut up is how their powers work. It’s difficult, reading LOTR, to say the words “Gandalf can’t do that.” His powers and his magic don’t work like that. Now, there is tons of lore out there and histories of Middle-Earth and all that, but at no point does Tolkien sit the reader down and explain how shit worked.

The thing, though? Tolkien knew how shit worked, he just didn’t explain it. You cannot make a reasonable argument that JRR Tolkien pantsed his way through LOTR even given the tonal shift between The Hobbit and the rest of the books. The man knew what he was doing, he just didn’t think you needed to know.

And the problem with The Bookshop Below is that I finished the book unconvinced that the author had really sat down and worked out exactly what was going on in her own book. And maybe this is me punishing the book for not being the book I wanted; I’ve certainly had moments like that before, but the books in this story are doing things like flooding the bookstore because they’re unhappy, and I feel like if you’re going to have a setup like that, maybe you devote a little more attention to your worldbuilding. There’s also this whole big thing where the magic of the bookstores and the books is powered by The River, which connects all the stores, and which at least some of the payments for the books are given to, but it’s not at all clear what the deal with The River is either, and I really felt like the book kind of ended up collapsing under its own weight by the end.

I read Alma Katsu’s Fiend today– it’s less than 300 pages in a pretty big font, so this was not a huge achievement– and it was deeply disappointing. The issue with Fiend is that all the characters are part of the same family, and the family runs this massive multinational corporation that has made all of them massively rich. There is a lot of talk about what is going to happen when the patriarch of the family (who is weirdly referred to by his first name throughout the book, including by his own children) dies, and who is going to inherit the company, and also who will become head of their “clan”, and I guess those two people don’t have to be the same person, blah blah blah. It’s treated as a given that the company is extraordinarily dirty, and there’s lots of talk about whether this son or that daughter is tough enough to run the company, or whether they should try to change how things have always been done; you’ve seen The Godfather, you get the idea.

I don’t think Alma Katsu had any idea at all what the Berisha Corporation actually does. The synopsis calls it an “import-export” company, but that’s immensely vague, and it’s not clear at any point what the company is actually for. There is talk of sweatshops and exploitation and there’s a Whistleblower at one point, but the whole thing is very these people are bad, and this company is bad, just trust me, and … it doesn’t take much for me to accept that a multinational corporation is evil! I’m all in on the “capitalism bad” train! But give me something here. Even the scenes where these people are at work makes it really clear that the author never bothered to think through what anyone’s actual job was, and interestingly this book also seems to exist in a world without email. People have cell phones and there’s a stray mention or two of AI so it’s not like it’s set in the past; it’s just a big weird blind spot.

Blech. The world’s descent into hell is accelerating on a daily basis so far in 2026; I’d appreciate it if I could at least have something good to read.

#REVIEW: The Place Where They Buried Your Heart, by Christina Henry

My Aardvark book box subscription scores again; the books from this service have consistently surprised me with their quality, especially the horror novels, which have produced some of my favorite books of the year– books that I’d never have come across were it not for the club.

I need to get something out of the way first, though. This is a haunted house book. It’s a pretty damn effective haunted house book. You can really stop reading here if you want! You probably already know if you like good haunted house books, and if you are that guy, go grab this.

That said: the verb that keeps getting used throughout this book about what the house does to people is eats. The house eats people. The main character is Jessie Campanelli, fourteen years old at the start of the book (and living in a neighborhood near where I lived in Chicago, and in high school in 1994, which was the year I graduated, so this book hits home in a few places) and sick at home in bed, when she dares her annoying little brother to get a couple of his friends and go spend half an hour in the creepy old house down the road.

One of his friends loses an arm. Paulie is never seen again. The house ate him. And it’s immensely creepy and atmospheric in the book, but God help me, every time I saw a reference to the house eating someone, I was reminded of this:

(Forgive me, please, Christina Henry; your book is way way better than Death Bed: The Bed that Eats, which Oswalt gets the name of wrong every time he mentions it, but I couldn’t get past the eating.)

Jessie, who is an adult with an elementary-aged child by the end of the book, spends her life living in the house she grew up in, and Paulie’s death reverberates throughout the book, leaving scars that eventually rob her of her entire family and bring her one of her own. The book does a great job of capturing the kind of working-class, multi-generational families that Chicago’s neighborhoods are known for, and the relationships, bad or good, between Jessie and the rest of the characters in the book are a definite highlight. Jessie herself is kind of a mess, but she’s earned it, and her determination to better herself and keep her son safe is kind of inspiring.

I read this book in about four hours, a hundred pages before bed and the rest this morning before I was able to do anything else. It’s hard to put down, and the pacing is masterful. It’s creepy as hell throughout, and if anything I could have gone for another fifty pages or so to beef up the ending a bit. The book doesn’t quite fumble the finish, but the ending does feel a little bit rushed, which is my only real complaint.

I missed spooky season with this one– I should have read it in October– but you should check it out anyway.

(Okay, one thing: to be completely clear, there are gonna be some dying and/or threatened children in this book? Paulie isn’t the only one. If that’s not your bag, avoid. Consider this your trigger warning.)