Doug:
To put it lightly, it has been a rough few weeks. Sometime between my 13 mile run, and my 14 mile attempt, my knee decided it didn't like this running thing. I'm sure many of you have experienced the same problem. A few miles into the run, the lower part of your knee begins to throb in pain. Then, as quick as one leg extension, the most horrible feeling shoots up your side. The first time it happened I had just reached the top of Massachusetts Ave. The pain was so sudden that it literally brought ground. I was reduced to jog/walking the rest of the way home, cutting my 14 miles in half.
It came as a huge blow to my not only my ability to run, but my running confidence. The next morning I told Justin I didn't think I'd be able to continue, but thinking about how much effort I have already put into this race, quitting without a fight was not an option.
The first several runs after the pain began, I couldn't go 3 or 4 miles before my knee told me to stop. I tired icing, cutting back my mileage and buying a knee band. While all of that helped, I still failed to complete my long run the next week.
This week I did something a little different. Instead of cutting back on the mileage, I kept up with the program. I changed my routes to mostly track workouts. The track was soft and flat, allowing me it still run 4-7 miles with minimal pain. It felt great.
I knew, however, that 4-7 was not what I needed to fear. There was no way I could bring myself to run 14-15 miles on a track. So yesterday, with butterflies in my stomach and a black band around my knee, I set off. I modified my previous long route to avoid any major hills until the last half of the run. My theory was that half way in, I would be far enough from home that it would force me to continue. Well, I did it. I made it over up the hills, and back, passing over 14.5 miles under my Asics.
While I know I still have a long way to go, last night's run was a huge boost to my confidence. I'm back, with 53 days to go.
Thursday, August 13, 2009
Wednesday, August 5, 2009
The Best Mediocre Run Ever
Justin:
So a few days ago I wrote about my worst run ever. Meant to be a 16 mile long run at an 8:30/mile pace it turned out to be a disasterous 14 mile jog featuring a 2 mile walk of shame and a sleepless night of agony. Needless to say, this experience left me dreading my next long run.
Well, after correcting for a few mistakes I managed to kill nearly 17 miles at my target pace of 8:45/mile. First, instead of eating lightly during the previous day, I ate a lot. Second, instead of killing a medium run the previous day, I jogged an easy 3 with a few pushups and situps thrown in the mix. Third, instead of eating lightly the day of the run, I ate and hydrated a lot. Fourth, instead of not hydrating during the run, I broke with principle and purchased a water belt and some Gu. Fifth, instead of over-reaching with an 8:30/mile target, I paced myself and ended up with a (relatively) respectable 8:45 - not great, but not bad given the distance.
These adjustments, common sense to most people, made all the difference in the world! Again, while the pace was nothing to swoon over, I finished and I felt great. As a result, whatever the run may or may not have done for my legs and lungs, it gave me the confidence that I needed to continue with the training schedule. Thus, the moral of the story is, I guess, that we not only have to run hard, we also have to run smart.
So a few days ago I wrote about my worst run ever. Meant to be a 16 mile long run at an 8:30/mile pace it turned out to be a disasterous 14 mile jog featuring a 2 mile walk of shame and a sleepless night of agony. Needless to say, this experience left me dreading my next long run.
Well, after correcting for a few mistakes I managed to kill nearly 17 miles at my target pace of 8:45/mile. First, instead of eating lightly during the previous day, I ate a lot. Second, instead of killing a medium run the previous day, I jogged an easy 3 with a few pushups and situps thrown in the mix. Third, instead of eating lightly the day of the run, I ate and hydrated a lot. Fourth, instead of not hydrating during the run, I broke with principle and purchased a water belt and some Gu. Fifth, instead of over-reaching with an 8:30/mile target, I paced myself and ended up with a (relatively) respectable 8:45 - not great, but not bad given the distance.
These adjustments, common sense to most people, made all the difference in the world! Again, while the pace was nothing to swoon over, I finished and I felt great. As a result, whatever the run may or may not have done for my legs and lungs, it gave me the confidence that I needed to continue with the training schedule. Thus, the moral of the story is, I guess, that we not only have to run hard, we also have to run smart.
A Bit of Inspiration from the New York Times
New York Times Article
Well: The Summer Running Slump
By Tara Parker-Pope
Published: August 4, 2009
Elite running coach Greg McMillan talks about the summer running slump many people experience before the fall marathon season.
Since May 18, the New York Times has been featuring a weekly blog entitled "Time to Train for Your First Marathon." The most recent entry is an inspiring (and timely) piece that deals with "The Summer Running Slump." Enjoy....
http://well.blogs.nytimes.com/2009/08/04/for-runners-losing-motivation-in-the-summer/
Well: The Summer Running Slump
By Tara Parker-Pope
Published: August 4, 2009
Elite running coach Greg McMillan talks about the summer running slump many people experience before the fall marathon season.
Since May 18, the New York Times has been featuring a weekly blog entitled "Time to Train for Your First Marathon." The most recent entry is an inspiring (and timely) piece that deals with "The Summer Running Slump." Enjoy....
http://well.blogs.nytimes.com/2009/08/04/for-runners-losing-motivation-in-the-summer/
Sunday, August 2, 2009
The Worst Run Ever
Justin:
So last week's long run was not only the worst run ever - it was, without exaggerating, one of the worst experiences of my life. It left me physically drained for several days and mentally discouraged. After 2.5 months of steady, if imperfect, training it left me seriously doubting whether I would be able to complete my goal of running the Baltimore Marathon this October. And while I have recovered physically after a week of nearly constant eating and drinking, I have yet to regain my confidence.
So, what happened? Well, the previous week I ran a solid, relatively painless 13-mile long run. While not an impressive distance, it was by at least a mile the farthest I had ever run. Not only that, it left me feeling pretty confident - so confident that I felt ready to bump it up to 16 (my lucky number) the following week.
Too much fun the following Saturday, however, left me feeling dehydrated, groggy, and uninspired for most of Sunday. As a result, I decided to postpone my long run until Monday after work. That said, by Sunday evening I was feeling recovered and restless - so I decided to go for a quick 7.5-miler - very quick as it turned out. I crushed it and it felt awesome.
By the time I got in, cooled down, and cleaned up, however, it was getting late - so I grabbed a quick pb & j sandwich for supper and called it a night. (For those of you keeping score at home, I believe we are at mistake number 3...?)
So the next day after an exceptionally long day at work, having eaten only one meal, I got home and relaxed in front of the tv with a couple of friends until around 8 pm. That's when I decided, my last meal having ended exactly 7 hours prior, to hit the pavement. I was feeling awesome. And while I didn't have any water with me, as I am (unlike my roommate) far too cool to wear either a backpack or belt, I had it all figured out. My plan was simple: instead of hydrating continually throughout the route I was going to run my 7.5-mile route twice, stopping half-way for a drink. Brilliant, no?
No. As it turns out, there were several problems with this plan. First, my 7.5 route is, in my opinion (and you are free judge for yourself), quite difficult. While it features two steep (but relatively short) downslopes, it also features two exceptionally long hills including the nearly 2 mile (and very steep) Embassy Row stretch that runs up Mass Ave from Dupont Circle to the National Cathedral. Moreover, the downhill stretches are almost too steep to be of any benefit.
Second, and probably more importantly, this plan forced me to run the second 7.5 miles on a sip of water. For the last 5-7 miles all I could think about was the giant bottle of icewater that I was going to kill when I got back. For the last 3-5 miles I saw water everywhere - but not a drop to drink. In fact I became so desperate that I nearly stopped another, better prepared, runner and asked them for a sip of water.
So if by now you've concluded that I am an idiot, I'm sure you're not alone. But there's a little more. To add to my already considerable woes, I chugged around 5 glasses of icewater and - due to my considerable (and much-deserved) stomach pains - did not eat all night. This, added to the litany of previous mistakes, made for a very exciting night indeed.
So, as I ponder my next long run - now less than 24 hours away - I wonder, will I be able to finish? What will I be feeling tomorrow at this time? Oh god...why do we do this? Ciao.
So last week's long run was not only the worst run ever - it was, without exaggerating, one of the worst experiences of my life. It left me physically drained for several days and mentally discouraged. After 2.5 months of steady, if imperfect, training it left me seriously doubting whether I would be able to complete my goal of running the Baltimore Marathon this October. And while I have recovered physically after a week of nearly constant eating and drinking, I have yet to regain my confidence.
So, what happened? Well, the previous week I ran a solid, relatively painless 13-mile long run. While not an impressive distance, it was by at least a mile the farthest I had ever run. Not only that, it left me feeling pretty confident - so confident that I felt ready to bump it up to 16 (my lucky number) the following week.
Too much fun the following Saturday, however, left me feeling dehydrated, groggy, and uninspired for most of Sunday. As a result, I decided to postpone my long run until Monday after work. That said, by Sunday evening I was feeling recovered and restless - so I decided to go for a quick 7.5-miler - very quick as it turned out. I crushed it and it felt awesome.
By the time I got in, cooled down, and cleaned up, however, it was getting late - so I grabbed a quick pb & j sandwich for supper and called it a night. (For those of you keeping score at home, I believe we are at mistake number 3...?)
So the next day after an exceptionally long day at work, having eaten only one meal, I got home and relaxed in front of the tv with a couple of friends until around 8 pm. That's when I decided, my last meal having ended exactly 7 hours prior, to hit the pavement. I was feeling awesome. And while I didn't have any water with me, as I am (unlike my roommate) far too cool to wear either a backpack or belt, I had it all figured out. My plan was simple: instead of hydrating continually throughout the route I was going to run my 7.5-mile route twice, stopping half-way for a drink. Brilliant, no?
No. As it turns out, there were several problems with this plan. First, my 7.5 route is, in my opinion (and you are free judge for yourself), quite difficult. While it features two steep (but relatively short) downslopes, it also features two exceptionally long hills including the nearly 2 mile (and very steep) Embassy Row stretch that runs up Mass Ave from Dupont Circle to the National Cathedral. Moreover, the downhill stretches are almost too steep to be of any benefit.
Second, and probably more importantly, this plan forced me to run the second 7.5 miles on a sip of water. For the last 5-7 miles all I could think about was the giant bottle of icewater that I was going to kill when I got back. For the last 3-5 miles I saw water everywhere - but not a drop to drink. In fact I became so desperate that I nearly stopped another, better prepared, runner and asked them for a sip of water.
So if by now you've concluded that I am an idiot, I'm sure you're not alone. But there's a little more. To add to my already considerable woes, I chugged around 5 glasses of icewater and - due to my considerable (and much-deserved) stomach pains - did not eat all night. This, added to the litany of previous mistakes, made for a very exciting night indeed.
So, as I ponder my next long run - now less than 24 hours away - I wonder, will I be able to finish? What will I be feeling tomorrow at this time? Oh god...why do we do this? Ciao.
Monday, July 27, 2009
The Lonely Half Marathon - 13 miles
Doug:
Several years ago my family decided that we should all run a half marathon together, so I signed up for the Rock and Roll Half Marathon in Virginia Beach. That was my first (and only up to this point) long distance race, and I was blown away by the number or supporters lining the entire route. Rock and Roll did a great job filling every mile marker with the bands and cheerleaders. The rhythms and lyrics could be heard a quarter mile away, so very little time on the course was left without sometime to pump you up.
Yesterday I ran that distance again, only this time without all the support. There were no signs telling me to keep going, no cowbells giving me a jolt of energy, and no Bon Jovi cover band as I turned the corner past the 10 mile mark. It was just me, the road, and the knowledge that I'm several miles from home without money or a phone, so I'm left with no choice but to keep running.
But I did it. Maybe a little slower than I had originally set out for, but I left the house towards Dupont and didn't return until I had another 13 miles on those shoes. The fan support and medal at the end sure would have been nice, but my eyes are set on a larger goal. Even if it is a little lonely along the way.
Friday, July 24, 2009
NY Times - "Running in the Rain"
New York Times Article
Running in the Rain
Running in the Rain
A group run with Olympian Deena Kastor made the dampness almost disappear.
http://well.blogs.nytimes.com/2009/06/04/runnin-in-the-rain/
Thursday, July 23, 2009
Caught In The Rain - 5 Miles
Doug:
Tonight I got caught in the rain. I've slacked a little this week, trying to 'let my knees rest', so I was pretty excited to get back out for a run today. I had dinner plans at Gloria's this evening, so I rushed home from work and threw on the shorts. I figured it best to be a little late for dinner, than try to run 5 miles after stuffing myself. Lord knows I can't turn down Gloria's delicious Pupusas. About 3 miles in to the run, I heard a few loud claps of thunder and within seconds the heavens opened up. I'm not sure why, considering the forecast for storms all week, but it really caught me by surprise. Immediately my body perked up and I took off up the hill beside Meridian Park. I don't know if all I needed was a little wake up, or if the fear of the rain ruining my MP3 player took over, but I was booking it back the last few miles.
I guess getting caught in the rain can be a good thing sometimes. Nature's shower sure kept the legs moving.
Subscribe to:
Posts (Atom)
