Obligatory “year in review” blog post

Doing a “look back on 2009” post seems to be all the rage among running bloggers this month. Although I normally purse my lips in disapproval at such conformity, I’ll jump on the bandwagon.

Now is as good a time as any to reflect upon the past year, which from a marathon racing perspective was a disaster for me. But it was not a disaster in all areas. For one, I ran some stellar races (and workouts) at various points in the winter and spring. I almost ran a stellar 5 mile race in the fall (only to DNF at 3.7 miles with a raging hamstring). And I learned a lot, oh, yes. I learned a lot — about training in general and about myself as a unique physiological running specimen.

Here’s what I learned this year:

  • High mileage results in huge gains for me, but only up to a certain point. If I run high mileage for too long, I will eventually break down in the form of either overtraining or injury.
  • If I have injured myself, I often have a short window of faux-recovery during which I can nevertheless run a spectactular race or speed session (and fool myself into thinking I’m not really injured). But if I continue to run hard after that I will get reinjured.
  • A hot, hilly long run or race will fuck me up for weeks, if not months.
  • Doing a very long and very hilly run at the end of one or two high mileage weeks is dangerous. Depending on how long I’ve been doing high mileage, chances are good that doing one of these will push me over the edge into injury, although it can take anywhere from 7-10 days to develop. Training in Central Park is an especially hazardous prospect in these cases.
  • Extreme changes in weekly mileage are a bad idea. Going from 50 to 95 (even if I’ve recently run 95 without issue) is a great big embossed and monogrammed invitation for Injury to attend my next workout, and perhaps even bring a guest.
  • If I’m feeling very worn down and don’t want to run, I need to take the day off. A few missed runs won’t destroy a season. But too many runs that I shouldn’t have done will.

Bonus realization:

  • My right gracilis muscle does not like running in weather below 20F. My left one, however, is completely okay with this.

The above lessons are hard won. But I won’t soon forget them.

As for what happened in Sacramento two weeks ago, here’s my theory: I suspect that I was undertrained for the marathon specifically. When you look back at my training in the fall, it was constantly being interrupted by one thing or another. First it was a two+ week trip to South Africa, which involved days of travel, a large time zone change, eating and drinking a lot of stuff that isn’t on the menu for marathoners in training, and big time stress in the form of all of the above along with the added treat of being a victim of major property crime. Not to mention some terrible workouts due to poor conditions (brutal heat among them).

Then I came home and had a few good weeks only to experience the first of two serious injuries: hamstring pull followed by inflamed tendon. I didn’t give myself time to heal properly from the first, piling on 95 miles after a 52 mile injured week, and the second injury came in to take its place. All told, injuries screwed up my training for close to a month total. So out of a 13 week schedule (3 of which were taper weeks), at least 6 were heavily compromised. For you mathletes, that’s a screwup factor of 60%.

I toed the line in Folsom thinking that there was a good possibility that I might have to settle for a 3:20 or even a 3:25. I might have been able to make that time somewhere else, but not on that course on that day. The downhills chewed up my quads a la Steamtown and the headwinds were just, wow.

This was all on top of whatever was wrong with me in the spring, which for the sake of simplicity let’s say was overtraining. After an amazingly good buildup from the fall into April, I crashed in May. I was a wreck in June and July, then ran in a holding pattern in August and commenced training in September, as described above.

So that was 2009. Good riddance.

2010 will bring some changes. More on that soon.

Fall Training: Week 12

Training, tapering, whatever. All I know is that the race is now close enough for me to check the weather for race day.

With the exception of a couple of quicker workouts, I’m firmly established in the holding pattern of a pre-race taper. The run on Tuesday, a little under marathon pace, actually didn’t go that well. I was surprisingly slow, owing to a mysteriously high heart rate.

I decided not to waste energy freaking out about it. It’s just one workout, right? I’m chalking it up to possible side effects of the drugs I took for my tendon for a week, plus a few nights’ lousy sleep, as well as my being in the follicular phase, which is typically when I run my worst in longer, sustained-effort workouts.

Friday’s session on the track was a blast. I love short intervals, especially when I’m running well. The hormones were in my favor for this one and my pace vs. effort shows it.

