Cotton Row Run 5K 2013

OK, so all my training, the running and the biking and the treadmill workouts, were for this race, the Cotton Row Run. The 10K started at 7 am. I know me and there is no way I'm going to be on the starting line of any race at 7 am. To be honest, I wouldn't be at the church for my own wedding at 7 am. I am not a morning person and I know this about myself. Thus, I do not commit to running a race that starts at 7 am.  I used to run the Cotton Row 10K back in The Day when it started at 8 am and was the only event, but once they added the 5K they apparently felt obliged to shove the 10K back an hour to 7 am and then start the 5K at 9 am, giving the 10K runners enough time to finish their race and get the heck out of the way for the next one.

So, my running was doing great up until about a month ago. I ran the fastest 5K time I had done in a number of years, but while on a treadmill which enabled me to time it exactly. Still, it was faster than I've been lately. After that, though, I had bad knee pains and was forced to begin biking in order to let my knee recover. When I was able to return to running, I was outside on the pavement. And I was really, really slow. Or at least that's how it felt. I didn't have a clock in front of me to tell me exactly how fast I was going like I do on a treadmill. But it sure felt slow.

For a month straight I did everything in my power to dodge knee injuries and calf injuries and any other injuries that tried to spring up and sabotage my training, all while finding ways to continue to train without stopping.

And then I decided to fartlek. And because I hadn't sprinted in awhile I suppose my calves weren't really ready for it. They felt extremely tight afterwards and I even stopped my workout just to make sure I didn't reinjure either calf.

Last year I had badly injured my left calf while training for this same race. It took forever to get back to a point where I could run again, and even then I had to be VERY careful not to run too fast or I'd reinjure it. This left me running races at a pace that wasn't at all competitive, but was the fastest I could go without blowing my calf again. I ran 2 races that way and it wasn't fun. My times were shameful, but I couldn't do much about it.

So fartleking made my calves tighten up badly. But they weren't injured. My arches in my feet and my calves were both sore for a solid week after. I biked a lot. I ran carefully. Less than a week before my race, I did a slow and careful run, then went home and stretched.

It was while stretching my calves after cautious run that my left calf said, "oh hey, did you feel that? Yeah, I'm hurt again. Booya!"  Yep, my left calf hit me with a distinctive needle-like pain of an injury not while I was running, but while I was home carefully stretching my tight calf muscles after a run. It was just a brief pain, but a distinctly familiar one. And it was 4 days before my race.

I should have iced it right away. But I didn't. I walked around the house carefully feeling out my calf and didn't think it was too bad. It was just a little sore. Maybe I was OK? Just to be sure, I tore the house apart searching for my protective calf sleeves. I knew where they SHOULD be, but when I looked they weren't there. I found the package that they came in, but they were empty. I shouted to no one in particular, "WHY DID I KEEP THE PACKAGE IF I WASN'T GOING TO PUT THE SLEEVES BACK IN THEM?!" And then I resumed my frantic search.

It wasn't until late Friday night, as I was packing for the trip to Huntsville, that I finally found my calf sleeves. I'm ashamed to admit that they were both buried under some crap I'd left in the floor of the bedroom since this time last year, just after the Cotton Row Run 2012. I came home and apparently put my bag of Cotton Row swag in the floor over against the wall, with the calf sleeves inside, and then laid something else on top of the bag and forgotten it.

Saturday came and off to Huntsville I went. I spent 2 days taking it easy and meeting with friends. Then came Memorial Day on Monday and it was race day at last!

9 am Monday morning, there I was standing in a massive crowd of runners. A team of black people all dressed in identical pink uniforms lined up behind me. They kept taking pictures and I couldn't help but notice that I was unintentionally photobombing every single one because I was taller than they were and they had chosen to line up for their photos with me standing right behind them. Hey, not my fault. And anyway, those pictures are probably the only photographic evidence that I was even there.

OK, 10 minutes of blah blah blah while we all stood there, hopping up and down, stretching, flexing, trying desperately to keep our muscles loose and warmed up while one person after another took the microphone and talked or sang or blew a trumpet. And then finally - BANG! The starting gun went off and the race started. There were so many people lined up ahead of me that it took a little bit before I was able to move forward and eventually jog across the starting line and begin the race.

Mile 1 - there was a woman reading off the 1 mile time - 9:27. I didn't feel like I was running very fast, but 9:27 was faster than I expected. Yes, I KNOW that a 9 minute and 27 second first mile is not at all fast by any definition of fast. But it was faster than I felt I was going. So far so good. But I really needed a water station. I didn't get enough water before lining up for the start. My throat was dry and I was really feeling it.

