I realized, too late, at work this afternoon that I had drank entirely too much water to be able to successfully complete the 2-mile run I had planned for this afternoon. But this is not actually where this story begins. Back up a few days...
I decided, again too late, this past weekend that I would run my second 5k...leaving myself a very short 2 weeks to prepare for the Jingle Bell Run on December 4th. Still, though, a little more background is needed. Let's back up to this past spring...
That's when I decided to run my first ever 5k. By "first ever" I don't just mean my first organized running event. What I actually mean is the first time I've ever worked towards any physical goal. Ever. In the history of me.
Luckily, I coerced two of my coworkers into joining me in this venture. We worked hard. We trained. We followed a plan that required us to run almost every day of the week. We sweated. Sometimes we missed a few days. We contemplated running twice in one day to make up for it (but, really, who were we kidding?!). A few times we almost vomited. But...WE DID IT! We all ran the entire 3.1 miles without falling, fainting, or just generally having to lie down. And...then we stopped. Well, for the most part. I myself have run sporadically since our race in June. By sporadic, I mean maybe once per week. That is, until this past weekend...
Propelled by an increasing desire to shed the few pounds I gained during our trip to Chicago, as well as a desperate urgency to run another race before 1.) I lose any endurance I have built up from preparing for my first 5k, 2.) it gets entirely too cold for me to run and/or set foot outside at all, 3.) my running buddies also lose enthusiasm, leaving me to sit my butt at home all the time watching HGTV and eating potato chips.
Anyway, back to today. From my [limited] experience, very few things cause me to suffer from the dreaded stitch in my side so much as eating/drinking too soon prior to running. At 3:15 this afternoon (prior to my 4:00 p.m. run) this realization came too little too late, as I chugged down cup number 2 or 3 since lunch! But what could I do at that point? I drove from work over to the trail, warmed myself up with a pep talk, and gave it my best. Which was NOT good enough.
The pain in my side (along with all the water I could feel sloshing in my stomach) began at the 3/4 mile mark. I had to slow to a walk for a few seconds as we turned around at the one mile line. Aaaaaand then again a few minutes later. Thoroughly disappointed in myself (given the short amount of time I have to work up to 3.1 miles), I scolded myself under my breath all the way back to the car. FAIL.
I recharged on the way home with my iPod playing and the sunroof open, on the scenic route, and made a quick run through the grocery store to pick up the things I needed for the Thanksgiving dishes I've been assigned for my various family gatherings. When I finally got home the full moon was bright, the temperature was still 71 degrees, and I felt like a new person. Soooo...I ran again! Not far, mind you. But still...it made me feel better about my poor performance earlier this afternoon.
I have no idea what this will mean for me tomorrow. One struggling run + another shorter, yet more successful one could = soreness and disaster. Of course, the internet is full of a variety of opinions on this topic. Some say two-a-days are the ultimate way to mix-up your routine. Supposedly you burn more calories taking the same workout and breaking it into two segments. Other sources say two-a-days can lead to burnout and overexertion. I seriously doubt that the minimal effort I put into a second run this evening could do much to help or harm me. But, if nothing else, it certainly helped my feelings! I just hope I can walk [and run again] tomorrow!
Q: Are there any actual benefits to two-a-days?
A: I'll let you know tomorrow.
No comments:
Post a Comment