Today's workout (elliptical): 25 minutes
This morning Mark Remy posted a piece on Runner's World about how media covers runners as crime victims or crime discoverers. The key point he makes is that newspapers usually refer to these recreational runners as "joggers" and this insults many runners. Before I stopped posting my daily blog on Runner's World last spring I would occasionally write pieces that I knew would generate lots of comments. The two subjects that I could count on for reaction were treadmill running (love it/hate it) and the terms "jogger" vs. "runner."
I'll admit that I prefer not to be called a jogger. The term seems to diminish the athleticism of the sport. When people call runners "joggers" I assume it's because they know little about running. For me the term jogger evokes a mental picture of an overweight, velour suited, slow moving person wearing tennis shoes and carrying a latte. It's a true cliche and if I wasn't so biased I might concede that it's far better to be that jogger than a person who sits on the sofa all day. Still, I don't want to be that jogger and I don't want anyone to think I'm that jogger.
One of those commenting on Remy's article suggested that a 9:00 pace is the demarcation point between running and jogging. If that's the case, it appears that I often jog without realizing it. It's just a word but it does seem to generate reaction. Next time I'm attacking the rocky slopes and vertical drops at Stillwell Woods at a 9:50 pace I'll take solace in the fact that it's really just jogging.
Friday, December 10, 2010
Thursday, December 9, 2010
23 degrees in the shade
Suddenly it's freezing and at 4:00 AM it's really really freezing. I anticipated those conditions last night and selected the following for this morning's run:
- Wool running socks
- Compression sleeves (ankle to knee)
- Light weight compression shorts
- Mid-weight compression pants
- Long sleeve running shirt
- Short sleeve running shirt
- Winter weight half zip
- Heavy polypropylene running hat
- Running mittens
It may seem like overkill but when I switched on the local news they were reporting temperatures in the low 20's, not counting wind chill. I briefly considered the treadmill but decided that I'd rather have a freezing run than a tedious workout. I set out at an easier pace than yesterday but my many layers allowed me to warm up relatively quickly. Like yesterday, I was pleased with my form and mechanics and I increased my pace as I moved through the run. Between a slower start and a faster finish I averaged 9:16. Much better than the 9:30-9:45 malaise I'd been experiencing over the last few weeks, but after yesterday's 8:44 run I suffered for the difference. I'm still happy with the way I ran and my recent 10K's have convinced me that I can run at slower paces on training runs and still perform well on race day. I have no races on the calendar for the remainder of the year so, for now, I'm going to focus on running for fun, regardless of performance..
- Wool running socks
- Compression sleeves (ankle to knee)
- Light weight compression shorts
- Mid-weight compression pants
- Long sleeve running shirt
- Short sleeve running shirt
- Winter weight half zip
- Heavy polypropylene running hat
- Running mittens
It may seem like overkill but when I switched on the local news they were reporting temperatures in the low 20's, not counting wind chill. I briefly considered the treadmill but decided that I'd rather have a freezing run than a tedious workout. I set out at an easier pace than yesterday but my many layers allowed me to warm up relatively quickly. Like yesterday, I was pleased with my form and mechanics and I increased my pace as I moved through the run. Between a slower start and a faster finish I averaged 9:16. Much better than the 9:30-9:45 malaise I'd been experiencing over the last few weeks, but after yesterday's 8:44 run I suffered for the difference. I'm still happy with the way I ran and my recent 10K's have convinced me that I can run at slower paces on training runs and still perform well on race day. I have no races on the calendar for the remainder of the year so, for now, I'm going to focus on running for fun, regardless of performance..
Wednesday, December 8, 2010
Brisk weather, brisker run
Today's run (street) 2.7 miles
Earlier this week I traded Turkey Trot experiences with my friend CK. He runs the same Thanksgiving day five mile race every year and tries to beat the neighborhood "kids" who are now in their 20's. CK ran that hilly course in 8:20 this year, slower than he'd hoped. I was happy to tell him that I PR'd on the 10K distance and paced under 9:00 per mile. CK said wanted to break eight minutes on his race and I started thinking about what it would have taken for me to do that at Long Beach. For a 10K race (6.2 miles), using my 55:10 time as a benchmark, I would have had to run every mile one minute faster than I did to hit 7:59. Given the difficulty in achieving 8:53 overall, that's a significant challenge. Perhaps breaking 8:40 would be a better target.
This morning I went out with no plans to run fast but when I hit the street everything was working for me. Almost everything, actually, the winds were stiff coming from the north and though I'd dressed for cold the chill and force were a factor. Still, I felt strong and my energy level was greater than it had been in a while. I didn't pay attention to my speed even as I passed the first mile. It wasn't until I passed mile two so quickly that I realized I was pacing far better than usual. I continued to run hard until I reached home and checked the Garmin's readout. Gmaps confirmed the pace: 8:44 per mile. This was the fastest run I've done in a long time. In fact I'll need to look at Garmin Connect to see how long it's been since I've averaged that pace. I don't know how I'll do tomorrow but today I feel good about my abilty to run in the 8:00 range.
Earlier this week I traded Turkey Trot experiences with my friend CK. He runs the same Thanksgiving day five mile race every year and tries to beat the neighborhood "kids" who are now in their 20's. CK ran that hilly course in 8:20 this year, slower than he'd hoped. I was happy to tell him that I PR'd on the 10K distance and paced under 9:00 per mile. CK said wanted to break eight minutes on his race and I started thinking about what it would have taken for me to do that at Long Beach. For a 10K race (6.2 miles), using my 55:10 time as a benchmark, I would have had to run every mile one minute faster than I did to hit 7:59. Given the difficulty in achieving 8:53 overall, that's a significant challenge. Perhaps breaking 8:40 would be a better target.
This morning I went out with no plans to run fast but when I hit the street everything was working for me. Almost everything, actually, the winds were stiff coming from the north and though I'd dressed for cold the chill and force were a factor. Still, I felt strong and my energy level was greater than it had been in a while. I didn't pay attention to my speed even as I passed the first mile. It wasn't until I passed mile two so quickly that I realized I was pacing far better than usual. I continued to run hard until I reached home and checked the Garmin's readout. Gmaps confirmed the pace: 8:44 per mile. This was the fastest run I've done in a long time. In fact I'll need to look at Garmin Connect to see how long it's been since I've averaged that pace. I don't know how I'll do tomorrow but today I feel good about my abilty to run in the 8:00 range.
Tuesday, December 7, 2010
Back on the X1
Today's workout (elliptical): 26 minutes
Despite my bravado about running in the coldest weather I couldn't face the below 20 degree wind chills this morning. It's been at least two weeks since my last elliptical session so I decided to defy convention and use the machine on a scheduled running day. I always go into these sessions thinking I'm due for an easier workout than I'd experienced with an equivalently timed run. By the end I felt like the elliptical matches or even surpasses any run that I do at a moderate pace. The elliptical was a nice change from running and I appreciated a few moments when I listened to music while I worked out, free of any ear buds and free to close my eyes without disastrous results. I'll brave the cold tomorrow for a run and gear up accordingly. I'm hopeful that it will be less windy on Wednesday. Today the elliptical provided just the right workout, all things considered.
Despite my bravado about running in the coldest weather I couldn't face the below 20 degree wind chills this morning. It's been at least two weeks since my last elliptical session so I decided to defy convention and use the machine on a scheduled running day. I always go into these sessions thinking I'm due for an easier workout than I'd experienced with an equivalently timed run. By the end I felt like the elliptical matches or even surpasses any run that I do at a moderate pace. The elliptical was a nice change from running and I appreciated a few moments when I listened to music while I worked out, free of any ear buds and free to close my eyes without disastrous results. I'll brave the cold tomorrow for a run and gear up accordingly. I'm hopeful that it will be less windy on Wednesday. Today the elliptical provided just the right workout, all things considered.
Sunday, December 5, 2010
Seven the hard way at Stillwell
Today's run (Stillwell Woods) 7.2 miles
Due to tight schedules around yesterday's party I had to keep my run fairly short. Today I considered a trip to Bethpage to attempt a long run on the bike trail. The temperature was in the low 20's with the wind chill so I decided instead to head to Stillwell Woods. I figured that the woods would cut the wind and provide better running conditions than Bethpage. Plus Stillwell is closer and I get in for free.
I parked close to Southwoods Road, purposely locating my car as far from the trail head as I could. I figured I'd add some extra distance by running the quarter mile road along the way to the woods. I felt strong winds at my back and looked forward to warming up further as I ran. I followed my usual loops through Stillwell. After two years I know some trails well enough to run with confidence. That's what I thought anyway. I was moving along, feeling good, and after four miles I varied my route and cut through the southern part of the woods that led me back to the main trail. At that point I was feeling like I'd mastered the geography of Stillwell and despite choosing paths that had many gradual inclines I felt strong. I decided to run for a couple more miles and restarted my usual loop, but at the six mile point I found my way into unfamiliar territory. With only the sun to guide me I followed trails that I thought would bring me back to my starting point.
It may have been the slight anxiety that comes from being lost or the fact that I encountered some steeper rises but I began to feel tired and frustrated by the lack of directional context. Maintaining my sun-based navigation method I eventually came to a path that I recognized and I followed it west until I reached the playing fields at Stillwell. From there I ran straight across in a beeline to my car. The freezing winds hitting me head-on were brutal and that last quarter mile seemed to take a very long time. I quickly got into my car and downed an electrolyte drink, sweating and freezing at the same time. I was happy to have covered over 7 miles today, bringing my weekend total to almost 12. I guess I'll have to wait another day to run 10. Seven in the woods was plenty hard today.
Due to tight schedules around yesterday's party I had to keep my run fairly short. Today I considered a trip to Bethpage to attempt a long run on the bike trail. The temperature was in the low 20's with the wind chill so I decided instead to head to Stillwell Woods. I figured that the woods would cut the wind and provide better running conditions than Bethpage. Plus Stillwell is closer and I get in for free.
I parked close to Southwoods Road, purposely locating my car as far from the trail head as I could. I figured I'd add some extra distance by running the quarter mile road along the way to the woods. I felt strong winds at my back and looked forward to warming up further as I ran. I followed my usual loops through Stillwell. After two years I know some trails well enough to run with confidence. That's what I thought anyway. I was moving along, feeling good, and after four miles I varied my route and cut through the southern part of the woods that led me back to the main trail. At that point I was feeling like I'd mastered the geography of Stillwell and despite choosing paths that had many gradual inclines I felt strong. I decided to run for a couple more miles and restarted my usual loop, but at the six mile point I found my way into unfamiliar territory. With only the sun to guide me I followed trails that I thought would bring me back to my starting point.
It may have been the slight anxiety that comes from being lost or the fact that I encountered some steeper rises but I began to feel tired and frustrated by the lack of directional context. Maintaining my sun-based navigation method I eventually came to a path that I recognized and I followed it west until I reached the playing fields at Stillwell. From there I ran straight across in a beeline to my car. The freezing winds hitting me head-on were brutal and that last quarter mile seemed to take a very long time. I quickly got into my car and downed an electrolyte drink, sweating and freezing at the same time. I was happy to have covered over 7 miles today, bringing my weekend total to almost 12. I guess I'll have to wait another day to run 10. Seven in the woods was plenty hard today.
Labels:
challenge,
cold,
direction,
navigation,
Stillwell Woods
Saturday, December 4, 2010
First run, then party
Today's run (mixed surfaces): 4.25 miles
It had been a very busy work week and it seemed to take a long time for the weekend to arrive. Today is also a busy day and it's going to get busier. We're hosting our annual holiday party that will start in the early afternoon. Final preparations are going on although most things are done. Happily, my wife doesn't leave too much for the last minute. I took the opportunity to go out for a four mile run around the neighborhood this morning before I prepared for the day. I began by heading north and following the perimeter road that runs west. A good part of that road is downhill but most of the benefit that's gained through gravity was countered by stiff wins blowing east. After about a mile I headed south along another busy road whose sidewalks are covered with layers of dried leaves. I normally enjoy running on this type of surface because it's softer than pavement but the depth of leaves made the terrain unstable and I was concerned about slipping. I ran slowly and carefully through this stretch.
I turned into the neighborhood at the south end and began to follow most of my usual roads. At the 20 minute mark I looked at the Garmin and saw that I was running at about 9:55 per mile. I figured out later that the calibration on the foot-pod was off and I was actually running faster but my reaction was to pick up my speed for the second two miles. I ended up with an overall pace of 9:40. I thought that was okay considering my slow start and the slower speed I maintained when running on the leafy sections. Today's run felt good and I know I could have gone on for a lot longer but I'm on a schedule today. Pretty soon our guests will be arriving. If all stays on plan I'll get out for a true long run on Sunday.
It had been a very busy work week and it seemed to take a long time for the weekend to arrive. Today is also a busy day and it's going to get busier. We're hosting our annual holiday party that will start in the early afternoon. Final preparations are going on although most things are done. Happily, my wife doesn't leave too much for the last minute. I took the opportunity to go out for a four mile run around the neighborhood this morning before I prepared for the day. I began by heading north and following the perimeter road that runs west. A good part of that road is downhill but most of the benefit that's gained through gravity was countered by stiff wins blowing east. After about a mile I headed south along another busy road whose sidewalks are covered with layers of dried leaves. I normally enjoy running on this type of surface because it's softer than pavement but the depth of leaves made the terrain unstable and I was concerned about slipping. I ran slowly and carefully through this stretch.
I turned into the neighborhood at the south end and began to follow most of my usual roads. At the 20 minute mark I looked at the Garmin and saw that I was running at about 9:55 per mile. I figured out later that the calibration on the foot-pod was off and I was actually running faster but my reaction was to pick up my speed for the second two miles. I ended up with an overall pace of 9:40. I thought that was okay considering my slow start and the slower speed I maintained when running on the leafy sections. Today's run felt good and I know I could have gone on for a lot longer but I'm on a schedule today. Pretty soon our guests will be arriving. If all stays on plan I'll get out for a true long run on Sunday.
Friday, December 3, 2010
What's behind a default running pace?
Today's run (street) 2.5 miles
Paces are a funny thing. I often find it difficult to gauge my speed as I run. There's a default pace that I maintain when I'm not thinking about performance. That's usually my starting point for taking it up a notch in a tempo run or slowing down to conserve energy on a longer run. I'm still not sure why my stride and cadence always seem to lock in around 9:30 per mile. Why not 9:00 or 8:30? When I run I sometimes imagine that I'm in a race with other runners. I do this because in races my pace usually drops into the 8:00 range. The theory is good but the practice is usually unsuccessful. Just imagining competition doesn't seem to help my performance. I'm sure there's much more to it than simply having others (real or imagined) by your side.
This morning I took off on a very cold morning with no regard to my speed. When my Garmin chirped at the first mile I looked at the watch to see that I'd paced it at 10:06. This was a surprise and even a shock because I'd felt like I was moving faster than that. I picked things up and by the 1.5 mile mark I was running closer to 9:40 per mile. Still not fast but definitely faster. I wasn't thinking about my speed but I was concentrating on where my feet were landing. My average cadence has increased about 3% since last year which I thought should yield faster paces overall.
I think my focus on mid-foot landing might actually be preventing progress on speed because, while my steps per minute may have increased, my stride length has probably decreased. I'm okay with that because as I build my base I'm expecting to continue increasing cadence to the point where my speed does increase. Since I can rarely tell how fast I'm actually running I should probably look more often at my watch to see how I'm performing. I've always resisted that because I don't like the pressure to maintain a specific speed. I guess I need to decide what's most important.
Paces are a funny thing. I often find it difficult to gauge my speed as I run. There's a default pace that I maintain when I'm not thinking about performance. That's usually my starting point for taking it up a notch in a tempo run or slowing down to conserve energy on a longer run. I'm still not sure why my stride and cadence always seem to lock in around 9:30 per mile. Why not 9:00 or 8:30? When I run I sometimes imagine that I'm in a race with other runners. I do this because in races my pace usually drops into the 8:00 range. The theory is good but the practice is usually unsuccessful. Just imagining competition doesn't seem to help my performance. I'm sure there's much more to it than simply having others (real or imagined) by your side.
This morning I took off on a very cold morning with no regard to my speed. When my Garmin chirped at the first mile I looked at the watch to see that I'd paced it at 10:06. This was a surprise and even a shock because I'd felt like I was moving faster than that. I picked things up and by the 1.5 mile mark I was running closer to 9:40 per mile. Still not fast but definitely faster. I wasn't thinking about my speed but I was concentrating on where my feet were landing. My average cadence has increased about 3% since last year which I thought should yield faster paces overall.
I think my focus on mid-foot landing might actually be preventing progress on speed because, while my steps per minute may have increased, my stride length has probably decreased. I'm okay with that because as I build my base I'm expecting to continue increasing cadence to the point where my speed does increase. Since I can rarely tell how fast I'm actually running I should probably look more often at my watch to see how I'm performing. I've always resisted that because I don't like the pressure to maintain a specific speed. I guess I need to decide what's most important.
Labels:
cadence,
mid-foot,
pace,
performance,
speed
Thursday, December 2, 2010
The important thing is that I ran
Today's run (street): 2.35 miles
One interesting thing about running at 4:00 AM is how the workout connects to the day ahead. The run itself can determine what type of day I'll have. A particularly good performance or a positive experience can carry far into the day. Regardless of how I've run, whenever I return to my driveway I always think "If nothing else, at least I accomplished this today." My wife shares the same perspective about her daily treadmill runs. Besides the convenience of getting it out of the way early, morning runs provide a great platform for managing whatever comes later in the day.
This morning's run was not remarkable in any way although it felt tougher than some. My energy band is highest before noon but at 4:00 AM it's sometimes a case of the spirit being willing but the flesh remaining weak. After the transition to aerobic breathing I got into rhythm but it wasn't one of my stronger efforts. The local weather report said 39 degrees but it felt colder, even with two layers of running shirts. I tracked a somewhat random course and made it back to the house close to schedule despite starting a couple of minutes later than planned. I'm glad to get that run in since I decided to take a day off from running (and blogging) on Wednesday. The weekend is almost here. I may try again to achieve a distance record on one of those days.
One interesting thing about running at 4:00 AM is how the workout connects to the day ahead. The run itself can determine what type of day I'll have. A particularly good performance or a positive experience can carry far into the day. Regardless of how I've run, whenever I return to my driveway I always think "If nothing else, at least I accomplished this today." My wife shares the same perspective about her daily treadmill runs. Besides the convenience of getting it out of the way early, morning runs provide a great platform for managing whatever comes later in the day.
This morning's run was not remarkable in any way although it felt tougher than some. My energy band is highest before noon but at 4:00 AM it's sometimes a case of the spirit being willing but the flesh remaining weak. After the transition to aerobic breathing I got into rhythm but it wasn't one of my stronger efforts. The local weather report said 39 degrees but it felt colder, even with two layers of running shirts. I tracked a somewhat random course and made it back to the house close to schedule despite starting a couple of minutes later than planned. I'm glad to get that run in since I decided to take a day off from running (and blogging) on Wednesday. The weekend is almost here. I may try again to achieve a distance record on one of those days.
Tuesday, November 30, 2010
Some new perspective on performance goals
Today's run (street): 2.75 miles
I've been thinking about my running focus for 2011 and my goals for next year. I'd like to increase the length of my runs and also work on tactical performance. In terms of distance, I've been averaging between 6 and 7 miles for my weekly "long" runs and in the last month I've done some runs exceeding 8 miles. Lately my weekend distances have been closer to six miles due to my running 10K's twice in November. My hope is to soon cover more distance than that - 9 or 10 miles - as often as I can. The toughest part of that is finding the time to run for 90+ minutes and to find interesting routes that provide enough distance.
In terms of tactical performance, I've thought about the way I've trained over the last month, with easy runs at easy paces preparing for races where I go all-out. It seems to be working. My average training runs have been on the middle and high side of 9:00 per miles but I've managed 9:05 and 8:53 respectively on my recent 10K's. I'd like to continue the easy runs (like this morning's steady run at 9:30/mile) but in place of races (I'm not sure if I'll compete again this year) I might try some "Run as fast as you can for two miles" workouts. Rather than suffering the complexities of speed drills I'm thinking this might accomplish the mission of recruiting fast twitch muscles along with the slow. I'm going to make it a goal to run two miles under 8:00 per mile. That seems like a challenging but viable goal. Right now I'm not sure I can break 8:00 for one mile although my experience at the Long Beach 10K tells me I'm close.
I've been thinking about my running focus for 2011 and my goals for next year. I'd like to increase the length of my runs and also work on tactical performance. In terms of distance, I've been averaging between 6 and 7 miles for my weekly "long" runs and in the last month I've done some runs exceeding 8 miles. Lately my weekend distances have been closer to six miles due to my running 10K's twice in November. My hope is to soon cover more distance than that - 9 or 10 miles - as often as I can. The toughest part of that is finding the time to run for 90+ minutes and to find interesting routes that provide enough distance.
In terms of tactical performance, I've thought about the way I've trained over the last month, with easy runs at easy paces preparing for races where I go all-out. It seems to be working. My average training runs have been on the middle and high side of 9:00 per miles but I've managed 9:05 and 8:53 respectively on my recent 10K's. I'd like to continue the easy runs (like this morning's steady run at 9:30/mile) but in place of races (I'm not sure if I'll compete again this year) I might try some "Run as fast as you can for two miles" workouts. Rather than suffering the complexities of speed drills I'm thinking this might accomplish the mission of recruiting fast twitch muscles along with the slow. I'm going to make it a goal to run two miles under 8:00 per mile. That seems like a challenging but viable goal. Right now I'm not sure I can break 8:00 for one mile although my experience at the Long Beach 10K tells me I'm close.
Monday, November 29, 2010
Minimalist running shoes, one year later
Mizuno Wave Universe 3 |
Brooks Green Silence |
NB Minimus |
Brooks has just launched the GTS 11's that are supposed to be even better than the 10's but, surprisingly, I'm not that interested. The higher heel of conventionally constructed shoes don't feel as good as they did prior to my running in the Kinvaras. I think that when my Saucony's wear out I'll either replace them with another pair, try the Green Silence or go super minimal with the Mizuno Wave Universe (3.8 oz. per shoe). Saucony just announced the Mirage, sort of a Kinvara for people who need stability and New Balance will soon have the Minimus based on the Vibram Five Fingers. So many choices now. I like this type of problem.
The Saucony Kinvara - my go-to shoe |
Sunday, November 28, 2010
Six good miles and one hurting shin
Today's run (street): 6.07 miles
Every time I have a bad run I fear that I'll never run well again. After yesterday's difficult time at Stillwell Woods I questioned whether it would make better sense to take two days off and resume my training on Tuesday. I've been away from the office for three days and while I've run each day I haven't really covered much distance. I wanted to reach 20 miles this week so I planned to go out for 5 miles that would get me to that number. It was 29 degrees on Long Island so I wore a light short sleeved running shirt under a Columbia long sleeve jersey and together they provided a perfect combination of warmth and wicking for that temperature. I followed a different set of roads than I normally do and before I knew it I had covered 2.5 miles and was feeling good. However, I began to notice some pain in my left shin. This may be a shin splint - I'm happy to say I've never experienced one before - but the pain was not intense and I didn't feel like I was doing any damage if I continued to run.
I shaped my route so that I would return to my house after 5 miles but I felt strong and continued on, following an extra loop that put my total at 6 miles. I'm icing my shin in hopes of heading off further troubles. I'm puzzled as to why I would develop this problem this week but you never know how these things start. I'll be watching this injury closely and perhaps take an extra day of rest this week. For now I'm pleased with my run today, especially after yesterday's bad experience.
Every time I have a bad run I fear that I'll never run well again. After yesterday's difficult time at Stillwell Woods I questioned whether it would make better sense to take two days off and resume my training on Tuesday. I've been away from the office for three days and while I've run each day I haven't really covered much distance. I wanted to reach 20 miles this week so I planned to go out for 5 miles that would get me to that number. It was 29 degrees on Long Island so I wore a light short sleeved running shirt under a Columbia long sleeve jersey and together they provided a perfect combination of warmth and wicking for that temperature. I followed a different set of roads than I normally do and before I knew it I had covered 2.5 miles and was feeling good. However, I began to notice some pain in my left shin. This may be a shin splint - I'm happy to say I've never experienced one before - but the pain was not intense and I didn't feel like I was doing any damage if I continued to run.
I shaped my route so that I would return to my house after 5 miles but I felt strong and continued on, following an extra loop that put my total at 6 miles. I'm icing my shin in hopes of heading off further troubles. I'm puzzled as to why I would develop this problem this week but you never know how these things start. I'll be watching this injury closely and perhaps take an extra day of rest this week. For now I'm pleased with my run today, especially after yesterday's bad experience.
Saturday, November 27, 2010
Tough connexin at Stillwell Woods
Electrolytes delivered painfully |
I was on the fence about running this morning. It's been busy week between Thanksgiving related activities and seeing friends. I'd run every day since Tuesday including Thursday's 5K. I talked all morning about whether I should go for a trail run or take a rest day. After lunch I was still talking about it and my exasperated wife finally said "Oh, just get into your running clothes and go for a run!" I had received a sample package of Sport Connexin electrolyte capsules in the mail this morning that I'd agreed to try. I took three before my run, per the directions, and headed over Stillwell Woods.
I'll start by saying that I had a bad run and I'm not sure why. It could have been due to over training this week, running after a big lunch, the electrolyte supplement or a combination of all three. I followed my usual route into the main woods and quickly came upon markings for tomorrow's Rob's Run, a 5K XC race that is held there each November. I've already raced three times this month, including two Turkey Trots, so I decided to forgo Rob's Run even though it happens so close to home. As I made my way along the course I felt far more tired at the one mile mark than I thought I should. My legs felt heavy and the supplements, that contain calcium, magnesium, zinc, potassium, and sodium, were backing up on me and providing a burning sensation in my throat and nose that reminded me of the effects from a highly carbonated beverage. Not pleasant. It may have been because two ingredients (potassium and sodium) are supplied as bicarbonates that may have reacted to stomach acids. No matter what I'm not going to use them again before a run.
By the time I reached the two mile mark I decided to continue only one more mile before calling it a workout. I'm still planning a long distance run tomorrow and I didn't want to push myself when I felt below par today. I may have been better off skipping today's run but you never know how things will go until you try. Hoping for a better experience tomorrow...
Labels:
electrolytes,
performance,
Sport Connexin,
Stillwell Woods
Subscribe to:
Posts (Atom)