Mile 2 - somewhere along the way I hit a water station. I should have guzzled that whole cup of water, but its hard to swallow a cup filled with water while running and I didn't want to stop just to drink it. So I took a few sips to make my throat feel better and then tossed the cup. I nearly hit someone. "Sorry dude." The skies had been overcast all morning and the 10K race was run under nice cool conditions. Lucky people. But the sun came out in full force just in time for the start of the 5K and I was feeling it. I felt myself slow down considerably for mile 2. I was afraid I was barely moving, but I kept going. At the end of mile 2 someone with a stop watch read out a time of 21 minutes. OK, I had slowed way too much, but overall I was still on track. After last year's worst ever time of nearly 34 minutes I just wanted to get back to my old bad times of under 30 for a 5K. That was my only goal for this year's race. I would run the last mile faster like I usually do and I'd make up that extra time. Everything was fine.

Mile 3 - just after I crossed over the mile 2 point my left calf said "BAM! I'm outta here."  OK, to be fair, my left calf had been steadily complaining to me the entire race. During mile 1 it wasn't so bad. Plus I was distracted with the task of getting my pace established, dodging people who oddly chose to walk right in the middle of the road and block runners, and trying not to fall over children who run up in front of you only to suddenly stop and then randomly begin running again. The pain was there, but very faint. During mile 2 it was worse and I was focusing all my attention on trying not to reinjure it. That was part of the reason I slowed down during mile 2. And now, with 1.1 mile left to go, my calf decided it was done with this race and wasn't going to finish with the rest of me.

Just like last year, I began to limp badly. Just like last year, I wasn't sure if I was going to have to stop and walk or even move to the curb and sit down. Just like last year, I kept limping along trying desperately to work out some of the pain and make my calf loosen up enough to let me finish this race. My limping was pretty extreme.  But after limping for what seemed like an eternity I finally managed to loosen my calf up enough to force myself into a normal stride. I couldn't do anything about my speed. I couldn't afford to speed up. So I just focused on my form and my stride. I tried to run with perfect form, and when that didn't hurt too badly then I slowly began to think about extending my stride a little bit. It was the only way I could make up some time and pick up speed. I couldn't afford to go up on my toes at all, so lengthening my stride was all I could do, just so long as my calf didn't bail on me again.

The last mile of the Cotton Row 5K is annoying, because there is a long stretch that creates the illusion of being the final straightaway. You can see well down the street, and somehow it appears that the end is within sight. But it isn't. It's just a 90 degree right turn down a short street and then another 90 degree left turn onto another street. And THAT street is the final straightaway. And THAT final straightaway is also an illusion, because you can see a big American flag hanging from a metal beam that marks the starting line where we all began. Most races that double back on themselves start and finish at the same point, on the same line. But not this race.

A lot of runners start to speed up on the first false straightaway, only to realize their mistake and almost stop altogether and walk. Others don't fall for the first false straightaway, but turn onto the last stretch and, because they can SEE what appears to be the finish line, they start to give it all they've got. It is a LONG way down that final straightaway before you even reach the original starting line, the false finish. A long, long way. Most people have a 100 meter sprint left in them at the end of a long race. Few people have a 400 meter sprint in them, and even fewer have longer than that. This last stretch of road is well over 400 meters long. The people still running in this race by the time I reach it are not the sort of people who have a 400+ meter sprint in them after running over 2 miles already. Even in my heyday, back when I was running 5Ks in 18 minutes or less, I would speed up a lot for the last mile, but I didn't have a 400-800 meter sprint in me. Those people who turn down the last straightaway and break into a sprint at the sight of the distant starting line die well before the finish, often reduced to walking and losing everything they'd hoped to gain from their sprint.

My calf was not doing well, but it wasn't as bad as it had been earlier when I first pulled up limping. My lengthened strides were working out alright for me. The extreme limping had taken a lot out of me, though, and I didn't have much sprint left in me. I strided down the long, agonizing straightaway until I crossed under the original starting line banner and then I stretched out my stride and gave it all I could with my gimpy calf and my other leg totally worn out from doing all the work while I limped so badly. I looked desperately for the time clock at the finish line as I crossed it. It was there, but it appeared to be turned off. I couldn't see a time at all.

All I had wanted for this year's run was to get back under the horribly embarrassing 30 minute mark. Last year, with absolutely everything going against me, I had the worst run of my entire life, nearly hitting 34 minutes. This year I felt sure I hadn't done as bad as that, but I was afraid that my injury had sabotaged my hopes of getting back under 30. In fact, I was sure of it. Even so, I still wanted to know just what time I had run. Surely it had to be better than last year.

