Run: Why you should train smart and not faint
How could anyone ever say that running is boring? So far, my running adventures are full of mishaps, surprises and drama—hilarious drama. Let me bring you all up to date. Try to stay with me because the last parts a doozy.
In April, I made a few summer goals. Although I have not completed them all within the time I allotted myself, I’m doing an okay job of crossing them off slowly. You know how I love lists, and this is quite amazing since, looking back, I set completely arbitrary standards for myself and didn’t take into consideration the science behind training, mileage, injuries and all that jazz. So after going from probably 12-mile weeks to 20-mile weeks over the course of a month or so, lo and behold…. my knees are feeling very angry and resentful.
They were feeling a lot better after the icing, stretching and pouting involved in my group run preparation, and during the run I didn’t feel any pain. So, naturally, I was healed. I did, however, run much faster than I usually do in an attempt to stay with the group... and yet I still was dropped. Fabulous. It was fun anyway. So there’s bad decision number one: increasing speed on a junky knee.
And then came Saturday: long run day. I woke up a little late, but I was determined to get closer to my eight-mile, eventually ten-mile, long run goal. The high on Saturday was 115, and it was probably well over 95 by 7am. From 7-9 am, I drenched myself in water, stayed clear of the stray dog pack and attempted to ignore the knee pain. Seven miles later, (the two hours included a lot of walking as a warm-up and cool-down), I almost fell over when my knee completely gave out. Ouch! I was also close to facing heat exhaustion. I guess I should stop. And how did I recover? Pizza and beer. Bad decision number two.
And then came Monday. After a weekend of celebrating, eating and hours in the sun, I thought it would be a great idea to go on a short run with my cousin around Tempe Town Lake. I didn’t eat dinner the night before, I only got six hours of sleep, and I was feeling extremely dehydrated. So guess what folks? After 15 minutes, I actually fainted! I mean eyes rolled back, cuddling with the pavement and twitching — fainted. The faint occurred after we stopped due to cousin’s side stitch. I suddenly became severely nauseated, had a jolt of pain to my stomach and then everything began to close in on me as I sat down and notified my running partner. Why exactly did I faint? No idea. I felt fine before that.
I’m sure it’s not surprise to the rest of you, but today I’m feeling exhausted, unmotivated, and my knees still hurt. I'm not sure if it's my ITB or what. It hurts on the outside of my knee, but also below my knee cap and on the inside side. Any ideas? Any suggestions? I guess I’m going to have to take a few days off until they feel better. I’ll definitely try to fill my week with cycling, walking, jump roping and maybe even a swim or two. So stay tuned.
Grr, I hate the ten percent rule.