Run 538: The pulled muscle recovery run

Run 538
Average pace: 5:18/km
Location: Brunette Burnaby Lake (CCW)
Start: 11:30 am
Distance: 5.02 km
Time: 26:40
Weather: Mostly cloudy
Temp: 17ºC
Humidity: 57%
Wind: light
BPM: 166
Weight: 156.4 pounds
Total distance to date: 4187 km
Devices: Apple Watch, iPhone

I was originally planning to wait until Tuesday to resume my runs since pulling the muscle in my left upper leg last Friday but spontaneously decided today to go out for a 5K, since the aforementioned muscle hasn’t exhibited any sort of soreness or stiffness over the past few days.

And so I headed out after seven days off, back to Burnaby “yes, there really are bears here” Lake. My plan was to walk to the lake, do a 5K, then hitch a ride back on the SkyTrain from the Burnaby Lake station rather than face a 9K+ walk back home, which I felt might be pushing it only a week later.

I started out by making a trip to the loo, which seems to happen quite a bit now for some reason. I don’t mean going to the loo in general, just specifically when I get to the lake and my body seems to interpret that as “nature calls” (literally). After relieving myself I headed back over the dam and encountered a far-too-cheerful cyclist pulling a small wagon behind him. I secretly wished rabid geese on the bike but later found the same bike was being used to collect cones that had been placed as part of a Running Room event (the event was over by the time I got there). He was still riding too fast and was too dang cheerful, though.

A small section of the trail near the sports field was closed for repairs and a spray-painted line through the grass suggests they may actually be preparing to shore up Ol’ Floody, as I call this particular stretch. It would be nice if they fixed it to not flood, because when the trail floods and you detour onto the field you discover that the grass is actually kind of floating on a layer of mud and water that is really tricky to run on.

I did not see any bears this time, for which I am glad. I have nothing against bears, as long as they stay, you know, out of the city.

The run itself started at a steady pace and I felt fine. Conditions were actually pretty good–cloudy and temperatures in the high teens–and for the first three km it felt pretty much like any other run. Around the 3K mark I started feeling stiffness around the left knee, though oddly enough the actual pulled muscle seemed fine. I’d seen some stiffness in the left leg on previous runs and it seems the pull last week accentuated the issue. The stiffness progressed to a point but never enough to slow me down (my best times were actually in the fourth and final km), but doing only 5K seemed like the right call.

After, the afflicted muscle continued to behave and the stiffness has retreated, so I think I’m probably going to be okay if I stick to 5Ks for now.

The average pace surprised me, coming in at 5:18/km, much faster than I was expecting, so that’s also encouraging.

The run on Tuesday will wrap up right around the time the sun is setting. I’m going to have to decide on whether to run at lunch on the yucky golf course loop, or switch to running on a yucky treadmill, or coming up with some other hopefully not yucky option.

Run 537: A bear-able run

Run 537
Average pace: 5:41/km
Location: Brunette Burnaby Lake (CCW)
Start: 11:29 am
Distance: 8.04 km
Time: 45:47
Weather: Sunny
Temp: 20-22ºC
Humidity: 33%
Wind: light
BPM: 157
Weight: 155.2 pounds
Total distance to date: 4182 km
Devices: Apple Watch, iPhone

On Friday afternoon as I was madly strolling to the SkyTrain station after work I noticed a sudden tweaking sensation in one of the muscles in my upper left leg, a little above the knee. This is one of the muscles that comes alive when I’m doing my lunch power walks but not one I notice as much when running.

The tweaking turned to actual pain when I made my way down the stairs into the station. Each time I stepped down I felt it sing a little. This seemed ominous.

Going down the stairs into the condo complex later was not as bad but it was clear a muscle was very stiff/sore in my upper left leg. I chilled out for the night and planned on a regular–if less intense–run today.

The muscle was still stiff but I headed out and my walk to the lake, deliberately slower, went without incident. I started the run, promising myself to a) keep the pace slower and b) stop if the leg started to hurt.

For the first 5K things went okay. The muscle was stiff but tolerable. By the time I was in the second half of the run the stiffness was getting worse and it was getting more difficult to maintain pace. At the 7K mark I figured if the stiffness stayed where it was I would finish, otherwise I’d stop early.

Alas, the stiffness continued to get worse so I stopped just after the 8K mark and walked out. I then walked up the the Production Way SkyTrain station to save myself about 3 km on walking back home, the better to rest.

The muscle stayed fairly stiff through the rest of the day.