There is a computer chip in our race numbers and it records our time for us. This enables the race coordinators to print out and post times almost immediately. Even so, to me it felt like I waited forever for them to finally post my time. I limped over to the white sheets of computer paper taped to the wall of the Civic Center and made me way through the crowd of runners all searching the pages for their times. It took awhile, but I finally found mine

31 minutes

Ah hell. That limping along easily ate up a minute of my time. It slowed me down so badly. If not for that I'd have made my goal. There was no doubt. So now I have this recurring calf injury to deal with. Two years in a row it has affected my races. It concerns me that it is back a full year later, the exact same injury. I don't want to have to be worrying about this next year when I run this race again. I want to be free to focus on my pace and give it all I've got. I'd like to be able to focus on getting well under the 30 minute mark and start moving to the lower end of the 20s again. But instead I have this to deal with.

I can't help wondering, if only I hadn't run the sprints so close to the race, after not having run sprints for such a very long time, if this wouldn't have happened at all. I don't think running sprints is a bad thing. I think I need to do more of it. I just think my muscles weren't ready for it because I hadn't been doing it consistently and hadn't done it at all in quite a long time. Perhaps, once I have this healed again, I can try to include sprints once a week in my regular workouts and strengthen my weak muscles enough that when this race comes around again next year I won't have to worry about this particular injury again? That would sure be nice. It seems like its been a very long time since I was last able to run a race without any injuries to worry about along the way.

 

Wordless Wednesday

Fartlek, heh heh

I don't know what happened, but a little over a month ago I ran the best 3 plus miles I've done in a very long time. I felt fantastic. But since then, when I moved to running outside on the pavement, I have been trudging along slower than a hybrid car filled with fat people and towing a trailer.

Last night, after a workout of biking for a few miles, I picked up the latest issue of Runner's World. It had an article about preparing for a 5K race, which is exactly what I'm doing. And it talked about the importance of interval training. I haven't done any interval training in a long, long time. It mentioned other options, all intended to increase strength and speed. A series of consecutive 400 meter runs with a small rest between each is apparently considered an excellent way to prepare for a 5K race. And, of course, the ever popular fartlek. 

OK, to be fair, I do fartleks, or used to, a lot. I actually like fartleking. It's a great way to break up a monotonous run.

I also love saying 'fartlek' because it just sounds like 'fart' only it has a legitimate purpose and usage. I can go into an athletic store, such as Fleet Feet, and say fartlek over and over again for an hour straight and no one will think I'm being a total smart ass. But on the inside I'll be giggling like a 12-year-old boy.

I just fartleked

Anyway, back to the topic of Swedish farting and today's workout, I decided last night after reading about the importance of speed work and intervals and fartlek workouts prior to a race that I should make that my workout for today. 

I do not feel like doing this first thing in the morning

When I woke up and headed outside I began having doubts about whether I was making the right decision. I certainly did not feel like doing any sprinting first thing in the morning. I barely felt like running at all. I walked a full mile before I reluctantly broke into a run. I say 'run' but it was more like a trot, a very slow and pathetic trot. I slow pathetic trotted for a half mile before my brain zoned out and I was able to slip into a regular, albeit slow, pace. I jogged for another mile until I came to a straight, flat stretch of road that stays flat and straight for about a quarter mile and then I began my fartleking. heh heh

My attempts at sprinting weren't very impressive. At first I felt like I was going to pull a muscle in my outer thigh and I wasn't even really going that fast. I was just picking my knees up high and springing hard off my toes, but somehow my body seemed to think it was under attack from this and complained. Gradually it seemed like my muscles began to remember what sprinting was all about. They stopped complaining so much and I was able to go faster. 

Repeat

To finish off the workout I fartleked to the bottom of the steepest hill on my course and ran sprints up it repeatedly. I ran about 6 of them. Then I walked home.

Running makes me age backwards, like Benjamin Button

It's funny how I feel so awful when I begin the workout. I feel old and decrepit and tired. The first mile I run I just feel like I'm going to die. But after that, my body steadily remembers that once upon a time I was a real runner and have done this before without dying. By the end of today's workout, after I had run several miles, plus striding out some mild sprints, I actually felt great sprinting up the hill over and over. I wanted to keep doing it, but my calves were threatening to revolt and pull a muscle, so I had to finally stop. I was exhausted when I finished. But I felt a hell of a lot better after all of that running and sprinting than I did when I first headed out from the house to begin. 

I'm thinking of getting a personalized license plate for my car that reads FARTLEK. heh heh

Wordless Wednesday

This is Getting Monotonous

This is jogging?

Monday I went for another run. With my left knee giving me a really bad time my runs have turned into more of a 'run' with the sarcastic single quotes around the word the way the media does when a conservative is being mentioned. I end up walking for a very long way until my knee finally says "OK, I guess I could try running now."

