Let’s talk about DAGGERMOUTH

It’s possible that you haven’t heard about this book yet, so let me set the stage here: H.M. Wolfe’s Daggermouth is a dystopian romance that blew up as an indie title before getting a seven-figure traditional publishing deal, and it was just recently released in a pretty new physical hardcover. It has also been publicly accused of being written by AI.

(A quick side note: If you aren’t an Atlantic subscriber, you won’t be able to read the article at that link. Ironically, perhaps, there is at least one other website that has taken the entire article, stripped the author’s name off of it, and reposted it, with only an “originally published at the Atlantic” link at the bottom to indicate that they didn’t produce it. I’m not going to link to that article. You are welcome to find it, if you want.)

Under ordinary circumstances, I don’t think I’d have picked this book up in the first place. I’ve read my share of romance novels/romantasies in the last couple of years but I’m growing tired of it as a genre, and what the kids call “spice” is starting to slowly slide toward being a reason not to pick up a book. But a good friend who has become The Person I Talk About Books To told me she’d read it and recommended it, and then told me about the AI controversy, which at the time I hadn’t heard about. She thought the accusation was ridiculous, having read the book, and pointed out that of course the author everyone was tossing accusations at was a young Black woman.(*)

For what it’s worth, Wolfe’s publisher, who gave her a whole lot of money, is standing behind her on this, and since AI-written text can’t be copyrighted, you’d think they’d have a significant interest in making sure she actually wrote the damn thing.

The book is on Kindle Unlimited, as it turns out. So I didn’t even have to pay for it. Fuck it, I thought, and downloaded it.

If this book was written by AI, we are all in really fucking big trouble, folks. Human-generated culture is dead if AI wrote this book.

That sounds like a strong recommendation. It’s not. Not quite. Daggermouth has a problem that for some reason seems very common to the indie-book-to-tradpub-success pipeline: Wolfe constantly either uses words that are just slightly not the right word or describes situations that sound good at first and don’t make sense upon second looks. The type of thing that sounds like nitpicking if you only provide one example, and I don’t plan to eviscerate the book at the moment, so let me nitpick: there is a bit early on where a character is drinking from a glass, and his many rings “clink” against the glass.

The glass in question is a wine glass– stemware, in other words– and if you’re holding stemware in such a fashion that your rings are clinking on it, you’re holding it wrong. At one point– hell, this might be the same conversation, I don’t remember– a character is sitting behind an executive-style desk having a conversation with a second character. He stands up and “in four long strides” (Wolfe is terribly fond of counting her characters’ strides) he walks to the other character to get all up in his space.

The problem is that this description both 1) forgets that he was sitting behind a desk and 2) puts the other character really far away from that desk. Seriously, take four “long strides” right now. Is that normal conversational distance?

The writing, in other words, in a mechanical and a craft sense, is mediocre. I’ve read a lot worse, mind you. But it’s definitely not good. And again, this is a weird indie-to-tradpub problem; I had the exact same issue with Ryan Cahill’s books, and I can think of three or four other authors I’ve had the same complaints about who I’m not going to bother to call out by name right now.(**)

The story hits its stride at about the 100-page mark and is off to the fucking races after that, and never lets up or slows down for the last 80% of the book. This is a good story, poorly written. And there’s enough genuinely good stuff in there– particularly the ending, which caught both me and my friend completely by surprise. There are bits that are ridiculous, too; the worst offense was a bit where the fated lovers of the piece surprise eight soldiers in his apartment, kill all eight of them, and then decide to stay the night in the apartment rather than, say, realize their cover is completely blown and go literally anywhere else. They don’t even clear the bodies out until the next morning.

I didn’t have any damn idea how to rate this, and had I not spent the first 100 pages debating every third word choice and mapping out locations in my head, this might have been a five-star read, because it needed to get good enough that I stopped paying attention to the flaws in the writing. The book managed to shut down the persnickety editor part of my brain, and usually, once that guy is unleashed on your book, you’re done. But I got caught up enough in the story that I finished the book basically overnight, and after that first 20% I was genuinely expecting to have to DNF or force myself through the rest of it. I put it at four and a half on Storygraph (follow me!) and four on Goodreads.