This morning (note that while the date for this post is Saturday the 16th I am writing the entry on Sunday the 17th) I can still feel the muscle but the stiffness is pretty much gone when just casually walking around the condo. I’ll be heading out soon to do some errands, so I’ll see what it feels like when walking close to a normal pace. I’m hopeful that as I’m in my two-days-off period from running that it will recover enough to at least allow for short runs and that it isn’t hurt more seriously.

It would be the height of irony if an injury from walking ended my running early for the year. It would also suck corn dogs.

As for the actual run itself, conditions were nice–pleasantly warm, with low humidity. Energy-wise, the slower pace kept me feeling comfortable and the area around the 5K marker (still missing) wasn’t closed off. They had added a layer of finer gravel on top of the other new gravel and steamrolled it, making the surface much nice for walking and running. I expect they will finish the entire stretch over the coming weeks.

When I came into this stretch I noticed two people stopping to talk to a runner ahead of me. I had no idea what they were saying but the runner jogged back toward me and signaled to get my attention. She informed me that there was a bear up ahead. If you’re going to see bears on the trail, this is probably the best place, because being next to the fields gives you lots of room to steer a wide path around said bear.

I’d had this happen before but never seen the alleged bear. Today was different.

Strolling causally maybe 50 m up the trail from me there was indeed a black bear. I scooted out onto the field (a soccer game or other ball-oriented game was taking place just a short distance up the same field) and made sure I had enough space between me and the bear to insure that the bear didn’t think I was running away from it (which would be bad). The bear didn’t seem to notice, though. It just kept walking slowly along the trail, keeping to itself.

I saw a few people taking pictures, of course. I paused briefly before ducking out of sight around the corner, to assess the bear’s trajectory. I felt I’d be safe for the rest of the run. I hoped it wouldn’t eat all of the soccer players.

Did I run farther to create more distance between myself and the bear? It occurred to me to do this, actually, but no, I just ran as far as I could comfortably manage.

My pace was a slothful 5:41/km, which was expected given the bear hijinks and the stiff leg. To illustrate how cautiously I started, my first km was 5:43/km. My fastest came during the 6 km mark and it was still only 5:31/km.

Overall, a weird and eventful run. I’m hoping that the stiff muscle in the left leg is only just that–stiff, not actually pulled. I’ve applied some stinky Rub-A535 to it this morning and will see how it holds up when I’m out and aboot today.

Book review: Cold on the Mountain

Cold on the MountainCold on the Mountain by Daniel Powell
My rating: 3 of 5 stars

This is a solid little horror novel that feels more like an expanded short story. There are no side plots or other distractions here, just a Point A to Point B story about a family that takes a shortcut in the Sierra Nevada mountains that leads them into the small town of Adrienne, a place where evil gathers (literally, all the bad people of the world end up here after they die).

As part of the contingent of “normals” that blunder into Adrienne, Phil and Wendy Benson are forced to work for the “dark ones” to earn a chance for a once-a-year lottery that sees a bunch of people, both good and bad, released back into the world via magic portal. Adrienne is host to demons, serial killers, Joseph Goebbels (“Call me Joseph”) and the teenage Columbine killers who are never mentioned by name and are weirdly depicted as cartoonish villains.

There is some nice tension as the family struggles to both follow the rules and sometimes defy them, knowing the dire consequences of being caught, but the story is almost too efficient as it speeds along to the endgame, the various pieces all falling in place so quickly there is little time to allow events to sink in. The reader learns about Adrienne but it only ever feels like the surface is examined.

Phil, the protagonist of the story, comes across as a decent but ultimately bland kind of everyman. Bo, his brother on the other side, leads a search to find him and his family, and at one point he and his girlfriend come to believe it’s essential to get the local sheriff on-board to make their kooky plan to free the normals of Adrienne work, though it’s never stated exactly why he’s needed. The sheriff is nice enough as a character, but he becomes increasingly non-essential as the story progresses, to the point where I almost felt his alleged need was a deliberate red herring.

The conclusion will likely leave a lot of readers with a “What happened next?” feeling but that’s not necessarily a bad thing.

Overall, Cold on the Mountain has a comfortable old school horror feel to it. The journey is brisk–perhaps too much so–but the action certainly keeps rolling along.

View all my reviews

Run 536: A fast 5K with no chest mishaps