The rest of the week consisted of what I call “toodle along” runs. My legs are starting to feel very fresh and springy now, so it’s been difficult to hold them back from running faster.

The problem left tendon is back to normal in terms of appearance and flexibility, although there’s still some pain if I flex it in an extreme way. But I don’t need to do that for marathon pace running. At this point, I’d be surprised if I’m even aware of it during the race.

I was looking over the women’s results from last year’s CIM and was again reminded of just how competitive a race it is. No AG awards for me this time around, but it does look like I should be able to find plenty of people running my pace, whatever that turns out to be. Interestingly, I do see a lot of positive splits in those results. That may be the case in every marathon (I rarely scrutinize such things), but I’m wondering if the early downhills on the course tempt people to run too fast.

I plan to go very minimalist for this race. I’ll have just two data screens on my watch, each with a single readout: Time of Day (so I know when the race starts) and Heart Rate %. That’s it.

Happy feet

I’ll say it again: cortisone is a fucking miracle drug. 48 hours after the shot into my tendon and the problem is all but gone.

I did my penultimate marathon-y run on the track yesterday: 12 miles with 9 at a few heatbeats below marathon effort. My heart rate during the warmup miles was just way too high — low 70%s for 10:00+ minute miles. Something was off. I suspect it was a combination of lousy night’s sleep, monthly hormonal shenanigans and possibly the effect of being on heavy duty NSAIDs for the past week. Not surprisingly, my speed for the higher effort miles wasn’t anything to write home about either.

I’m not allowing that performance to rattle me. I do know that it’s been very easy for me to run at 85-86% effort for long periods of time (up to 2 hours) and finish up with plenty of energy left over. So I’m confident in my endurance and feel that if I hit things on the right day, my speed will be respectable. I’ve been off the NSAIDs for 24 hours and this morning’s recovery run seem to indicate that things are getting sorted out with regard to energy output vs. speed. I’ve got a little bit of speedwork on Friday, so that should be another checkpoint.

I have a goal time for the race, but I’m not going to share it this time around. There are so many variables and my goals for this race aren’t so much about seeing a particular time on the clock as they are about running at the appropriate effort and managing my energy output. A negative split would be a bonus.

I’ve raced five marathons and four of them have been mediocre to disastrous. What I want most next week is to run a solid, consistent pace — without spending the last 30-45 minutes of the race feeling like I want to die.

Fall Training: Week 11

Interesting week. Not quite the one I wanted. But I’m learning that I can’t control everything, and that can’t be a bad thing.

First side tangent about control: I was reading a book about adventure travel (Robert Young Pelton’s Guide to the World’s Most Dangerous Places) recently. There’s a chapter on adventure racing and it’s noted that marathon runners usually make lousy adventure racers. We’re control freaks, apparently (who knew?). In an adventure race, everything is constantly going wrong and you have to deal with it, adapt and change plans along the way. Compare not having the right flavor of gel to losing two of your kayaks on a four person team, or watching helplessly as all of your camping equipment slips into a deep ice crevasse, and you get the picture.

Second side tangent about control: I’ll preface this paragraph with the caveat that everything I’m about to say is completely speculative in nature; my personal observations and opinions only. This year’s NCAA Cross-Country Championships featured one of the most bizarre races I’ve ever seen. College phenom (and Olympian) Jenny Barringer, initially in the lead, but with Susan Kuijken right on her tail, not only faltered at several times in the race but actually appeared to pass out for a moment. She rallied, but with all those stops along the way ended up way back in the field.

I suspect she had a panic attack midrace (timely, given my recent post). Why? Besides the enormous pressure on her, as the favorite, to win, she just looked uncomfortable from the very start. Kuijken was right behind or alongside her for the start and you could see how aware of her Barringer was. Barringer’s facial expression and physical demeanor changed dramatically in the moment that Kuijken passed her (8:00) and things when rapidly downhill. You could see Barringer, looking distressed, talking to herself. Her form was shot and she didn’t look good. Then, a bit farther along, she wobbled, dropped to her knees, and collapsed (0:54, 1:42).

