Tuesday, November 18, 2014

Oh Yeah...Chaffing

I picked up Kathrine Switzer's book Marathon Woman this weekend and have almost finished it already. What an inspiring story! One think Switzer says in the book is that, "you find time to do thing things you wan to do." Granted, she was talking about writing love letters, but I am sure I can apply it to running. Although, truth be told, I don't particularly enjoy running at the moment, since I feel so slow and plodding. Like this post equating diet desserts to sex with your pants on, running the way I am running now contains none of the delight it held when running was new to me, because I know how good it can be, if only I were lighter or fitter. So I guess, to get to the thing that I love (running marathons, feeling strong and connected to my own body) I have to do the thing I hate, which is slogging through the miles to build a base.

The wild card in all of this is my thyroid. Pregnancy is hell on my body and I am still reeling from the precipitous birth of my youngest daughter nearly two and a half years ago. I experienced hyperthyroidism after the birth of my oldest daughter, which led to a 60 lb weight loss and my introduction to running. When I got pregnant again, my training was derailed by an appendectomy at 16 weeks, followed by blood clots in my lungs a few weeks after the delivery itself, which was a rather spectacular affair, involving the hallway and a lot of blood loss. This time, instead of speeding up, my thyroid went the opposite way and I gained 30 lbs over a 6-week period, went on medication and have been stuck ever since (for over a year).

In an effort to find out if my inability to loose weight is 100% related to my hormones, or if it is lifestyle (I changed from a job with non-traditional hours where I stood a majority of the time to a 9 to 5 office environment around the same time as my thyroid issues began) I started the Whole 30 diet. On the recommendation of my naturopathic physician, I jettisoned all grains, legumes, alcohol and dairy from my diet and am increased my exercise to at least four times per week. So far, I am only on day 9 out of 30, so the jury is out on whether or not this will help. I have to admit, I'm skeptical.

I'll post an update once I've finished the 30 days.

Thursday, May 30, 2013

Starting from Scratch

 Here's a little update since my last post is well over a year old:

It turned out I was pregnant during that 50k from my last post. I had every intention of running through my second trimester, including a couple of half marathons. But then I had an emergency appendectomy at 16 weeks, which pretty much tanked that plan. So I was basically a slug (exercise-wise) until I had the baby (healthy 7 lb. girl named Moxie) in June 2012 after about two hours of labor--a PR! I started running again about a month after delivery, but that got derailed when I ended up hospitalized for a week with pulmonary emboli (blood clots in my lungs)--which could have killed me but didn't.

Now I'm back to running.

In teeny tiny little distances.

When I started running in 2009, finishing a marathon sounded like a crazy goal. But then I did finish that first marathon and from there it was fairly easy to do  another and another, until it started to seem like just part of my life. Like I could just plan vacations around long races in interesting locations or decide on the spur of the moment to run a half marathon and it would always be that way.