I would not have thought for a single second that this text was AI-generated had I not been told that it was controversial. And, to return to the article for a moment, I’m not convinced of their methodology, at least based on what the article tells me– there are, for example, two entire sentences that appear word-for-word in other books that they looked at, but they leave out the kind of important detail of which book came out first. Maybe the fucking AI ate the sentences for this book and spit them out for the other one? Plus, I’m sorry, if you’re comparing this book to a book from someone who “wrote” 400 books last year, and the sequel to this one isn’t coming out for another year, guess what? I know which author I think is writing AI. Hell, I know which author I’m pretty sure doesn’t even exist. If this book comes out as a higher percentage chance of being AI than one of the other person’s 400 books, your methodology is crap and you should redo your study.

Is it possible? Sure. I’m not going to claim that my internal AI detector is top-tier or anything like that; in 8th grade the easiest way to see if a student cheated and had AI write a paper is to ask them to read it out loud, and as soon as they hit a word they can’t read, ask them what it means. It works every single fucking time. I generally don’t have to think about it a whole lot harder than that. But if it is? If a fucking genAI slop program wrote this book? It doesn’t have to be fucking Dostoyevsky for that to be a major fucking concern.

So, yeah. I’m pretty sure H.M. Wolfe’s Daggermouth is not written by AI. It has issues but ultimately I enjoyed reading it. I’m in for the sequel. And I am absolutely terrified about what is going to happen to human culture if I’m wrong.

(*) I Googled “H.M. Wolfe age,” and the fucking AI assistant told me she was born on October 28, 2025, and then helpfully added “Age: 0” afterwards.

(**) In fact, I’ll go so far as to say that the only indie-to-tradpub author who I haven’t had this problem with is Matt Dinniman, including his non-Dungeon Crawler Carl books.

#REVIEW: For Whom the Belle Tolls, by Jaysea Lynn

I am tired, and I stayed home sick today, meaning that when I take my son’s graduation day off at the end of the year I’m going to get docked for it. I still feel kind of gross and don’t have a ton of energy, but I want to recognize this book for its Dungeon Crawler Carl level of “has no right to be this good.”

So, with that in mind, a two-sentence review: For Whom the Belle Tolls is, somehow, a warm, witty and delightful book about dying young from cancer and then living and working in Hell, and also about self-acceptance and found family. And hot sex with demons with ribbed cocks.

So, yeah. Maybe that convinces you to read it and maybe it doesn’t. But I had a much better time with this one than I would ever have imagined possible.

#REVIEW: Voidwalker, by S.A. MacLean

It’s nice to be surprised once in a while, although maybe this book shouldn’t have been a surprise. I’ve been losing steam with my Illumicrate book box subscriptions; I cancelled my quarterly horror box after the third book in a row that I already had, and upon reading the description of the book that turned out to be S.A. MacLean’s Voidwalker, I very nearly skipped it. To be clear, the way Illumicrate works is their boxes are semi-blind; they’ll give you a description and a theme but you’ll have to do a bit of detective work if you want to know the actual title of the book before it shows up on your doorstep. And as Illumicrate’s main subscription line has been leaning far too hard into romantasy lately for my tastes, and the brief description of Voidwalker I had felt pretty bog-standard for the genre, I was disinclined to pay for it at first. Then I learned that the author was the same person who had written the excellent The Phoenix Keeper and decided to go ahead and let it ride.

(I suddenly find myself wondering how MacLean managed to get featured in two Illumicrate boxes in less than a year; her agent may be owed a raise.)

