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.
- 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.