Except now I can't really do that because I can barely run two miles. Seriously. Two! That's it. I did a 5k on Mother's Day, but it's not like I ran the whole way. (Holy hell, it's exhausting just thinking about it.) The problem is that I know how much work it takes to train for a marathon. The first time around, ignorance was truly bliss. I was constantly amazed with my gains; every race was a PR. Not so much this time around.

Here's a short summary:



Benefits of Re-Starting a Running Program
PRO
CON
I have an entire wardrobe of tech fibers
None of it fits
I could start the Natural Running plan now that dropping mileage down to sub-10 miles/week isn’t a concern
I’m not really going to do that
Running 26.2 miles in a row doesn’t sound so crazy now that I’ve done it several times
Yes, it does
Running such short distances saves on Body Glide
There’s more of me to chafe


The fact is, I am completely demoralized because now I  know how much work it takes to get there when you're starting from scratch, and I am just not sure I can do it again. I tried to go back to my running group for motivation, but while I was waddling off going to Starbucks' Frappacino happy hours, having a baby, and letting my Garmin die of neglect, they were taking long runs to a WHOLE. NEW. LEVEL. I tried a few times to follow along for a couple of miles, but they lost me before we'd  gone even a block. And I don't blame them. I am slow. SLOW. SOOOOOO SLOW.

Trying to stuff my giant nursing boobs and floppity belly back into my running gear isn't exactly a moral booster. I've taken to running in the early morning so no one can see me (and also because my life has absorbed the time I used to set aside for running).  I've been trying to write this blog post almost as long as I've been trying to get back to running. It's not where I'd like it to me, but I'm going to kick it out the door anyway. Like I need to be kicked out the door for a run. Maybe putting this down on *digital* paper will be motivating. I doubt it.

Me and my girls at the Run Like a Mother 5k. Good thing most of my tech wardrobe is *slimming* dark colors.















Sunday, October 2, 2011

Delivering My First 50k


For me, running a 50k for the first time was a little like being pregnant—I was looking forward to it more before it actually happened, I spent way too much energy just trying to stay upright, and at a certain point I just wished like hell it was already over. 

Near the beginning of the trail
My husband and I chose the Baker Lake 50k for our second attempt at an ultra-marathon because the course is an out-and-back, so there were no double loops to tempt us to quit at the halfway point. It is located in a beautiful region and the course was supposed to be easy, with relatively little elevation gain. It is also just a 50k, that is no 25k or 50 or 100 milers are held on the same day (therefore, if I wore my race shirt there would be no question of which distance I completed). Superficial of course, but you should never underestimate the power of a good race shirt. In fact, I’m wearing mine right now and might never take it off.

Another benefit of the location near Baker Lake, Washington is that the campground where the race started offers free sites after Labor Day. We ended up missing the early start time by a few minutes because we were still breaking down our campsite when the horn sounded about 10 minutes early. The sun hadn’t completely risen yet, so we weren’t that disappointed about not making the early start because the visibility was still a little poor. We spent the hour before the regular start time generally being intimidated by the other race participants, nearly all of whom looked like they usually run 50 kilometers before breakfast. 

There would be only one aid station, so we both wore hydration packs loaded with sports drink (Nuun for me, Gatorade for Aaron) and plenty of gel. I also carried a carb/protein drink (Perpetuem by HammerNutrition) in a handheld water bottle. We each packed an extra shirt and socks as well as more gel and some Body Glide in our drop bag that would be driven to the halfway point for us to use at the turn-around.
One of the numerous bridges
The starting horn sounded and we were off, generally staying toward the back of the pack. We ran up a paved road and across a dam. I’m not necessarily scared of heights, but I still found myself avoiding looking over the edge to the bottom so far below. After we crossed the dam, we went up a gravel road for about a mile and then turned off onto the single-track trail and were instantly enveloped by thick forest. The trail was padded with pine needles and undulated lazily through the woods and over many wooden bridges.

Fortunately, wearing the packs allowed us to carry our cameras and we took plenty of opportunities to take photos—before it started to rain. Yes, it started raining about an hour into the race, and it wasn’t just the omnipresent Pacific Northwest misty sort of rain, it was pretty much a downpour. The canopy of trees tended to shield the trail in most places, but it was still wet and getting wetter. At this point, we were about six miles in and feeling pretty good about our 12 minute per mile pace. Although we told ourselves and everyone else that “finishing is winning’” we both really wanted to finish in between six and seven hours. 
Me leading the way over a river crossing in the mist

The trail became slightly more treacherous and rockier at about this point. It was also punctuated with many stream beds to cross, some with flowing water that soaked our feet no matter how careful we were. The foliage along the trail become significantly thicker, obscuring the ground for large stretches at a time making it difficult to go much faster than a walking pace for fear of tripping. It was difficult to settle in at a comfortable pace and keep it steady for long because of the constantly changing terrain. I lost my footing several times and recovered, except one time when I actually fell. My water bottle broke my fall with a wheeze, prompting me to compare it to an airbag for runners. I was none the worse for wear and quickly scrambled up and kept running. If I had tripped any later, I would have been a road hazard because we ran into the first runners coming back the other direction about a minute later, four miles from the halfway point.

We stopped to let others pass many times in the next hour, stepping off the trail because it was so narrow. Aaron stepped into a patch of stinging nettles at some point and spent the mile before the aid station with a burning sensation on his left calf. One thing that was hard not to notice was how pleasant and courteous all the runners were. Without fail, everyone who passed us or whom we passed offered a kind word. I’m not sure if this is common among trail runners in general or ultra-runners in particular, but I suspect it has more to do with the distance; these people know what it takes to push their body past limits that seem inconceivable to most people and understand that sometimes a friendly word is all that is needed to get through the next mile. 

We finally reached the turnaround about three and a half hours into the race. We refilled our packs and I changed out of my soaking wet shirt, used the bathroom and we were on our way once again. This time Aaron took point and pretty soon I wasn’t able to keep up with him. After Haulin’Aspen, we agreed that we would both run our own races at Baker Lake. Of course, I expected this to mean that I would beat him with no hard feelings, but I was feeling pretty wrecked already and was actually pleased that Aaron hadn’t started to physically break down yet, as he had in other distance races. Normally, my super power is endurance and I typically have negative splits (where I run the second half of a race faster than the first), passing many other runners in the last few miles, but for whatever reason I was merely mortal today and feeling pretty grim about the next twelve miles. 

Those who know me know I never waste a downhill, but I found myself walking the downhills on the way back because I was in quite a bit of pain. I actually walked a majority of the last half of the race, only running when I was sure I could go for a significant distance without having to break my gait because of a steep patch or a creek. Every rock seemed to rise up out of the trail like a whale breaching the surface of the water—surprising and dangerous. The combination of the rain and the footfalls of other runners had caused the trail to degenerate into a muddy morass in several places. I stumbled less on the way back, but only because I was going slower and selecting my foot placement with excruciating care. I hadn’t felt this bad in a race since my first marathon and I hadn’t even gotten to 21 miles yet. I knew I had to keep eating and drinking, but the gels made me gag (in the best of times they aren’t great) and even the taste of my own sweat from where the nozzle of my hydration system had been resting against my chest was hard to take, but I chocked everything down anyway and I’m sure I would have been worse off if I hadn’t.

I overtook a few people on the way back and our brief conversations were a welcome distraction, but I was essentially in complete solitude for the next several hours. I alternated between hoping I would come across Aaron so I would have company and hoping he had already finished. My Garmin had given up the fight at about mile 24  when it got so wet running through the overgrown section of the trail where I held up my forearms to ward off the wet blows of the branches. My Nike Sportband was still going strong, but because it’s a pedometer and doesn’t connect to GPS, I knew the mileage could be significantly off. I got something of a second wind around mile 26, which was probably a combination of knowing I was nearly finished and the fact that the trail became significantly easier; knowing at this point I was going further than I had ever gone before was also motivating. As per my usual technique, I kept mentally breaking the course into tiny fractions (five sixths complete!), but I had to constantly revise my math as my mileage (according to the Sportband) kept increasing but I hadn’t yet reached the road I knew would start about a mile and half from the finish. I finally popped out of the trees at what I thought was 30.25 miles hoped that my recollection of how long the road was had been incorrect. The Race Director waiting there quickly dispelled that notion when he told me I had one and three quarters of a mile to go. I stopped to chat and have a drink since my pack had run out. I took a cup of what I thought was Gatorade but that turned out to my Mountain Dew. I don’t think I’ve had Mountain Dew for 20 years and it is just as nasty as I remembered. 

I started running again before my stomach rebelled, and this time I resolved to run the rest of the way without interruption. I passed one more person on my way in and just after I crossed the dam I saw Aaron waiting for me and cheering me on. He ran me in for a ways, but I have never half-assed it across a finish line before and I wasn’t about to start now—I took off and sprinted across the finish line at 7:44:40—exhausted and sore and happy, kind of like at the end of a pregnancy. And one more reason why the two are alike: I didn’t get a medal when this one was over either.

Tuesday, August 9, 2011

Haulin' Husband

Note: The Haulin' Aspen trail marathon has about 2300 feet of elevation gain and about 2500 feet of elevation loss. It is course is described as "challenging" on the website and (like Fueled by Fine Wine) the promise of booze at the end becomes a motivating factor. I had never done more than 25k on a trail until this event.

The morning of the race dawned crisp and clear in beautiful Bend, Oregon. Bend is in the high desert, so it is not unusual to have very chilly mornings in August. My husband had registered us both for the full marathon for my birthday. We arrived at the elementary school where the race started to blissfully short port-a-potty lines and an interesting cast of characters. My particular favorite was the guy with vertebrae threaded onto his truck antenna like a more sinister (but less creepy) Jack-in-the-Box ornament. Frankly I was pretty intimidated when all of the early starters (usually reserved for people expecting a 6-hour time) had body fat percentages lower than my shoe size. There were also a grip of people in Cascade Lakes shirts, a 216-mile relay race that had ended the day before and I overheard a discussion between two runners who had both run a 50 miler the previous weekend. Can you spell H-A-R-D-C-O-R-E? Fortunately, a fair amount of the starters at the regular time looked more my speed and we queued up for the pre-race briefing: The course was to be well marked with "confidence flags" that would be placed to reassure runners that they had indeed taken the right path. I have always maintained that the interstate needs confidence signs--Congratulations! You are actually on the way to the airport!

The race started and we left the paved parking lot to immediately bottle-neck at the start of the single-track course. Aaron and I were perfectly content to stay toward the back of the pack. I know that my strength has always been a strong finish. I was worried about Aaron from the start just knowing the difficulty he has had in the past with physically breaking down towards the end of long races. I put it out of my mind and just enjoyed the beautiful scenery and the cheerful banter between me and my husband. At about mile 4, I had to tie my shoe <wink> and after about 10 feet back up the trail, I realized that I had inadvertently gotten a stalk of weeds stuck in my pants. I pulled out the 2 foot stem, but the leaves remained behind (pun intended). In what I am sure was a WTF moment for the runners behind me, I plunged my hand down the back of my capris in an attempt to scoop out the chaff. I knew it was a loosing battle and wished once again that it was possible to dip my entire body in Body Glide.

For the first several miles, we played leap frog with a particular pair of runners. After the third or so exchange of the lead, we started talking to them. The big guy, Peter, was talking up the Galloway (run/walk) method with evangelical fervor, and since we couldn't deny that all of us ended up at about the same pace, we decided to join them. It turns out that there were buddies from way back in high school. Peter is raising money for cancer research by running 50 marathons (one a month; he's about three years in) and his buddy Haig was running his first marathon ever. We ran for three minutes and walked for one minute together. My only experience with Galloway is limited to knowing someone who does 9/1 intervals, so I was surprised at the short length of time for the run. It seemed to work pretty well though, especially since the course was on a steady climb. We had a great time talking to these two guys; one of the best things about running  is the people you meet along the way. I mean that in the larger sense too, because I am blessed with a very supportive community of running companions.