The premise still isn’t the most original thing on the planet, even considering that romantasy is a genre ruled by the trope and its biggest fans seem to literally want a checklist of Things What Are Supposed to Happen that they can go through as they’re reading. The main character is a smuggler; there’s a turf war happening between two members of a vaguely-fascistic race of antlered and tailed humanoids who each rule a chunk of the world and, oh, also eat people; the turf war turns into a revolution, and one of the daeyari (those are the monsters; I’m picturing Nightcrawler with antlers, but not blue) turns out to be really sexy.

And … well. There’s an interesting mix of fantasy and science fiction going on here, the main character rides a Void Horse, which is a horse that is actually a lizard, possibly my favorite kind of horse; and there’s lots of hints at a wider world that I assume will pay off in future sequels. I’m being snarky, but I didn’t really expect much from Phoenix Keeper and loved it; I expected even less from Voidwalker and enjoyed it enough to write about it and recommend it. MacLean has a great grasp of character that serves this book quite well; the relationships between MC Fionamara and the other secondary characters in the book are what keeps the book interesting, and while Antal, the daeyari, initially comes off as the same Tall Dark and Scary broody big-dicked male character that I’ve read about in a thousand Sarah J. Maas books and more recently in Alchemised, he’s got enough unexpected twists to his personality that I ended up liking him by the end. And while I hate the phrase “slow burn,” MacLean takes her time with the romance angle of things, so by the time Fi and Antal start boning it feels earned and not inevitable.

Honestly, my biggest gripe is a deeply nerdy one, which is that S.A. MacLean doesn’t know the difference between antlers and horns. Do you know the difference? I didn’t until recently, but now that I do I’m going to notice every time the words are misused in books for the rest of my life. There are other differences, but antlers are shed, and horns are permanent, and what the daeyari have are horns, even though they look like what you’re probably picturing when you hear the word “antler.” This would have been less of a big deal was it not an actual plot point that daeyari horns grow throughout their entire immortal-unless-killed lives and so you can get an idea of how old one is by the number of points and bends in the horns. So they are definitely horns and not antlers.

And now you know. Even if you weren’t interested in the book, hopefully the random factoid made reading the post worth it.

Two quick book reviews

I am in a horrendous mood, as the world is continuing to go to shit and nothing seems to be able to stop it or even slow it down, but there are still books out there, so I may as well talk about them. I don’t have the energy to make a full post about either of these so let’s just do a couple quick paragraphs each and call it a day.

Samantha Downing’s Too Old For This is a book about a serial killer forced out of retirement when a documentarian comes calling who wants to make a series about her. She was never actually brought to trial for her crimes, but changed her name and moved across the country anyway, and she’s less than interested in someone dragging all of that back into the light again.

She’s in her seventies, by the way.

This book ended up being lightweight and quick and more fun than it probably had any right to be, as Lottie Jones’ life keeps getting upended more and more as she attempts to cover for her crimes– both the old ones before she moved away and the new ones she has to keep committing as she keeps making mistakes that wouldn’t have mattered when she was killing people decades ago but are a bit of a problem in an era of near-constant surveillance by our own possessions. I can imagine a reader who is bothered by the fact that the protagonist is an unrepentant serial killer who we’re more or less expected to like, or at least enjoy reading about, but I’m not that reader and I had fun with this. I may look into more of Samantha Downing’s work if I ever allow myself to buy books again.

So, yeah, okay, I finished it, and it’s a thousand pages long and I have a full-time job and I still finished it in less than a week, and because of that I can’t really call it bad, but … if you weren’t going to buy this anyway, don’t let anyone talk you into it. SenLinYu is a perfectly cromulent author and no one would ever read this book and figure out on their own that it was originally brought into the world as Harry Potter fanfiction, but it’s way overhyped, at least from my perspective. I keep seeing videos about people who were in tears for the last two hundred pages or whatever, and I feel like these people need pets or significant others or something, because in the end it’s just a book and it’s being treated like a life-altering event online. I said in my first post that I was buying this out of FOMO, and I’ve got to stop doing that. I’m never going to be missing out if I don’t read a book TikTok likes.

(I deleted the app again today; we’ll see how long it lasts this time.)

