(First off, Blogger ate this post yesterday)
I started yesterday at 5:05 at the pine swamp. Too swampy. My new headlamp didn’t work. All I saw was fog in all directions. And the swamp was overwhelming the path for the first 1/2 mile, so I quit and turned around.
I went to Maudslay, starting at 6:10. Not bad, but HUUUUUUUMMIIIDDDD. God! It was so miserable that I was sweaty and ruined by the first mile. By the fourth mile, I had NO energy in the tank. I decided to call it quits and left after four miles.
So, cruddy sunday.
And this morning. Ah, yes. Feeling ashamed for missing my 13 miles, I decide to screw my schedule and run a few miles on the treadmill to make up for it. At 1.89 miles, I felt a weird twinge in my back. And then, OW! It was the same “throw my back out” feeling that put me out of business for a week a few years ago, only up higher on my back.
I got off the treadmill, hobbled through cleaning the thing up (because I’d already sweat all over it), and then slowly moved out to my car to head home. I got Kat out of bed and she nursed me through a shower, and then into bed. Thankfully, between six ibuprofin and some really decent home massage, I think we nipped it in the bud. I feel some weird pulls in my back and if I walk certain ways, I feel it more. So what the hell is that?
I’m not sure what I’m going to do differently. I’m going to take today and perhaps tomorrow off, and then see what happens Wednesday. I’m going to revert to fueling up more before my runs (I’d switched to just a few pieces of fruit). I’m going to pray like hell that the twinge was just a whoops. I’m going to re-enter my Core Performance workouts instead of the lighter stuff I was doing. It focuses on core muscle strength and stability, and this twinge is dead center of what core would’ve been working on.
But sheesh. I guess there’s something telling me to slow down a little.
Good news department: a friend is running the same marathon as me this November.
[email]