Run 536
Average pace: 5:12/km
Location: Brunette River trail
Start: 6:26 pm
Distance: 5.03 km
Time: 26:12
Weather: Sunny
Temp: 20-21ºC
Humidity: 30%
Wind: light
BPM: 171
Weight: 155.8 pounds
Total distance to date: 4174 km
Devices: Apple Watch, iPhone

One of the minor annoying things about after-dinner summer runs is the sun is low enough in the sky to shine directly into your eyes.

The fact that the sun was already too low to do that tonight is a good indication that summer is coming to an end. Also, all of the rain in next week’s forecast. My poor nipples. 🙁

And speaking of, I wore one of my sleeveless shirts tonight because the fabric is a little lighter and smoother than my other running shirts. Since I was going without nipple protection, this seemed to be the best way to avoid another chest-related bleedapalooza. And it turned out fine. I think I’ll only really have to cover up, so to speak, when it is raining, because that’s when the clothes start sticking.

So next week, as per the forecast I mentioned above.

Two things I noticed on the trail tonight: the first was a pervasive dusty odor. Despite the bit of rain we had on the weekend and a brief shower yesterday morning, it’s still quite dry, so cyclists are still churning up clouds of dust along the river trail. Weirdly, the whole trail still smelled of dust even when none was visible hanging in the air. It was kind of weird.

The other thing I noticed were lots of cyclists. They were all well-behaved, so no issues there.

Conditions were quite nice. With the sun tucked behind the trees and the temperature hovering around 20ºC it was nice and comfy, with only minimal sweating and no real dry mouth to bother me.

My idea was to settle back a bit after the last few runs but I somehow managed to end up with my fastest 5K of the year, at 5:12/km. My last km pace was 4:546/km, marking the first time this year I’ve broken the five minute mark.

At one point it felt like a stitch was going to develop, so I eased up a little, but even that had no effect on the overall pace.

My BPM was back up to 171, which is about where it goes when I basically sprint for an extended stretch.

I’ll try to moderate my pace for real next time.

Also, it was starting to get dark about fiften minutes after I got home, meaning the extended runs along the river and then to the lake are pretty much done for the year, there simply won’t be enough daylight after dinner. Alas. Even the 5K runs are going to start getting iffy in about a month’s time. I’ll have to decide between treadmill or noon runs then. I don’t like either option.

But for tonight, I soared.

Run 535: Protecting nipples

Run 535
Average pace: 5:26/km
Location: Burnaby Lake (CW)
Start: 12:59 pm
Distance: 10.02 km
Time: 54:29
Weather: Sun and cloud mix
Temp: 18-21ºC
Humidity: 62%
Wind: light
BPM: 161
Weight: 155.6 pounds
Total distance to date: 4169 km
Devices: Apple Watch, iPhone

I was having trouble with the plumbing so stayed home from work today. By early afternoon things seemed better enough to prompt me to do my run then instead of waiting until after dinner.

I reluctantly shaved my chest after Saturday’s run in order to make it easier/less painful to protect my strangely sensitive nipples. I covered each with a Band Aid before heading out because even though there was no rain in the forecast and it was warmer, I wasn’t taking a chance.

It proved unnecessary because a) it didn’t rain and b) it was warmer. Plus now the skin under the Band Aids is red after I removed them. Oh well. Maybe I’ll look into official Nipple Guards® or something in the future.

The sky was clouded over, which is nice for a run when the same clouds don’t empty a bunch of cold water on you. Less than a km into the run the sun started poking out and while it never got hot, the jump in temperature from 18-21ºC was noticeable.

I felt decent for the first half of the run, even peppy, but started feeling a bit tired on the second half as the temperature climbed and the sun did its thing. Annoyingly, they were doing more work on the trail near the now-absent 5K marker, forcing me to run across the field, which is lumpier than I’d expect for a sports field. Maybe I’m just used to running on gravel.

Looking at my splits, I got off to a sluggish start at 5:28/km but dashed along at 5:17/km for both the fourth and fifth km. Interestingly, the same thing happened on Saturday, when I was running counter-clockwise. I have no real explanation for this.

And speaking of detours, the sewer construction around the condo expanded today to the point where my three-block walk to Hume Park turned into a maze-like journey that added more than a km to my walk to Burnaby Lake. Never live near construction if you can help it, kids!

The slower pace meant my BPM was also down, to 161. Overall, it was still easily my second-best 10K of the year and with no other issues, a solid effort. Even better, I didn’t finish covered in mud and blood. Never finish a run covered in mud and blood, kids!

Run 533: Return of the smoke haze