Again, it’s not awful, but it’s definitely romantasy despite all the people insisting that no, it’s dark fantasy— I’m pretty sure “dark fantasy” is just romantasy with at least one rape scene to these people– and I’m tired of romantasy as a genre. It’ll look good on my shelf, and I didn’t hate it like I figured I would, but those are the best things I have to say about it.

Monthly Reads: March 2025

There are actually quite a few good choices for Book of the Month in here. The Reformatory? Oathbound? The Unworthy? Martyr!? The Bones Beneath My Skin? All are great choices, but I have to go with Galileo’s Daughter, by Dava Sobel. Review coming in the very near future. Lots of great books this month, though.

2024 in Books

Well, this is just ludicrous.

According to Goodreads, I read 185 books in 2024, comprising a grand total of 81,191 pages, or 221.83 pages per day. That’s assuming I finish Katherine Addison’s The Grief of Stones tonight, which I’m going to, because I have to start reading The Way of Kings tomorrow and I want to be halfway through that big bastard by the end of the day.

(It’s my dad’s birthday tomorrow and we will have family in town. That’s not gonna happen. I’m going to shoot for it regardless.)

With the exception of video games, I went full hermit this year, abandoning nearly all of my hobbies or media consumption except for reading. I have read for half an hour before going to bed at the end of the night for my entire life, and I think I stretched that to an hour this year, and I started reading with my morning coffee on Saturday and Sundays, meaning that my “morning coffee” would regularly last from whenever I got up to lunchtime. So yes, I read a lot faster than most people, but I also spend a whole damn lot of time with a book in my hand. Estimating an eleven-hour-a-week minimum would not be unreasonable at all, and I strongly suspect if I were to ever calculate any such thing it would be more than that.

My average book, by the way, was 439 pages. I actually did hit 200 books one year because I decided to; this year I genuinely wasn’t aiming at any particular number. I bet I could have done 250 if I had selected for shorter books, but I didn’t want to. Only 13 of those 185 books were nonfiction, which is shockingly low even knowing how hard I focused on series fiction this year– I’m shooting for 20% of my books next year being nonfiction, if you didn’t see the update to my reading goals in my previous post.

I read books by 124 authors this year, of which 86 were new to me, which is surprisingly high, especially once we get to how many books by each author I read. Without even looking, I’ll tell you right now that the author I read the most books by is Adrian Tchaikovsky, totaling …

… (looks at Goodreads list) …

Jesus, ten books. Other authors showing up more than once:

Six books: Pierce Brown

Five books: J.R.R. Tolkien, James Tynion IV

Four books: John Gwynne, TJ Klune

Three books: Thiago Abdalla, R.J. Barker, David Dalglish, J.S. Dewes, Robin Hobb, Jay Kristoff, Josh Malerman, Andrea Stewart, Richard Swan

Two books: Susan Abulhawa, Josiah Bancroft, Carissa Broadbent, Shannon Chakraborty, Rin Chupeco, Piper CJ, Rachel Gillig, John Keay, Judy Lin, Vaishnavi Patel, Ava Reid, Samantha Shannon, M.L. Wang

I thought about doing a gender breakdown, but it broke my brain. I have a bunch of authors with initials for first names, and a lot of the time I don’t immediately know those folks’ gender, and then you throw in the enbies and that’s more research than I really want to do. I’m about to show you the whole list anyway, so you can look for yourself if you want. :-). Of the 29 authors I read more than one book by, I’m certain 14 are men and 13 are women and yes, I know that doesn’t add up to 29 and I still might be wrong on a couple of them. For whatever that might be worth.

Pretty covers time? Pretty covers time. Click on ’em for gallery view:

#REVIEW: The Honey Witch, by Sydney J. Shields

