Pages

Friday, May 30, 2014

Snapshot Book Review: Fiend

FiendFiend by Peter Stenson
My rating: 3 of 5 stars

As a book about drug addicts, Fiend really succeeds. The mind and motivations of Chase are exactly as simplistic and yet complex as any drug addict I have ever known or read about.

As a zombie novel . . . it's not bad. Stenson doesn't delve very deeply into how or the zombie apocalypse happened, and since the book is told from the first-person point of view of a meth head, that makes sense, because he wouldn't know more than what he could observe and wouldn't care enough to sit there and "figure things out." Still, I can't help but feel as though it's a bit of a cop out. How did drugs keep this small contingent of people from being infected with "zonbie disease?" How did the disease come about in the first place? I'm a curious reader. I want to make sense of things!

My biggest issue with this book was its pacing. The pace starts out frenetic and really just tries to maintain that level all the way through. Yes, there are "down moments" when Chase reflects on the past or stops to really think about whatever situation he's in, but these feel more like stalls in the action than valleys in a rolling arc of narrative. Essentially there are just too. Many. CLIMAXES!

This might be the first time I've ever said this, but I think Fiend will do much better as a movie than it will as a novel. I hope a producer has the insight to pick it up.

View all my reviews

Thursday, May 29, 2014

Snapshot Book Review: The Goldfinch

The Goldfinch: A Novel (Pulitzer Prize for Fiction)The Goldfinch: A Novel by Donna Tartt
My rating: 4 of 5 stars

I can absolutely understand why this novel won the Pulitzer Prize. It is extremely well written, with an astounding level of detail that is--as a resident of the New York City area, I can verify--very accurate. The scope, subject matter, and themes of the book are those that resonate today and will stand the test of time--all hallmarks of a prize-worthy book. Each character is nuanced and believable, and the narrator Theo is both reliable and unreliable in ways that any reader can identify the way they would a slightly neurotic but still endearing friend.

My feelings about Theo waxed and waned throughout the duration of the novel, which is an aspect I actually liked. It's difficult to enjoy a book where you don't particularly like or sympathize with the narrator, and my feelings for Theo shifted continually as the story progressed. He's essentially a sympathetic jerk, a stubborn pushover, if you will. His friend Boris is the perfect foil: a guy who is clearly trouble but with a good heart and a zeal for life that is addictive to both Theo and the reader. And who cannot relate to Theo's idolization and obsession with Pippa? She represents the obsessive adolescent attachments we label as "love" and pine for all our lives. Nothing resonated more with me than that subplot.

Of course, I had my qualms about this book. Sometimes the detail I found so impressive got to be too much. "Just get on with the story!" I found myself thinking periodically. Also, the very end was a massive disappointment. I don't mean the ending of the story itself; that was appropriately bittersweet. Life doesn't work out perfectly, and I think Theo's story ended on exactly the right note of an "almost" happy ending. However, those last cluster of pages are what really did me in. My opinion is that if the reader didn't understand Theo's mindset and the themes of the novel by the time he or she reached the end, then no amount of tiresome, explanatory exposition was going to give them a better reading experience. I read those last twenty pages only because I felt that I had to; I had come too far not to finish the book to its absolute conclusion. Were I the editor, however, I would have lopped them right off and finished the book where the story itself ended, leaving the reader to speculate on his or her own.

View all my reviews

Sunday, April 27, 2014

La Jolla Half Race Recap

I never thought I'd say this, but second place never felt so disappointing. And not for the reason you'd expect, either.

I never had any illusions about winning this race. After looking at the course and the race times from last year, I honestly never even thought I'd place at all, outside of maybe an age group award. So placing second woman overall was, frankly, a huge surprise. It was such a surprise, in fact, that it upended my plan to hurry back to my hotel in order to get ready for my (already delayed) workday. But really, I had to stay. How many times do you get to accept an award in front of an audience? Not many.

The thing was, though, I'd have gladly traded my second place plaque for a PR. I went into this race with my sights set on breaking 1:28:00, and the bottom line is that I just didn't do it. I wasn't even very close. So second place woman or not, I was disappointed.