Run 533
Average pace: 5:16/km
Location: Brunette River trail
Start: 6:51 pm
Distance: 5.03 km
Time: 26:36
Weather: Smoke haze
Temp: 22ºC
Humidity: 72%
Wind: light
BPM: 149
Weight: 156.6 pounds
Total distance to date: 4149 km
Devices: Apple Watch, iPhone

It turned out the forecast was sort of right for today’s run. It was 22ºC and cloudy–but most of the cloud was actually the return of the smoke haze. Boo. It seems a little weaker this time, at least, so the air isn’t quite as stinky.

It was humid as all get-out, though, so no dry mouth but much wet everything else as I sweated like a well-oiled sweating machine.

I opted for a basic 5K tonight as I headed out later than planned and intended to find a comfortable pace. I somehow managed to fall into a cadence that felt nearly perfect, and felt very light on my feet as a result. I didn’t really push at all until the final km.

As a result, my pace was 5:16/km, only one second off my best for the year, and my BPM was a low 149. For much of the run I was even able to breathe through my nose. This doesn’t sound impressive to a non-runner, perhaps (“Duh, I breathe through my nose all the time!”) but try jogging hard for a few km with your mouth closed and see what happens.

No issues at all on the run and only a few people opted to hit the trail on this rather dreary-looking evening. The shadows are starting to get a little more ominous with the sun setting earlier.

Overall, a spiffy and pleasing effort, despite the grossbuckets conditions.

Book review: The Ways We End: Six Tales of Doom

The Ways We End: Six Tales of Doom (Dark Collections Book 1)The Ways We End: Six Tales of Doom by Ann Christy
My rating: 4 of 5 stars

The bland cover of The Ways We End (at least of the ebook edition) is unfortunate because it may turn away potential readers and they would miss out on a terrific collection of stories by Ann Christy that depict apocalyptic scenarios that deviate from or subvert the usual zombies/nuclear war/alien invasion tropes. Even the author’s notes at the end of each story are a delight, conveying the infectious joy Christy had in both writing the stories and their reception.

All six stories are well worth reading and are best without spoilers, so here’s some quick takes, in order:

“A Cottage of Hunger” puts together a rules-following protagonist, her quite mad mother and a lost teenage girl in a world where the sun is permanently blotted out in the sky. It raises interesting questions on how far some people might go to preserve a sense of order, believing they are doing the right–the proper–thing.

“The Mergans” is a story set in the far future, where descendants of Earth have formed a galactic “Peace Force” that uses its military might to intervene in corrupted cultures of planets colonized from seed ships, mostly by blasting everything to smithereens. The particular culture in “The Mergans” is especially ghastly in its treatment of women, but its liberators may not be quite what they seem, either.

“The Mountains of Five” follows the journey of a 12-year old girl exiled from her village and forced to find her way through a dystopian landscape. I found this story particularly evocative, its spare prose perfectly capturing both the spirit of the titular girl, Five, and her dangerous journey. There is a twist ending of sorts, but the astute reader will likely see it coming. It doesn’t make the story any less effective, though.

“The Bridge.” As Christy notes, this is a quick little “spooky campfire” story and it works nicely for what it is, but it is the slightest of the stories collected here. Still, trolls.

“Rock or Shell” is a time travel story that hints at larger mysteries while never fully revealing them, leaving the reader with a sense that there is a lot more to this depiction of a mist-like realm where thought alone can send someone off into nothingness, erasing them from time and space. Dashes of humor lighten the constant undercurrent of tension.

“A Mother So Beautiful” is probably the darkest and most disturbing tale of the collection. It eschews the body horror of “The Mergans” in favor of telling the story of a sociopath whose mother attempts to stamp out aggression through genetics and achieves horrific success. Watching the world disintegrate from the eyes of a profoundly unstable person is something that will stay with you well after the story ends.

Overall, a fine collection of doom, where some hope or happy endings are (usually) at hand. Recommended.

View all my reviews

Run 532: It’s not the humidity, it’s the bug you just swallowed

Run 532
Average pace: 5:40/km
Location: Burnaby Lake (CCW)
Start: 9:45 am
Distance: 10.02 km
Time: 56:50
Weather: Sunny
Temp: 24-26ºC
Humidity: 55%
Wind: light
BPM: 160
Weight: 156.8 pounds
Total distance to date: 4144 km
Devices: Apple Watch, iPhone

It’s Labor Day so I went out and labored on a 10K run.