At the top of the BIG HILL. (Thumb left in
for authenticity)
Aaron had run this same marathon last year, so he knew what was coming up--a big hill. Make that a BIG HILL--at mile 12. It was pretty steep and everyone just walked for about a mile and a half. Aaron, Peter, and Haig all have longer legs than I do, so I fell behind and didn't want to stop to take a photo; however, let me assure you the view of Mt. Bachelor in one direction and the entire city of Bend in the other would have taken my breath away if I had any left. Aaron was waiting for me at the tippy-top and a girl, Jen, who I had fallen into step with, took our picture together. We started running again and soon caught up with our new running buddies at the start of some truly amazing single-track. I took point right away and sailed down the mountain at an easy 8:00 mile clip. It was so fun, we where literally whooping for joy--those almost involuntary expressions of glee that you think can only be experienced on roller coasters until you find yourself tearing through a forest on sandy single track, high on fresh air and exercise.

Looking over my shoulder to see if Aaron was having as much fun as I was, it was immediately obvious to me that he was in a bad way. I gave up my lead and slowed to a trot as I repeated "don't be selfish" over and over in my head like a mantra, because all I wanted to do at this point was RUN. But...ultimately, my relationship with my husband is far more important than a silly race. There will be *many* other marathons in my future, but only one husband. With that in mind, I told him I would finish the final 11 miles with him no matter what. So we walked. For the most part, walking was okay, especially when I had to see my husband nearly crumple in agony whenever he tried to run, as though some malicious wizard from Harry Potter had struck him with the cruciatus curse. That was hard, but even more painful was when we neared the finish line and had to go past a long line of finishers waiting in the port-a-potty line. It felt like the walk of shame when they all started clapping and cheering for us. I felt like a failure and secretly wished for some physical evidence for our slow pace (a little blood, maybe a broken limb). However difficult it was for me to walk, I know it was far more difficult for my husband to ask me to make that sacrifice. We finally crossed the finish line together at just under 6 hours. And though there was never really any other option, I am proud that we finished this race together, however long it took.

