A Pound of Flesh

I’ll admit, I went into *A Pound of Flesh* expecting another *‘soldiers vs. monsters’* slog, but Chesser subverts that trope from page one. The horror here isn’t just the *thing* lurking in the server farm—it’s the way the base’s hierarchy *enables* it, with officers more concerned about optics than the fact that their people are disappearing. The first act is a slow simmer of unease, all clipped military jargon and eerie silences, but once the dam breaks, it’s a full-on nightmare of quarantine zones and betrayal. Patton’s narration sells it: his delivery is so natural you’ll forget you’re listening to an audiobook, especially in the quieter scenes where a single hesitated syllable speaks volumes. The production team deserves credit too—subtle sound design (a flickering fluorescent hum, a distant scream cut off mid-broadcast) adds layers without ever feeling gimmicky. That said, this isn’t a flawless listen. The middle act drags slightly as Chesser indulges in *just* a bit too much tech-speak about satellite arrays and comms protocols—fascinating for gearheads, but I found my mind wandering during a 20-minute deep dive into signal encryption. And while the ending *lands*, it leans hard into ambiguity; if you need neat resolutions, you’ll leave frustrated. But those are quibbles. What sticks with me is the *atmosphere*: the way Chesser turns a mundane Air Force base into a pressure cooker of dread, where the real terror isn’t the supernatural element (though it’s genuinely creepy) but the banality of institutional failure. Patton’s reading elevates it further—his voice cracks with exhaustion during a 3 a.m. radio check, and you *feel* the weight of every unanswered call. For fans of *Annihilation*-style unease or *Black Hawk Down*’s procedural tension, this is a must-listen. Just maybe not before bed.