I can't even remember what a good run feels like

But on Monday I was impatient and not in the mood to walk forever, so after about a half mile I broke into a run anyway. It was sort of a "ready or not, let's get it on" sort of thing. I ran slooooow. I mean, it was what people mean when they say 'jogging' instead of "I went running." Does that make sense? My mind was a million miles away and I wasn't paying any attention to my pace. So my pace was slow. On the plus side, because I wasn't paying much attention, I ran much further than I have in at least a month by just zoning out and trotting along. There are a lot of hills out here and I hit them all. Well, up to a point. I could have run farther and hit many more, but I had a set course in mind. I've taken to walking down the steepest hill just as a precaution for my cranky knee.

Gravity running - it still counts

I jogged about 2 1/2 miles before I reached the top of the steepest hill, gasping from the pollen-clogged air which I had been sucking deep into my lungs as I tried to maintain good running form while climbing the hill. I sort of let gravity take me to the bottom on the other side and then trotted a little further. Then stopped and walked the rest of the way home. Somewhere I have a map where I wrote down the distances to various points along my route. I think I was about a half mile from the house when I started to walk.

My foot hurts

Later that night I noticed that my heel was bruised on my left foot. I have no idea how this happened. My running shoes are padded like little foot-shaped pillows under each heel. I've run with far, far less padding in a sole before. I can't imagine how my heel got bruised.

So, with a bruised heel, running on Tuesday seemed like a bad idea. Walking didn't seem much better, either. So out came the bike. I pumped up my tires, which clearly needed air the last time I rode as I could feel the rims of the wheels transferring bumps and ridges up through the bike frame into my butt. And then off I pedaled, into the wild green and asphalt yonder.

My bike is kind of old

It was a decent ride, not fast, but with endless hills I couldn't avoid. By the time I arrived back home again my legs and lower back definitely felt satisfied that they had endured a workout.

Today I woke up and decided to try running again. My heel seemed better and my race is coming up fast. So I went outside, walked even less than I did on Monday, and started jogging. I felt agonizingly slow, which I was, but my goal was to keep going the entire way and cut out more of the walking, so that I started running maybe a quarter mile from home and then planned to stop running the same distance from the house. That would still leave me plenty of distance for a proper cool down.

My knee doesn't feel right

Somewhere around 2 miles my left knee suddenly started complaining. And I do mean suddenly. Everything was fine and then suddenly it wasn't. Ouch! I briefly considered trying to continue on, running through the pain in the hopes that it would go away by itself. But it's less than a month until the race and I remember what happened last year when I tried to run through the pain in my calf. It wrecked my calf and I wasted a race just limping along the entire course afraid to accelerate for fear that I'd reinjure my calf. By the time the main race for the year came along I was still unsure of my calf, although it did ultimately hold up.  So, lesson learned, I stopped and walked.

It even hurt to walk on it. So I walked more carefully. I came to the bottom of the steepest hill and began trying to jog up it. I thought "I'll just stride up this, working on my form, and then stop running again. My knee won't mind that." But it did and I stopped and went back to walking pretty quickly.

My new best friend

I made it home just fine. My knee isn't screaming or swollen or anything. I think I'm going to become addicted to Chrondroitin or however you spell it. I should have taken some before I ran instead of just after, but I didn't. Next time I won't forget.

Back to biking

Anyway, looks like tomorrow its back to the bike. And Friday I have an appointment so I don't know if I'll get to run or bike before breakfast or have to do it after, with food in my stomach. Part of my goal with these terrible runs is to run first thing when I wake up so that my body has no fuel. The theory is that this forces your body to use fat for fuel, which doesn't feel very good, but it helps you lighten up before a race. Of course, if my thyroid is still sabotaging me then all I'm burning is muscle. I need to make an appointment to be retested so the doctor can see if the very weak thyroid medicine they gave me is accomplishing anything.

If you'll throw this ball for me I'll stop chasing you

So, that's my exciting update of my adventures in jogging. No snakes this time, but a big yellow Lab did run out of the yard as if he was going to eat me, only to get right in front of me and wag his tail at me until I reached down and scratched his ears and chest for a bit.  Oh, and a friend sent me a link to a Sprint Triathlon coming up this month. After yesterday's bike ride I don't think I'm up to it. The bike ride in this triathlon is only listed as being 8 miles, but all I'm biking is maybe 3 or 4 and that seems to do a number on me. Apparently I'm still too pathetic to swim, bike 8 miles, and then run 3.1 miles. I still have a lot more work to do just for a tiny little Sprint Tri, which is the shortest triathlon there is.

Pathetic.