As with most things, there is usually a silver lining. I try to take lessons from each race I do and this one taught me that I am more than capable of surviving a six hour race. This is good news indeed as I head into training for the Baker Lake 50k in October--my first ultra marathon. As a bonus lesson, I also discovered that caution trumps speed when it comes to pulling up one's knickers during a shoe tying break.

Monday, July 25, 2011

Short, Hard, and Dirty (but Hey, She's Pretty)!

The course was about .25 miles short of 13.1; the elevation
gain and loss made it very hard; and here is a great illustration
of both the dirty and the pretty scenery.
Fueled by Fine Wine is a half marathon that takes place in Dundee, Oregon, the heart of Oregon's wine country. Their slogan is something along the lines of, "you won't run your best time, but you'll have the best time." A more accurate appeal might be, "come try for your personal worst and then drink wine until you don't care about your finish time." I have to hand it to them though, it works. I have run it both years (it was started in 2010) and both years the course was changed at the last minute and turned out to be harder than advertised. This year was twice as hard as last year because it had at least twice the number of hills; it was, however, at least twice as beautiful to help ease the pain.

And boy was it painful. I haven't been this sore since I ran a marathon after six weeks of solid rest. I've been gimping around the house like my hips are made of peanut brittle. I'm sure this has a lot to do with my fetish for running down hills as fast as possible. In fact, I actually heard someone say, "she's coming in too fast, she'll never make the turn" as I came flying around the corner at the (downhill) finish line, as though I were coming in for a landing on an aircraft carrier. I'm going to hold on to that memory, as I doubt anyone will ever again worry that I'm running too fast (which I wasn't by the way; I made the turn just fine, thank you very much).