Where was her coach? Even if it wasn’t a panic attack, she clearly wasn’t in racing shape and belonged in the med tent. Even more disturbing than watching her struggle to her feet to finish the race was that she allowed herself to be interviewed right afterwards. On camera, she was clearly upset and shaken from the experience. I saw her doing everything other than taking care of herself. It struck me as profoundly sad, because she seemed so utterly alone.

Updated: Here’s an extended interview with Barringer after the race in which she discusses the incident and the confluence of pressures, transitions and expectations that may have contributed. I’ve also added links to the video above, along with where you can see the key meltdowns.

Anyway, back to my week. My big run on Sunday of Week 10, as I’d suspected it might, pushed my foot into a whole new world of pain. My ankle and foot also blew up overnight, resembling a Virginia ham. My sports doc couldn’t even determine which tendon was the source of the issue, so I spent the week taking NSAIDs (oral and topical) and the swelling and pain improved enough that I could run easy on the treadmill. My one run outside on Saturday caused the problem tendon to flare up, though, so I went back to my sports med guy yesterday, who (surprise!) gave me a cortisone shot.

Needless to say, I didn’t run my 4 mile race in Central Park on Sunday as that would have qualified as Doing Something Stupid. While I’m disappointed that I didn’t get to try for that first corral bib, I gotta keep my eyes on the prize, which is December 6 in Sacramento. Doc gave me the all clear to run and race as much as I like, starting today, with the warning that my race may hurt a little (and possibly a lot afterwards). But I won’t be doing any further damage to myself by running it.

Ankle and foot look and feel better this morning thanks this miracle drug. I had a planned 12 miler with 9 at just below marathon effort. I’m going to go attempt this on the track right now.

Fall Training: Week 10

09fall-training-10This week started out well but rapidly nosedived as a new injury emerged. On Tuesday, toward the end of a midlength run, the top of my left foot suddenly started hurting. A lot.

With icing it seemed to get better overnight and I felt good enough to go do my tempo run at the track on Wednesday. That went very well until the penultimate fast mile when the pain started to come back. I could still run fast, but it wasn’t a pleasant experience. The recovery run later that day was a bit better and I was encouraged to find that the more I ran, the better the foot felt.

Then on Thursday I did a nine mile recovery run with the same expectation, but ended up with a completely different experience. My foot hurt like hell for the entire run. Aside from one incredibly hot and humid half marathon in which I had a small…um…”accident” in my shorts just past mile 4, these were the longest 9 miles I can recall ever having gritted my teeth through.

After that run the pain started to migrate upward from the top of my foot to the lateral side of my ankle. There was no obvious inflammation, which I suppose was a good sign, although the area was tender.

As much as I hated to do so, I backed off for the rest of Thursday, as well as Friday and Saturday, chopping my mileage by close to 30 miles in the process. I’m upset that it came to this, but what could I do? After Thursday’s sufferfest I felt that running on it further would only delay the process of healing.

Fortunately, I have a stationary bike for just such occasions, so I whaled away on that for a couple of days. At the risk of offending duathletes and triathletes, biking is not that hard. I averaged 16mph at 60-63% MHR with a resistance setting of 5 (on a scale of 1-10). Maybe I need to put these monster legs onto some pedals one day, since I know I’ve got the running nailed.

Last night I did a 20 minute run test on the treadmill, scooting from 11:00 pace down to 8:00, just to see what my tendon would do. It didn’t get worse, which was good enough for me. Hardly the best test, since 20 minutes on a flat treadmill at a slow pace does not equal 20 miles in Central Park at a fast pace.

Since I take some measure of pride in being an honest blogger, even when it makes me look like an idiot (see shorts shitting episode above), I’ll confess that I took a serious painkiller for this run: 500mg of Hydrocodone (prescription only!). I resorted to this measure only because OTC meds had no effect on the pain over the preceding days. I took half one hour before the run and kept the other half in my shorts. I took that at the 13.5 mile mark when my ankle was starting to whine.

I know that it’s generally not a great idea to include narcotics in one’s training plan, for the usual reasons: they mask pain, they can have unpredictable physiological effects when mixed with high effort, one can become overly reliant on them as a “band aid” of sorts, yadda yadda. But I’m a big girl and know the risks. I knew going in that my tendon was inflamed and would hurt. I knew I didn’t have a stress fracture. I knew that 500mg of something in my system during a few faster miles wasn’t going to wreak havoc. I used to be alarmist about such things, but I’m not anymore.

