2018 Race Recap #34: CMS 52-Week 5K

How’s that receding hairline treating you there buddy? Photo credit: @ThatKimGordon

Today was a bit of a lark. I wasn’t sure I would actually run the race, but I did have to get my miles in. We have house guests this week, one of whom I’ve been running with: he is into Nordic walking, so while I run, he does his walking and it works out well. Recently, the running club has promoted a “walking” aspect to the race, actively seeking walkers to do a timed walk of the course. He was down with the idea, so he and I went down to Worcester State to do the 5k.

While they’ve been here a few days, I seem to have gained about 5-pounds which is definitely an unhappy development – especially since over that time I’ve run 16 miles. We may have stayed up a bit later last night than would generally be considered appropriate training regimine, and with that in mind I figured today would be a train wreck.

It wasn’t. Well, not really. It still wasn’t great – better than the last time I ran it last month, with the closest comparator being last November’s 24:55 time. It’s 11-seconds faster than last month which is a positive, but in re-reading my description of the race (nagging injury, conditioning) and my action plan (increase mileage, more frequent long runs) I see that really hasn’t done too much – enough to get me 11-seconds, but not much else. I went out HARD in mile 1 – a 7:01 min/mile and despite my best efforts, I realize that was entirely too fast – it was a fast group today, and to my detriment, I tried to keep up with the big dogs. I’m not sure of my actual pacing after that, as my watch lost the satellite connection midway through the second mile and for some reason when it reconnected, it decided that I had run an additional .3 mile. I know about where that happened based on the map it drew, but as far as doing the math to figure out what my actual pace was for that mile, it’s going to be lost to history. But, what I do know the time translates to about an 8:02 pace for the overall race, and given that I know my first mile was 7:01, it’s not really hard to figure out that at least one of the following miles was pretty disgraceful.

It’s not so funny after 3+ miles of that nonsense, now is it? Photo Credit: @thatKimGordon

I have noticed this past month or so running in the heat and humidity — prior to this year its something that to this point I have not done with any consistency either due to injury or motivation — I am a big sweaty mess. Almost as if someone poured a bucket of water over my head. Today, I had to wring out my headband. Just. Gross. I don’t know why this is or if it’s normal to get that disgusting, especially after a short race like a 5k. I don’t know if that’s my body telling me that my conditioning is terrible, or if it’s normal, or what. I do think, though, that it reflects the effort my body is putting out and that it means I’m working far harder (at least on these hot, humid days) than my pace would suggest. So, perhaps come October, when the weather is cooler and far less humid, I’ll be in far better condition to go back to tearing up these races.

Clockwise (last 5):

July 28, 2018: 24:57. Humid, 76. Disgusting swamp weather.
June 16, 2018: 25:08. 75, clear. Beautiful.
February 24, 201824:16. Mid-40’s,  clear
January 27, 201824:24. 34 degrees, sunny. Just beautiful.
January 13, 201825:14   53 degrees, cloudy, 22 mph wind, rainy

Advertisements

2018 Race Recap #27: CMS 52-Week 5k

35405330_10215875835870923_8925447142126911488_n[1]
Like so many other areas of my life.  13th of 25 runners. The low side of average.
Where to begin.  I’ve run this race many times over the last three years, so there’s really not much to describe in terms of the course: start at Worcester State University, run in either clockwise or counter-clockwise direction make a couple of turns, and, depending on the direction you’re running, you finish in front of a bus stop or in front of Aristotle.  Today, it was clockwise which means Aristotle was the finish line.

For what seems like forever at this point, I’ve been battling dents and dings related to running: jacked my piriformis doing the To Hale and Back trail race, tried to push through it at varying intervals, which led to shin splints…both of which reduced the amount of actual running and HIIT bootcamp training I could do so basically despite having had a few decent outings, my conditioning is not what it needs to be.

This is the first time I’ve run this course in this direction since February, when I finished with a 24:16 time.  In February and March, I was really at my peak form: hitting personal best times all over the place and feeling AWE-SOME about the whole thing.  The last few months have really kind of sucked and more and more lately I find myself asking no one in particular when I’m going to feel “good” again. The shin splint comes and goes – kind of like a roommate you don’t particularly like or want around – just long enough to take the wind out of my running sails.  I find myself limping sometimes and I’m not really sure if it’s because my shin actually hurts or because I’ve just become accustomed to it.

It seems disingenuous to say my conditioning is for crap because I’m basically running at the pace I was running most of last year, but I’m certainly not where I was the last time I ran this particular course.

Today was a glorious day outside, perfect weather. Perhaps a touch too much pollen in the air, but then again I’m probably just looking for excuses.  I got a quick warm up run in around the WSU campus.  Running in this direction I will often run as fast as I can the first mile – it’s pretty much downhill – and then find a comfortable pace to latch onto for the final two as there is some gradual elevation gain, but it’s otherwise so flat as to not be noticed.

So the result? About a minute slower than the last time I ran it: twenty seconds a mile.  When written out it doesn’t seem like a lot, but when you’re hauling your butt across 3.1 miles it seems like forever.  Not quite as slow as I ran it in January – by about 7-seconds – but basically it tells me I’ve been shuffled back to where I was 5 months ago.

Time for some more long runs and more frequent longer distances.  This race has a special place in my heart as it was this that gave me the benchmark I needed to see progress when I first started running, it was frequent (and CHEAP!!!) enough that I could keep doing it, and it introduced me to a running community I don’t think I would have kept running without.  That’s why my backsliding hurts so much: it’s literally the benchmark I use for everything else and how I’m feeling about my running condition.

Clockwise (last 5):

June 16, 2018: 25:08. 75, clear. Beautiful.
February 24, 201824:16. Mid-40’s,  clear
January 27, 201824:24. 34 degrees, sunny. Just beautiful.
January 13, 201825:14   53 degrees, cloudy, 22 mph wind, rainy
November 25, 2017: 24:55 Sunny and 28 degrees.