The other reason I, and everyone else I know who ran that race, took so long to recover is that we do not run enough trails. Although FBFW wasn't technically a trail race, there were swaths o the course that ran through the vineyards. Not nicely groomed trails, but lumpy, bumpy, grassy fields. All the little stabilizing muscles get called into service for this kind of running and it really make you sit up and take notice that those muscles rarely get a work out. Running trails is a great way to strengthen those axillary muscles, which can help prevent injury. They are also a heck of a lot of fun. I've gotten into kind of a complacent spot with my running lately and I'm glad this race came along to shake me out of my rut.

Friday, July 8, 2011

How a PR Really Feels

My first year of running was 2009. That year, everything I did was a personal record (PR) because I was always running a distance for the first time. The following year, I PR'd at nearly every race simply because I was getting stronger and learning more about running, so there wasn't a huge sense of accomplishment at getting better because the original bar was set so low. This year, after an injury set-back, I had not PR'd even once, though I was already half-way through my season. I kept getting close, but could never quite grasp that brass ring. I set an ambitious goal for the Seattle Rock and Roll half marathon to not only break my personal record, but also to finally break two hours in a half marathon.

As the race day wisdom goes, no new is good new, that is, don't muck up your race by wearing new shoes, trying the sponsored sports drink for the first time on the course, eat cereal for breakfast if you always have toast, or otherwise mess around with your routine. With that in mind, I set out to find a way to get coffee at five o'clock in the morning since I am now so beholden to that caffeinated mistress that I am afraid I will cease to function without her favor by mid-morning. The hotel where we were staying (The MooreI highly recommend it) has neither coffee makers nor microwaves in the rooms (The MooreI highly marginally recommend it). One would think it would be easy to get coffee in Seattle, what with all the Starbucks within Starbucks, but that proved not to be the case. After an exhaustive Yelp search and several phone calls to downtown coffee shops, it turned out that downtown Seattle is a coffee wasteland on Sunday mornings. I actually thought about purchasing an electric coffeemaker to bring along because the one we use at home requires boiling water. Aaron suggested canned coffee, but that only comes pre-mixed with cream, which I do not take in my coffee and do not want to start, especially on race day. I settled on iced Via, a specialty instant coffee meant to be mixed with cold water. It comes pre-sweetened and tastes like coffee-tinged ass, especially mixed with tap water in a plastic hotel cup. I choked it down anyway.