The run went well. I did 5 miles at around 10:00 and then picked it up to average 7:35 per mile 7:50 per mile (I can’t do math properly) for the faster 15. This is a very good decent pace for me in Central Park, which is constant ups and downs. I avoided the huge hills at the top of the park, opting to go clockwise along the 4+ mile “inner loop” (utilizing the two major transverses at 72nd and 102nd streets) for most of the run. It was also around 60F and 92% humidity. Add in that I was running on a bum ankle and I’m happy with today’s performance. I know I worked hard because I came home and slept for 2+ hours.

Random fun facts: I counted four people who were running faster than I was today and they were all guys in their 20s and 30s; that always makes me feel good. Also, there was an ice cream cart on the corner of the 72nd street transverse and West Side Drive, but no one was buying ice cream. I bought one at the end of the run and it took the guy about five minutes to excavate the desired item from the bowels of his cart. I wondered if it had been buried in there since September.

Next week is the transition from training to taper. I’ve got my last speed session (I skipped the one planned for Friday of this week) and a 4 mile race in the park on Sunday, in which I will make my second attempt to garner a NYRR First Corral bib. As for my tendon, regardless of what it does overnight I’ll go see the orthopedist this week for a cortisone shot. It wouldn’t be marathon season without one.

My left foot

Oh, you poor thing.

I know why you’re so unhappy. I forced you to run 18 miles in a newish pair of Adidas Adizero Tempos, which, with their slightly too-narrow toebox, pinched your award-winning bunion. You were also probably working hard to compensate for the right leg’s compromised hamstring.

Then I took you on a 22 mile spin along the Central Park hills despite the fact that you were still iffy in the bunion department. You let your displeasure be known on Tuesday, at mile 11 of a 14 miler, again after numerous ups and downs on the way to White Plains and back. “Here’s a little tendonitis for you,” you muttered ruefully and then added, more ominously, “Or maybe it’s a stress fracture.”

Oh, sure, I made a show of caring about your needs, wrapping you in ice for 20 minutes several times on Tuesday and feeding you horsepill-sized anti-inflammatories. But then what did I do? I frogmarched you to the track on Wednesday morning and forced you to run 6 miles at around 7:10 pace, with another 4.4 miles around those. You did your best, stifling your dismay until the penultimate tempo mile, during which you shouted in no uncertain terms, “No more! Can’t you see I’m in pain?”

Yes, I could. Because you shared your pain. Your pain became my pain. And now we’re in a lot of pain together.

But not so much pain that I didn’t make you run another 4.6 yesterday afternoon, mere hours after our abusive session at the track. Nor did I spare you 9 miles this morning. You’re probably wondering if we have another run later today. I’m not answering that question.

I’m sorry. I’ve given you the painkillers (Hydrocodone) that we save for special occasions. And I’ll offer you more ice throughout the day and evening. Perhaps even some Swedish vodka.

Forgive me.

I’ve seen this sort of thing before

It’s the last month or so before my goal race and, as typically happens, a host of physical issues are suddenly emerging on the horizon like thunderclouds only to recede just as quickly and mysteriously, having spared me from a soaking, or worse, a lightning strike.

Where have I seen this before? Oh, right. During every single previous training season. Looking over my logs of the past few years (you do keep detailed logs, don’t you?), I see that this is something that happens like clockwork in the 4-6 weeks prior to each marathon.

In the spring of 2007, it was chronic shinsplints. In the spring of 2008 it was a torn fascia in my right calf. In the fall of 2008 it was a general malaise that I couldn’t shake for days at a time, almost as if I was on the verge of getting the flu. In the spring of 2009 it was a twofer: a cyst on one of my left foot’s ligaments accompanied by a mysterious pain in my right quads that migrated from quad muscle to quad muscle for a few weeks. (Ironically, the iron/vitamin deficiency and/or overtraining — which eventually did me in — was the one thing I wasn’t accutely aware of.)