This will be my second post in a row that is about a book but which I’m not calling a “review,” mostly because in the case of Sydney J. Shields’ The Honey Witch I’m not convinced I know how I feel about it yet. It is also the second book in a row where the thing about it that grabbed me was the title. I don’t know what a honey witch is, or at least I didn’t before I picked the book up, but for some reason I found the idea immediately intriguing– so intriguing, in fact, that I decided to overlook the fact that nearly everything else about it indicated that it was likely to be something I wasn’t necessarily going to enjoy. I mean, take a look at that pull quote. Those of you who have been here a while– have you ever heard me recommend a book with the phrase “sweet feast”? “Tender longing”? Okay, I’ve been reading a fair amount of romantasy lately, and I’m pretty sure if I went through my books in the last couple of years and counted up the ones with gay relationships in them versus the ones that were primarily hetero, the gay stack would be quite a bit taller. But everything about this just kinda feels like Not Me. I mean, this is the blurb:

The Honey Witch of Innisfree can never find true love. That is her curse to bear. But when a young woman who doesn’t believe in magic arrives on her island, sparks fly in this deliciously sweet debut novel of magic, hope, and love overcoming all.

(And see that “deliciously sweet” bit there again? All the pull quotes have honey- or tea-related puns in them and they’re excruciating.). But yeah. Honey Witch. The concept sold the book. Fuck it, I got it on sale for nine bucks. Who cares about nine bucks? I don’t care about nine bucks.

The first 80% was, indeed, sweet and whimsical and I might be starting to overuse this word lately but delightful and also, I dare say, cozy, another word that is maybe a sign of Not for Me sometimes. And it’s a fast read; 340 pages and I was reading about a hundred pages an hour while going through it.

And then after that first 80%, it gets really dark going into the ending, and I don’t want to spoil anything but I either loved this book or the ending ruined it, and as I’m sitting here I honestly can’t tell you which it is yet. I five-starred this and even put it on my shortlist for the end of the year, and it’s either going to end up at, like, number nine or something or it’s going to be a book that I quietly pull off the list in October. And it’s really going to depend on whether the first part of the book sticks with me more than the ending.

(At this point, I’m changing the title to my standard “Review” template, because screw it, this is a review. “I loved it up until the ending and I’m not sure about the ending” is a review. #myblogmyrules)

(And it occurs to me that, while this feels pretty standalone and as far as I know is not intended to be part of a series, but if a sequel were to come out, I’d pick it up, mostly because I like the characters so much. That, in and of itself, may seal the “review” part of the review.)

#REVIEW: Silver Under Nightfall, by Rin Chupeco

Yes, that’s right, three book reviews in three days, although this one is going to be shorter. Rin Chupeco is kind of a known quantity around here; this is the … sixth? of their books that I’ve read, and I’ve enjoyed all of them and at least one or two have made my end-of-year list. And, honestly, Silver Under Nightfall sat on my unread shelf for long enough that by the time I picked it up to read it I’d forgotten what the hell it was about.

And, honestly, I may never have known what it was about– it’s possible that I just ordered the damn thing on reflex because of 1) that cover (my god, that cover) and 2) Rin Chupeco. Again, known quantity. I buy Rin Chupeco books. It’s a thing I do.

It’s, uh, about vampires? And a bisexual vampire hunter who falls in love with both members of an engaged outwardly-cishet vampire couple? And there is so, so much sex that I promise you is nowhere to be found in the Bible, and that’s three super queer books in a row now. And I’m sorry, but “vampire hunter who falls in love with some vampires” should absolutely have led to me putting this book down, never looking at it again, and quietly looking down on anyone who said good things about it. I’m tired of vampires. I’m tired of vampire books. I’m definitely tired of vampire books where the vampires are irresistible and fuck everything. At least there are no werewolves, I suppose? Yet?

Finished the fucker in a day. Reflected on just how different Chupeco’s writing style is in this book compared to everything else they’ve written. Looked up the sequel. Got mad that the sequel wasn’t available in paperback yet, since my copy of Silver is in paperback. Spent ninety fucking dollars on the absolutely fucking breathtaking Illumicrate editions, which will probably take so long to get here that the paperback will be out by then anyway.

I’m mad at myself. Go read it.