The one thing I can say, though, is that the lack of PR was not for lack of trying. Hindsight is 20/20 of course, so it's tempting to look back and say, "Oh, at mile 7 I should have just sucked it up and picked up the pace. I was probably just being a baby," or, "I should have taken it out slower, and maybe then I'd have had more energy for that outrageous hill at mile 5." But the fact of the matter is, I gave it everything I had.

My race started before the gun even went off. I got to the Del Mar Racetrack parking lot, did a bit of warmup jogging and drills, and realized that I definitely needed to hit the Port-a-Johns or there were going to be problems. So I got in line. Fifteen minutes later, the line had barely moved, and we were five minutes away starting the race. So I did the only thing I could do: I found a nice array of bushes, wedged myself between them and, well, that was that. Then there was the national anthem, the gun--which was actually just an announcer saying "Go!!!"--and we were off.

I took it out as close to tempo as I dared, aided by the fact that the very beginning of the course tilted a bit downhill. I was feeling pretty good by mile three, pretty confident that I could hold this pace. It was a lovely day, the breeze felt great, and I was closing in on a small cluster of girls in front of me. Then there was an uphill, and the 1:30 pacer passed me, which gave me a bit of a scare. But that was followed by a long downhill overlooking the Pacific where I just let my legs spin. That put me back in front of him again, where I belonged, which would have felt nice if I hadn't been staring straight ahead at the mountain that we were about to climb. And that's when the race got hard.

I am not a powerful runner. I never have been, and I while I might be someday, right now I have a really hard time sprinting up a hill, never mind a mountain. So I compensate by taking it slow going up and then I make up time coming back down. That was my plan of attack on this course, too, but I knew that to average 6:42s per mile, I couldn't slow down too drastically. Therefore, when the 1:30 pacer passed me (again!), I decided that the least I could do was keep him in my sights. That, surely, would be good enough. But then a woman passed me, charging up the hill like it was nothing, and I began to doubt how the rest of this race was going to go.

A mile and change later, I began repeating the mantra "shut up" to my brain, which was having a panic attack over the fact that I couldn't seem to get my pace back under 7:30/mi. I had averaged something like 8min/mi up that terrible hill, and now I couldn't get it back down, even though the course had flattened out. "You're never going to make up that time," my brain kept saying, "and your legs feel like they were just beaten by heavy wooden mallets. AND you're only halfway done. How are you going to even finish the next 6 miles? You're toast." Shut up, shut up, shutupshutupshutupshutup.

Around mile nine, when my brain had moved from doubting this race to doubting all distance races--"Maybe you don't have it in you anymore to run distance. Dropping time used to feel easy; you didn't even notice until you'd done it. Now you're running all this fancy extra stuff and what's it gotten you? One, maybe two minutes faster? Pathetic. You think you're going to PR in the Chicago Marathon? Dream on."--a tall shirtless guy appeared beside me. We'd already exchanged places a few times throughout the race, him passing me on the uphills and me blowing by him on the downhills, but now we were on the flat and and I was struggling to get my legs moving again. But no way this guy was faster than me. No way.

That thought was enough to help me get moving again, at least to keep up with him, even as my breathing became more and more ragged. Miles nine and ten weren't nearly as terrible as the ones before had been, and when we hit another downhill, I closed in on the woman who had passed me on that mountain. "Third woman!" spectators kept shouting, holding up three fingers. Third? Really? Me? I wasn't even running very fast!

With another downhill, I caught the woman and trailed her halfway through mile eleven before I passed her . . . only to be passed by the 1:30 pacer again. "Shit!" I panted aloud. "Don't worry, I'm ahead," he shouted back over his shoulder. He'd better be, I thought, because if I finish over 1:30, I am going be super pissed. Things seemed to be going well now; I was pretty sure I'd dropped my pace back down and I could keep this up for the last mile . . . and then we hit another hill. All I could think, as I charged that hill with my arms pumping furiously, was She's right behind you. If you let her pass you on this hill, it's over. Are you really going to accept third when you have second right now?