This time around is no different, although I’ve learned not to be completely freaked out by each new complaint. Two weeks ago, it was a hamstring pull. Yesterday, it was some sort of odd, painful ligament or tendon issue on the top of my left foot.

I dutifully take my anti-inflammatories, ice and massage the sucker, and hope for the best. If something persists, I go to the orthopedist, who at this point can probably set his watch by my twice-yearly appearances. After a completely unnecessary, “defensive medicine” x-ray, I usually leave with a good dose of cortisone surging through the area in question and a “good luck” on my next race. Did I see him rolling his eyes too?

I’m like a car that starts to belch black smoke from beneath its hood at the tail end of a drive through Death Valley in July. As long as I can make it to Sacramento on December 6 with my radiator, suspension and transmission intact, I’ll be happy.

Fall Training: Week 9

09fall-training-09
This was by far one of my most enjoyable weeks of running in recent memory. I may not be as speedy as I’d like at this point, but I am becoming a stronger runner by the day, or so it seems. Even training with a dodgy hamstring, which was more a slightly worrying nuisance than a hindrance, I felt great this week.

By “stronger” I mean that I am evolving into even more of an endurance machine than I usually am. I can run seemingly forever at a moderate effort, and tacking on high effort miles has been almost easy. I’m also not exhausted after any particular workout or at the end of the week.

I’m not sure how you quantify training progress outside of racing times, but this week of training has me feeling that after two+ years of consistently running high mileage, I’ve finally adjusted to its demands. Almost as if I really do now have a “base” upon which to build further, as opposed to a base that I am working to build.

The highlights for the week, aside from running 95 miles without issue, were Wednesday’s tempo run, Friday’s speedwork, and a monster run in Central Park this morning. Tuesday was no slouch either, with 15 miles at a decent pace for 70% effort.

The tempo run was an experiment in hamstring healing. My ailing leg felt okay, so I decided to try running as far on the track going counterclockwise as I could. That turned out to be 3.5 of the 5 faster miles before the hamstring started to tighten up. So I finished up going the “wrong way” and, aside from the slower, cautious first mile, chalked the run up as a success, given the decent paces.

Another thing about that run: I realized while running my warmup miles on the way to the track that I no longer dread tempo runs beforehand or suffer through them. If anything, they’ve become too easy and I have felt in the past few weeks that the faster blocks are too short. I have said as much to Coach Kevin and he concurs that they are becoming easy for me. So we may schedule longer tempo blocks for the spring cycle.

Friday’s speedwork was worrisome insofar as I didn’t want to screw up my leg and compromise the Sunday run. Still, I was feeling brave, so I decided to once again run in the proper direction on the track and see what the leg would do. It held up well, possibly owing to the fact that I had trouble working up to 92% effort due to fatigue. Still, I’m happy with the splits, considering most of them were run at 91% effort.

I should also note that I only had two days of doubles this week, which is not bad for a 95 mile week. I have observed that I am overall less fatigued in the weeks that I only have one or two days of doubles compared to those in which I have three or four. I don’t know whether it’s a function of age or just my own particular physiology, but I suspect I need 24 hours between runs to recover properly. Fortunately for me, I like running long.

Friday evening and yesterday morning, my legs were completely trashed. Not just my legs, but ankles and feet as well. My confidence in being recovered in time for this morning was shaky, but I’ve learned that miracles can happen overnight.

As it turned out, today’s run was, again, no big deal. I’ve decided to do my final long runs in Central Park so I can get the benefit of the hills there. The California International Marathon course is by no means as hilly as Central Park is, but it does feature a net downhill drop. I’d like to avoid another thigh shredding exercise if I can.

I ran three full loops of the park starting at 72nd St on the west side, along with a 1.5 out and back north, turning around at the 102nd St transverse. Holding effort between 76-79% was easy and I felt energetic enough to run the last mile at 86% just for the hell of it. That got me a 7:26 mile over hills on extremely tired legs. I’ll take it.

Fall Training: Week 8

09fall-training-08This week was a planned recovery week, although it featured exceptionally low mileage due to lingering issues with my hamstring. Interestingly, after watching Paula Radcliffe drop off to fourth place due to a hamstring problem in today’s New York Marathon, I can understand how that happens. It’s possible to run with a problem hamstring, but not as fast as you’d like to. I learned all about this on Friday.

