Disappearance at Devil’s Rock, by Paul Tremblay:
Late one summer night, Elizabeth Sanderson receives the devastating news that every mother fears: her thirteen-year-old son, Tommy, has vanished without a trace in the woods of a local park.
The search isn’t yielding any answers, and Elizabeth and her young daughter, Kate, struggle to comprehend Tommy’s disappearance. Feeling helpless and alone, their sorrow is compounded by anger and frustration: the local and state police have uncovered no leads. Josh and Luis, the friends who were the last to see Tommy before he vanished, may not be telling the whole truth about that night in Borderland State Park, when they were supposedly hanging out a landmark the local teens have renamed Devil’s Rock.
Living in an all-too-real nightmare, riddled with worry, pain, and guilt, Elizabeth is wholly unprepared for the strange series of events that follow. She believes a ghostly shadow of Tommy materializes in her bedroom, while Kate and other local residents claim to see a shadow peering through their windows in the dead of night. Then, random pages torn from Tommy’s journal begin to mysteriously appear—entries that reveal an introverted teenager obsessed with the phantasmagoric; the loss of his father, killed in a drunk-driving accident a decade earlier; a folktale involving the devil and the woods of Borderland; and a horrific incident that Tommy believed connects them.
As the search grows more desperate, and the implications of what happened become more haunting and sinister, no one is prepared for the shocking truth about that night and Tommy’s disappearance at Devil’s Rock.
I have a hard time writing about books I really enjoyed, because I usually find myself reduced to wanting to say stuff like, “Read this already, okay?” and “Oh, wow” and “This was good. Really good. I mean it. This was good.”
Which is not particularly helpful. And, since I really enjoyed Disappearance at Devil’s Rock and find myself wanting to say, Just pick this one up and read it! I’ve been trying hard to figure out exactly what I should write (other than “You really should read this”).
So to make it easier on both me and you, I thought I’d do this in a list. That way, I can be incoherent and ramble on a bit, which is probably a lot more helpful than waving the book in the air and saying to everyone and anyone near enough to hear, “You need to read this!” (which is what I actually did say when I finished reading it).
- Disappearance at Devil’s Rock is billed as a horror, and yes, it is an eerie read, with lots of atmosphere and I think you’ll like it if you like horror … BUT this isn’t really a horror novel. At its heart, it’s about love and it’s about loss.
- So if you were thinking, this read isn’t for me, because I don’t like horror novels, I think you should still give this a try.
- It made me cry. I read this nearly a month ago, and even now, thinking back to that last scene, I can still remember why it made me cry.
- I read this in one long gulp. I literally couldn’t put it down, so it ended up being one of those books where you read the last words with a deep sigh and then realize, oh, crap, it’s 3 in the morning. I’m getting kind of old for this kind of thing, but at the same time, I’m very happy when I stumble across a book that keeps me reading deep into the night.
- Even though I couldn’t put the book down, this wasn’t a purely plot-driven novel, the kind that keeps you madly flipping the pages quickly, sort-of-kind-of taking in the words because really, you’re just hell-bent on getting to the end and finding out WHAT HAPPENED. Sure, there was plot, a good one at that, but for me, it was the characters that really made this book work.
- I liked the way the narrative went back and forth between the present and the past. It worked well. And I was never confused about when in time I was. Always a really good thing.
- I think it could have used a better title. Disappearance at Devil’s Rock doesn’t really work for me. Actually, it makes me think of the Hardy Boys, so maybe it would work for me if I’m feeling like reading the Hardy Boys. Which I used to do all the time, back when I was 13. But not so much now. (Don’t ask me what would be a good title, though, because I’m not good at stuff like that.)
- I really enjoyed this book.
So a huge thanks to TLC Book Tours for sending me a review copy. And of course a huge thanks to Paul Tremblay for penning this one. And did I mention, you should read this already, okay?
What it’s about:
Traveler, Cleric, Witch.
The villagers in the sleepy hamlet of Lychford are divided. A supermarket wants to build a major branch on their border. Some welcome the employment opportunities, while some object to the modernization of the local environment.
Judith Mawson (local crank) knows the truth — that Lychford lies on the boundary between two worlds, and that the destruction of the border will open wide the gateways to malevolent beings beyond imagination.
But if she is to have her voice heard, she’s going to need the assistance of some unlikely allies…
I picked up Paul Cornell’s Witches of Lychford after I read an excerpt of it on the Tor website (actually, I pre-ordered it right after reading it, as it wasn’t released yet — and I don’t normally place pre-orders, so the excerpt definitely grabbed me).
Then the ebook was released and sent to my Kindle … and like lots of other ebooks on my Kindle (and my Kobo), it ended up sitting on my Kindle for a while. But then I remembered it, and decided to pick up where I’d left off.
And I’m really glad I did. Even though this is a short book (it’s novella-length), Cornell has no problems building a believable world where magic is worked within the nicks and corners of the normal, magic-less every day.
Set in a small English village, the story pulls in the workings of local politics and is quite epic in scope. The rest of the story turned out to be just as good as the excerpt that had pulled me in, and when I finished, I found myself hoping Cornell would continue to set more stories in this world he’s created.
I had read Cornell’s London Falling a while back and enjoyed it, so reading the Witches of Lychford has reminded me how much I wanted to read his The Severed Streets, too.
So … I figured out “whodunnit”. Not until close to the end, but definitely before the big reveal.
It’s never nice when that happens. Still, this was an okay read. I particularly liked the parts of the narrative that took place in Botswana, and I enjoyed the mystery of how those parts fit in with the rest of the story. Unfortunately, once I found out exactly how those bits fit in, the rest of the puzzle pieces slipped into place–just a little bit too early.
Botswana? you say. But I thought Die Again was a Rizzoli and Isles mystery … And so it is. Here’s the synopsis:
When Boston homicide detective Jane Rizzoli and medical examiner Maura Isles are summoned to a crime scene, they find a killing worthy of the most ferocious beast—right down to the claw marks on the corpse. But only the most sinister human hands could have left renowned big-game hunter and taxidermist Leon Gott gruesomely displayed like the once-proud animals whose heads adorn his walls. Did Gott unwittingly awaken a predator more dangerous than any he’s ever hunted?
Maura fears that this isn’t the killer’s first slaughter, and that it won’t be the last. After linking the crime to a series of unsolved homicides in wilderness areas across the country, she wonders if the answers might actually be found in a remote corner of Africa.
Six years earlier, a group of tourists on safari fell prey to a killer in their midst. Marooned deep in the bush of Botswana, with no means of communication and nothing but a rifle-toting guide for protection, the terrified tourists desperately hoped for rescue before their worst instincts—or the wild animals prowling in the shadows—could tear them apart. But the deadliest predator was already among them, and within a week, he walked away with the blood of all but one of them on his hands.
Now this killer has chosen Boston as his new hunting ground, and Rizzoli and Isles must find a way to lure him out of the shadows and into a cage. Even if it means dangling the bait no hunter can resist: the one victim who got away.
So yes, the Botswana parts were good. Figuring it out early? Not so good. Still, it was nice to meet with Rizzoli and Isles again.
But I have to say, I’ve not been all that interested in the story arcs of a number of continuing series characters for a while now, this one included. I don’t mind the conflict going on at Rizzoli’s parents’ house (although someone really really needs to sit Angela down and talk some sense into her) but the whole thing with Isles and her sociopathic mother? It’s like, the priest thing didn’t work out (both literally and also as the continuing story arc) so we have to have something just as dramatic going on. We share DNA so we have a bond … I mean, really. Isles is supposed to be a scientist.
And while I’m not one to rip covers apart, and I love the woman’s eyes in the cover of the hardcover version (which is the version I read), I really don’t get the connection between that cover and the story. I think the paperback cover provides a much better connection to the story:
If you’ve read the book, you’ll know what I mean.
If you’re a Rizzoli and Isles fan, you’ll probably enjoy this one.
Why yes! I am determined to keep my Read List up-to-date (once this post publishes, I’ll be two for two – yay!).
So I just finished Fiction Unboxed by Sean Platt and Johnny B. Truant. I’d missed all the hoopla around the Kickstarter that began this project a couple of years ago, so I’m glad I discovered it the other day when I was bored and clicking around Amazon.
As I always do when I’m deciding whether to buy a book, after reading a handful of the five and four star reviews, I then read all the three, two and one star reviews. I find that these lower-starred reviews often help me to gauge whether a book is a right fit for me. If I don’t agree with what these ” this book was meh” reviewers are saying, or if they point out the reasons why the book isn’t for them and these reasons don’t affect me (or, as is sometimes the case, these reasons actually make me want to read the book), I often will end up getting the book.
(So to all you authors out there despairing about mediocre or downright bad reviews, take heart! There are readers like me who actually find these kinds of reviews helpful in making the “purchase” (rather than the “don’t purchase”) decision.)
After reading the “this didn’t work for me” reviews, I decided to take a shot with this one, because:
- I don’t listen to the authors’ Self-Publishing Podcast;
- I didn’t know anything about their Kickstarter for the Fiction Unboxed project; and
- I haven’t read their other writing book, Write, Publish, Repeat.
In the meh reviews, this sounded like the main problem–that if you’ve done all of these things, there’s nothing fresh in Fiction Unboxed for you (although many of the five star reviewers had done all these things, and still really liked the book).
Luckily, that wasn’t me. So I plunged in. And i’m glad I did.
What I liked about this book is how Truant takes everything that happened during the course of the 30 days it took for them to write, produce and publish The Dream Engine, plus all the Kickstarter days preceding it, and puts it into a narrative first-person tale that’s engrossing enough to keep you reading. I mean, seriously, you’re reading about two authors writing a book–that’s something that could get quite boring.
As they indicate at the beginning of the book, Fiction Unboxed is all about their process, and it’s a very intriguing process. They use story beats rather than a set outline, and I was fascinated by how the story beats enabled them to continue to write organically, with all the spontaneous surprises that entails, while at the same time providing them with a series of guideposts so they always knew in what direction they were headed.
My problem with all of my fiction WIPs has always been finishing the projects. I write by the seat of my pants, and often find myself backed into a corner at around 50,000-60,000 words. I’ve tried to outline projects several times before, and it’s never worked for me. There’s something about the word “outline” that makes me feel confined within the plot points I’ve put down, and I find myself just plugging away at my writing, bored stiff–and trust me, this shows in the resulting work.
But I also know that when I sit down to write and I know where my scene needs to end up, the writing is almost always fun and effortless. I just haven’t done this that often, so I can’t say for certain I still get those delightful surprises which, for me, are one of the main reasons I like to write–I want to discover the story as I go.
So I think I’ve discovered a process that I can tweak to my needs. For that alone, Fiction Unboxed was worth the price.
But it’s also a good look behind the scenes at how a couple of full-time fiction writers actually do their stuff. And judging from the excerpts in the finished book, writing at that speed doesn’t affect the quality of their writing – Truant seems to have a real knack for painting a scene and quite a lovely way with words. In fact, their production process seems quite rigorous, and while I haven’t read any of their novels yet, I suspect none of them are rife with the kind of grammatical errors I’ve been seeing in a lot of books lately (both self-published AND traditionally published, sadly).
Have you ever had those reading moments when you know you really need something light and funny? That’s how Summer at Castle Stone, by Lynn Marie Hulsman fell into my Read List. Something about the synopsis caught my eye, and next thing you know I had it on my ereader.
This summer, lose your heart in Ireland…
Shayla Sheridan’s a New York native born into big city luxury, but she’s never really fitted in with the “it” crowd. Desperate to make it as a writer and to finally step out from her famous father’s shadow, Shayla decides to take on a tricky assignment across the pond…
Swapping skyscrapers and heels for wellies and the heart of the Irish countryside, Shayla must go about ghost-writing a book of recipes by the notoriously reclusive and attractive head chef of Castle Stone, Tom O’Grady.
The only problem? He has no idea that she’s writing it.
Shayla Sheridan is eking out a living as a ghostwriter. She has her principles, though, and refuses to make use of her father’s literary fame to get her the writing stardom she craves. So she ends up undercover in Ireland, trying to get on the good side of dishy chef Tom O’Grady.
A ghostwriter! And there’s food and cooking! Not to mention the lushness that is Ireland! Some really good combinations here.
This was a fun, entertaining read. And when I got to the last third of the book, I couldn’t put it down—which I found interesting, because I usually associate “can’t put this down”-itis with thrillers and mysteries and such.
Shayla gets into a lot of scrapes, most of them of her own doing, but it didn’t hit the type of silliness that made me want to put the book down. And there was, of course, the classic moment of miscommunication thing (in this case, it was the “I should really tell him, I really should, oh, here’s a good moment to tell him, oh, but I really can’t now … yikes, it’s TOO LATE, the damage is done” thing—I trust this isn’t spoilerish because of course it’s the expected narrative arc in this type of plot, right?). But Lynn Marie Hulsman pulled it all off quite well, I thought.
So, yes, a fun read. One caveat, though: this book could have used a lot more editing than it got. And I mean A LOT more. Which was surprising, considering this one comes from HarperCollins, a major publisher. So if things like that take you majorly out of a book, this might not be a great read for you.