This whole coffee thing feeds into my race strategy: Start slow, never waste a downhill and avoid port-a-potty stops. I am sure I am not the only person who relies on caffeine to get things moving (you know what I'm talking about). The Via worked, though not necessarily efficiently. I ended up getting the job done, but in drop-cookie fashion (two tablespoons at a time); fortunately, the batch was complete before the start of the race.

Chilly race morning.
The weather was forecast to be cool, but it turned out to be quite chilly and the sky looked ominously like rain. Our group of twenty or so Portlanders battled the cold by wrapping ourselves in blankets while huddling on cardboard boxes, hobo-style. Some of us <casual whistle> may also have nabbed a sweatshirt from the donation bin to wear until our coral got to the starting line. I am a big fan of coral starts, especially in races with so many people, but it does make for something of an anti-climax when you hear the gun go off and then have to wait 17 minutes before you can start to run. It never did rain, but the overcast sky, while making the temperature nice for running, did lend a gloomy cast to the course, which made it seem not quite as pretty this year.

I started out with my fast friends (whom I rarely run with) for this race, like I had somehow been promoted. It was nice, but a little disconcerting because I felt some performance pressure along with the loss of comfort from having my regular running buddy at my side. I did a pretty good job of keeping up with them until my left arm went inexplicably numb around mile 2.5 and I slowed down to eat a gel and assess the situation. I finally decided it didn't matter since I don't run on my arms and the numbness didn't appear to be spreading. I wasn't really feeling my best and said as much to my friend Gayla right before a downhill (which, according to my strategy, I did not waste). That downhill (around mile five or so) got me into a groove and I was able to get back to a pace that would put me near my goal and that I thought I could sustain. However, my Garmin was getting more and more inaccurate (according to the course markings) so I couldn't rely on my average pace display. I tried to do math in my head according to my elapsed time but kept getting distracted by the teenage cheer squads along the route who got progressively more slutty-looking until I was worried they would be down to thong panties and pasties by the end of the race.

As the miles fell away and I got closer to the finish line, I knew I was close to two hours but couldn't be totally sure because of my Garmin issue, which was exacerbated by the long tunnel around mile ten. I picked up the pace to be within my margin of error and crossed the line at 1:57:15. Finally a PR!

Oddly enough, I have mixed feelings about meeting my goal. I didn't leave everything on the course as they say, and so I am left with the feeling that I could have done better. Surely this is why running is so addictive. Initially it was enough to see big gains; now as I pursue ever smaller increments of improvement, I feel like I am also pursuing this new, more elusive goalto not just go faster, but to go as fast as I am absolutely able. I want to find my limit, to know without a doubt that I have reached it, and then find a way to push that limit further; to know how a PR really feels.