It was warmer than yesterday but my early start saved me from having to run in 30ºC+ temperatures. It was 24ºC at the start and 26ºC by the end of the run. It was also more humid so the sunny stretches found me sweating like some kind of machine designed for maximum sweating.

I didn’t experience any issues on this run, I was just generally a little slower, given the extra heat and humidity. My pace was 5:40/km, four seconds off Saturday, but consistent with the yuckier conditions.

The trail was fairly busy but unlike the last run there were no near-collisions. On the Cottonwood Trail I was humming along and doing fine in the shade of the canopy. The long version of “Disco Inferno” had just started playing (that song is long enough to last several km of running) when I felt a sudden catch in my throat. While grooving out I had swallowed a bug. Knowing a coughing fit was bound to ensue, I summoned up as much saliva as I could (sort of ew, sorry) and swallowed hard, twice. Better to just down the thing that try to spit it back out.

This did not work. Instead I started hacking fiercely and, strangely, I actually did manage to spit the bug out and was immediately fine after that.

I am uncertain if the bug survived. Sorry, bug!

The run went otherwise without incident, though the conditions were definitely eating away at my strength. I’ve been running just long enough in more seasonal temperatures that this Africa hot-stuff is throwing me off. It’s expected to last a few more days then the possibility of actual precipitation is in the forecast. I’m not running tomorrow and have a bike ride planned for Wednesday so my next run will likely be Thursday after work. The current forecast is calling for a pleasant high of 23ºC and cloudy skies. Good running weather!

Run 531: Long weekend EVERYONE GO TO THE LAKE

Run 531
Average pace: 5:36/km
Location: Burnaby Lake (CW)
Start: 9:39 am
Distance: 10.04 km
Time: 56:14
Weather: Sunny
Temp: 20-25ºC
Humidity: 48%
Wind: light
BPM: 155
Weight: 156 pounds
Total distance to date: 4134 km
Devices: Apple Watch, iPhone

Given the forecast (Africa hot) I thought it might be prudent to start the run earlier in the morning and to run clockwise, as there is less canopy in the first half of the loop when running this way, meaning I would face it while it was a little cooler.

I was wise to follow this plan. It was already 20ºC when I started out and was up to 25ºC by the end of the run less than an hour later. You feel a five-degree change in temperature.

Fortunately, the humidity was low so it remained tolerable (though I did experience some dry mouth, something that hasn’t happened much this sticky, sweaty summer). I initially tried to moderate my pace after a week off from running 10Ks and indeed, I felt a stitch in my lower-left abdomen around the 8K mark. I eased up a bit and it went away fairly quickly.

I also had a weird déjà vu moment as I ran down the part of the Conifer Loop with the tree root that tripped me up last summer. At around 10:10 a.m. the sun was still low enough in the sky that it was slanting through the trees in such a way that it created a flickering effect in my peripheral vision. This, combined with the trail being cast in a dappled combination of bright and dark areas made it difficult to see what was actually coming up even right in front of me. It’s quite possible that if I was running on the same side of the trail as the tree root that I might have tripped on it again, even knowing where it was.

I did not run on the same side of the trail.

I ended up with a pace of 5:36/km, a little slower than my previous 10K, but consistent with the higher temperatures.

This is the Labour Day long weekend and it turns out that this year a lot of people wanted to spend the first morning of it at the lake, as the trail was replete with pedestrians, joggers and one horse.

But no cyclists, hooray!

However, the most annoying moment came when I approached the second boardwalk. The boardwalks only allow for two people to comfortably walk/jog beside each other and because they are elevated, it’s not possible to duck out of someone’s way. I got onto the boardwalk, which in the clockwise direction, has a corner right at the start, and was immediately confronted by a pair of joggers moving fairly swiftly. The one to my immediate left did nothing to make room for me. I had to nearly stop so I could shift and get out of the way to keep from falling off the boardwalk.

That jogger was:

  • selfish
  • careless
  • going to get attacked by a rabid goose, if there is such a thing as karma

Really, the pair should have been moving slower and running single file. It’s just common sense given the conditions imposed by the boardwalk. Anyway, it was weird to be annoyed by another jogger instead of a cyclist.

Despite the near-collision, it was still a good run overall and the new shoes were problem-free, so yay.

August 2017 weight loss report: Down 4.0 pounds

For the month of August:

August 1: 159.8 pounds
August 31: 155.8 pounds

Year to date: From 165.9 to 155.8 pounds (down 10.1 pounds)

