Okay, I have a bone to pick with H. Beam Piper. Writing a police procedural is hard. Writing a multiverse time-travel procedural is harder. Writing one that doesn't feel like a stack overflow exception in your brain? Apparently impossible here.
I picked this up because I needed a palate cleanser after a 40-hour fantasy epic. That epic was Conjuring of Light: A Novel, which left me needing something with fewer magical factions to track. At just over four hours, Time Crime looked like a quick ticket closing—something I could knock out in two round-trip commutes. But listening to this while dodging tourists on the Caltrain was a tactical error. The plot density is O(n²). You look away for one second to scan your badge, and suddenly we're in a different probability line dealing with an entirely new set of laws.
The premise is solid, though. The Paratime Police monitor different timelines to keep the secret of time travel safe. It's basically DevOps for history—patching leaks and ensuring the production environment (our timeline) doesn't crash because someone messed with the staging environment (the past). But the execution? Spaghetti code. The narrative jumps around, and the "crime" aspect often gets buried under the weight of the world-building mechanics. I found myself rewinding three times just to figure out which faction was betraying whom.
Mark Nelson: The Times New Roman of Narrators
If you've ever trawled through LibriVox for free classics or grabbed the budget versions on Audible, you know Mark. Clear, functional, zero frills. He doesn't do the whole "voice acting" thing where he tries to sound like a gruff space cop or a weeping victim. He just reads the text. Honestly? It helps here. With a plot this convoluted, I didn't need a narrator doing emotional gymnastics. I just needed the data stream delivered clearly.
Legacy Code Warning
This is vintage sci-fi (1955). The social norms in some of these timelines—slavery, casual violence—are presented with a detachment that feels too clinical for modern sensibilities. It's a feature of the "Paratime" setting (different histories, different morals), but it can be jarring. Like finding a hardcoded credential in a config file from the 90s—it belongs to a different era of engineering, and you just have to work around it.
Who Should Queue This Up (And Who Should Skip)
If you're a vintage sci-fi completist or love multiverse mechanics, this is worth the four hours. Skip it if you need to multitask—you'll lose the thread. It's a decent background hum for coding if you don't care about the details, but if you actually want to solve the mystery, you need to allocate some RAM to it.
Ticket Closed
Not merging this into my favorites branch.