I took Monday off because the hamstring bothered me running. Instead, I took a walk to get the blood flowing to it, then spent some time massaging it to try to head off any scar tissue buildup. On Tuesday I did a little test run in the morning, in which the leg showed improvement, although things were still iffy, so I did another walk in the evening rather than a run.

Wednesday was a turning point, as the leg no longer hurt while walking and I had a lot of range of motion back. It could also tolerate being rolled along the foam roller and massaged fairly aggressively.

I pushed things a bit further on Thursday, with a slightly faster run and an experimental stride at 7:15 pace. There was still some stiffness present, but no pain at that speed. Again, to give it 24 hours rest for the big test on Friday, I cross-trained, this time on the stationary bike.

Friday was the day of reckoning: Could I run fast on the bum leg? The answer turned out to be: well, sort of. But only in a certain direction. I ran to the track and all was well on the way there. Then I started into the tempo work and within half a mile of trying to run fast the leg stiffness evolved into pain. And, like Paula, I couldn’t run fast. The first mile was a disappointing 7:47, owing to my inability to extend my stride with my right leg.

I have no idea why this occured to me, but I thought about the fact that I couldn’t extend my right leg properly and realized that every time I hit a curve on the track I was forcing my right leg to extend further out than my left leg was extending. So, much to the confusion and annoyance of others on the track, I reversed direction for the next three miles and got much better results. At least I was considerate enough to take the extreme outside lane (there’s one guy there sometimes who runs “the wrong way” in the middle lanes and it’s confusing — and probably dangerous — on a track crowded with people).

So I’m not sure whether to call Friday a success or not. I could run fast, but only clockwise on a track. Is that good? Or just necessary for the time being?

For obvious reasons I skipped strides and any speedwork this week. Yesterday was very easy, with another experimental 30 second surge down to 6:40 pace. That speed had my hamstring not so much hurting as tapping me insistently on the shoulder, as if to say, “Uh, what are you doing?”

Fortunately, I knew I wouldn’t get anywhere near 6:40 pace on today’s run (boy was I right about that, as my speed sucked today). But the run today was about endurance and, without making too many excuses, I could still feel Friday’s effort in my legs in addition to having to fight a steady headwind for most of the miles.

I still consider it a successful workout, though. I easily maintained 77-78% effort for 12 miles and then had no problem stepping it up to 88-89% for the last five. I also wasn’t trashed by the workout — no need for naps or other forms of collapse. I credit that more to the lower mileage this week than I do to some leap in fitness.

Toward the end of the run I had matching fatigue and complaints in both hamstrings, which offered some comfort. Although now, six hours later, the right one is definitely complaining slightly more than the left. I have trained injured before, the latest example being the 10 weeks I trained with a mild groin pull, which I suffered on a cold and slippery half marathon in Central Park in January. That was probably worse than what I’m experiencing now (can you hear me rationalizing this away?). But it’s always unnerving to have in the back of my mind, every time I put on my running shoes, the knowledge that something’s not quite right. Kind of like living with faulty wiring and wondering if your house is going to go up in flames at any moment.

New links

I recently updated a few of my links. Yeah, uh, so what, you say? Well, I think a few of them are worth pointing out.

First, I added a link to Run Away Fast, Jaymee Marty’s running blog. Jaymee just took second at the Marine Corps Marathon, three weeks after running a 2:46:26 at Twin Cities. She’s a latecomer to running and to marathoning, as am I, and she’s also part of the over 40 set. She’s currently gearing up for a qualifying run for the 2012 Olympic Marathon Trials in six months. I doubt she’ll have any problems achieving that goal.

I also added links to sites for two runners in trouble. The first, set up to benefit Jenny Crain, has been around for awhile. Jenny was hit by a car while out running in August of 2008 and suffered horrific brain and other physical injuries as a result. The second site deals with Kevin McDermott‘s plight after a recent diving accident left him paralyzed, although he has made astonishing progress in restoring mobility since then.

As a side note, both these runners and their families are struggling to pay medical bills despite having been insured at the time of their accidents. If that isn’t a wake up call to people who for some baffling reason don’t support health care reform, then I don’t know what is.