I stayed consistently below 160 pounds this month, ending the month at my lowest weight, 155.8 pounds. For the month I’ve lost four pounds, proof that running a crazy amount may have some effect on burning fat.

For the year to date I have gone from 165.9 to 155.8 pounds, a total weight loss of 10.1 pounds, putting me within reach of my official goal of 150 pounds and not much further from my unofficial goal of 145 pounds. Looking at my waistline now I think it’s fair to say I still have more than five pounds of fat clinging tenaciously to my mid-section, so 145 is probably the more realistic goal.

I did not switch to an all-donuts diet as I had feared.

Body fat for the first eight months of the year:

January 1: 19.1% (31.7 pounds of fat)
August 31: 16.7% (26.1 pounds of fat)

August 2017 big plans: Report Card

In this post I wrote up the big plans I had for this month. Here are the results!

  • get my learner’s license: NO
  • get my prescription updated for my glasses; get new glasses or at least new lenses: NO
  • clean up the junk in the living room: PARTLY YES (cleaned up some of it)
  • visit over on Vancouver Island: NO
  • go camping for a few days somewhere that isn’t on fire: NO
  • run 10K at least three times a week (starting in the second week): YES
  • write fiction for one hour each day: LOL NO
  • achieve world peace: PARTLY YES. I felt somewhat at peace during my vacation

GRADE: D+++

Not exactly a huge rate of success here. This is more of what scientists refer to as “a tiny smidgen.” As such, here are my big plans for September 2017:

LOL NO.

Book review: Haven

HavenHaven by Tom Deady
My rating: 2 of 5 stars

When I pick up a book by an author I’m not familiar with, I do it because the story interests me, or I heard something positive about it, or it was on sale.

What I don’t do is familiarize myself with the author before reading, and so it was that I found out afterward that Haven is Tom Deady’s first novel. It is also the 2017 Bram Stoker Award winner for First Novel.

There are things I enjoyed about the story, an old-fashioned horror novel about a monster lurking in the lake of a small town–and the perhaps more menacing human monsters that work and live around the lake–but I found the story dragged on too long and the melodramatic writing was distracting at best and eye-rolling at worst. I read through to the end but didn’t feel much reward for having done so.

Given the reviews and awards, it may be that I’m just not getting the tone Deady was going for. He renders the characters well for the most part, though some of the supporting characters are typical small town stereotypes, and all of them tend to be overly explicit in their thoughts and actions. Subtlety is not merely tossed out the window here, it is packaged up and shipped over to the other side of the world.

In Haven the sheriff is a cartoonishly evil man with an equally cartoonishly evil son. They serve as the primary antagonists while the monster–the design of which brings to mind the car devised by Homer in The Simpsons in how it’s a conglomeration of mismatched parts intended to be the ultimate representation of its form–occasionally devours, but more often just weirdly mutilates and kills people who get a bit too close to the lake.

The mystery is slowly revealed over the length of the novel, mostly by having characters remember key details from the past piece-by-piece as their minds struggle with the wicked effects of alcohol, mental trauma or both. Conveniently, everyone remembers everything before the story ends.

The whole thing is hokey and kind of silly and I’m actually okay with that, but the writing ranges from a plain meat-and-potatoes quality to stuff that would have benefited from a more discerning editor. Observe:

“Shut the hell up. Who the hell do you think you’re talkin’ to, your freak friend, huh, Father?” The last word he literally spit out, spraying the priest with drops of saliva.

Eddie’s body was literally in pieces.

It hadn’t rained all summer, literally.

He was literally doubling over he was laughing so hard.

Women had never been a problem anyway, but after nailing Greymore, they literally threw themselves at him.

Next he stole a glance at his partner in crime—literally.

What if his little sermon had worked, and Jake had gone off half-cocked (literally) to the lake to find the thing himself?

And my personal favorite:

The ground was literally shaking under their feet as rocks rained down.

Not figuratively shaking, no sir. This ground was literally shaking. It was the real deal, shaking-wise.

The point of these examples (and there are many others) is that any good editor would have stroked out that one word without hesitation and made every sentence better as a result. That this was not done does Tom Deady no favors as a writer.

But I will say this–while I found the ending ultimately unsatisfying and the story overly long, I kept plugging away at it, anyway, so Deady obviously managed to capture enough of that old-fashioned monster horror novel thing to keep me engaged. If he continues to write and gets better help with editing and revision, his workman-like prose can only improve. He can tell a story so I see promise here.

View all my reviews