As someone who's run a fair number of half marathons, when you're giving a race your all, that thirteenth mile feels endless. Where's godd*%$ the finish line? is all you're thinking as your legs scream and your chest feels like you're having an asthma attack and a heart attack all rolled into one. The race ended with a steep downhill, which I should have been happy except my legs felt so out of control that it was all I could do to keep them from flying out to the sides or buckling beneath me. But she hadn't passed me. The woman hadn't passed me. And now we were on a downhill. I was going to take second!

When I crossed the finish line, the clock read 1:30 and change. I was gasping; I could barely stay upright; I felt like this was the hardest half marathon I had ever run; and I hadn't even come close to the 1:28 goal I had set for myself. Awesome.

Winning 2nd definitely redeemed this run for me, because otherwise, there'd have been no silver lining. I started out feeling determined and excited, and ended feeling like crap. Still, whether it sounds crazy or not, I really do think I can break 1:28. Just not today, I guess. Next time.

La Jolla Half Marathon

Race Length
Finishing Time
Average Pace
Overall Place
Gender Place
Age Group Place
(F25-29)
13.1 mi
1:29:08
6:48/mile
32 / 5,891
2 / 3,058
n/a* / 543

*Note: When you place in the top 3 for your gender, you are automatically removed from the age group rankings. It's my first time to be excluded!

Wednesday, April 23, 2014

Snapshot Book Review: Sous Chef

Sous ChefSous Chef by Michael Gibney
My rating: 3 of 5 stars

It's important that I specify that I'm an outsider to the food industry. The closest I ever came to working in a restaurant was when I worked at a coffee shop on my college campus. While I suppose that technically "counts," it was also an insulated experience due to the fact that it was operated by the campus dining services and nearly impossible to get fired.

I enjoyed this book, but I think I'd have enjoyed it a lot more if I were part of the same insiders group as Gibney--that is, chefs, cooks, and anyone else involved in the preparation of food in a restaurant. You do get a sense of his experience in the kitchen, which is what I was looking for, but he sticks to the insider's lingo, which is alienating without footnotes to reference (I was halfway through the book before I discovered there was a glossary in the back!), and the frequent conversations the cooks have in Spanish are never translated, leaving me to guess what they might have said with the help of my incredibly limited knowledge of the language.

His descriptions of food in its various forms--packaged, raw, cut, cooked, served--are very beautiful and sensory, which is great, but for an impatient reader like me, I thought Gibney got carried away, so much so that he lost the forest for the trees. I didn't want to read a manual on how to properly de-bone a fish; I wanted a book that tells me a story. And this book, quite honestly, didn't. "A day in the life of" was a very accurate depiction, but at the end, I didn't much care about any of the characters, including Gibney himself. Sure they might be real people and this might be a real day, but I needed at least a whisper of a story in there, to keep me hooked. Instead, I was left feeling adrift as I turned the last page.

The book does earn three stars, however, because it accomplishes what it set out to do: give the reader the experience of being sous chef for a day. Complete with second-person narration and all. I read the book to understand that experience a bit better (admittedly as research for a book I intend to write), and I now feel that I do. So bravo for that. And now I'm going to go read a proper story.

View all my reviews

Monday, April 21, 2014

Snapshot Book Review: Save the Cat!

Save the Cat!: The Last Book on Screenwriting You'll Ever NeedSave the Cat!: The Last Book on Screenwriting You'll Ever Need by Blake Snyder
My rating: 5 of 5 stars

Loved this book! The only drawback is, well, I'm not a screenwriter. But I read this book at the behest of a friend who told me it would help me devise a strategy for working out plots, and it definitely fulfilled that promise.

My favorite aspect of this book was its tone: it reminded me of a coach giving tough-love instruction to his or her athlete. The message--over and over again--is, essentially, "You don't want to do this tedious, agonizing, impossibly hard bit of work? Well suck it up, because it's the only way to get the results that you want. So here's what you've got to do." Snyder's writing style is chatty yet informative. He offers personal experiences and notes from other writers and producers in the industry to exemplify why certain things work or don't work. Yes, at times he gets a tad repetitive, but in a how-to book, you pretty much have to be repetitive to ensure that your point sinks in. So I'll forgive that minor annoyance.

I'm excited to try some of the strategies. Now, if only someone would write this book, exactly the same, only different . . . for novel writers!

View all my reviews