One running challenge down, one still left to go. (I haven't gotten my final holiday running streak effort in yet, but I will after I post this!)
I wrapped up my 2012 running season with two very cold and shockingly, nauseatingly fast miles on New Year's Eve. That put me at 931 for the entire year, running and walking.
The night before that — New Year's Eve Eve — I went ice skating at Brenton Plaza with two good friends, one of whom is a natural athlete and the other of whom is, well, more like me. (However she can swim laps around the two of us, so it evens out.)
As natural athlete friend outpaced the two of us who were clinging desperately to the handrail, I found myself thinking: "This was an ill-advised decision for a runner who's just days from completing two challenges she's worked fairly diligently on ... "
But as I found my stride and completed a loop or two, I tried desperately not to jinx myself with thoughts of "wow, I haven't wiped out yet!" but rather "I wonder how far each loop is" and "Does this count toward my run streak?"
It was facetious, sort of; I'd argue that skating is more worthy of being counted than biking, which I definitely saw people doing and definitely am not bitter about.
Thinking back on it post-challenge, however, makes me vaguely nostalgic, because it's emblematic of 2012 for me: I spent the year focusing on mileage, asking my companions "How far do you think we walked around [insert outdoor event or city]?", re-creating the hike from Ogilvie Transportation Center to Chicago tourist attractions on MapMyRun, live-tracking a midparty liquor quest.
Can I quit measuring any move of significance, cold turkey? Can I stop demanding that someone else uncork wine because, after all, I walked 1.7 miles to get that wine to share with her?
I should probably say yes to the latter and no to the former. The race against the calendar lit a fire under me to keep active this year, but the takeaway — for a nonwinner — was ultimately a helpful reminder that the walking miles add up in an important way for fitness purposes.
But first comes a well-deserved and much-needed period of inactivity. That will be the true judge of how deeply the fitness-tracking bug bit me.
Showing posts with label Rock River 1000 Mile Challenge. Show all posts
Showing posts with label Rock River 1000 Mile Challenge. Show all posts
Tuesday, January 1, 2013
Tuesday, December 18, 2012
I ran/walked 900 miles this year, no big deal
With two weeks left in the year, I reached my downwardly revised goal of 900 miles for the year.
I was at 894.74 through Sunday, so Monday — my day off — seemed to be a good time to cross that line. So after much trial-and-error in planning a long-enough route, I got myself out the door, onto the trail and across the 900-mile marker.
It was just like any other unremarkable milestone (turning 20, turning 25, reaching 100,000 on your car's odometer, etc.), in that it happened without fanfare. Heading in, I'd felt like maybe a sparkler should go off.
It didn't. I knew I'd achieved the goal, but I didn't spend much time congratulating myself on it — one text, only because someone else had texted me good news before; one brag on Daily Mile. Mostly I wondered: What's next? That is, how much closer can I get to 1,000 before 2013?
Poor 900. First it was a consolation prize, now it's a stepping stone. My gaze has moved on to 925 ...
I was at 894.74 through Sunday, so Monday — my day off — seemed to be a good time to cross that line. So after much trial-and-error in planning a long-enough route, I got myself out the door, onto the trail and across the 900-mile marker.
It was just like any other unremarkable milestone (turning 20, turning 25, reaching 100,000 on your car's odometer, etc.), in that it happened without fanfare. Heading in, I'd felt like maybe a sparkler should go off.
It didn't. I knew I'd achieved the goal, but I didn't spend much time congratulating myself on it — one text, only because someone else had texted me good news before; one brag on Daily Mile. Mostly I wondered: What's next? That is, how much closer can I get to 1,000 before 2013?
Poor 900. First it was a consolation prize, now it's a stepping stone. My gaze has moved on to 925 ...
Monday, December 3, 2012
My 11th check-in on the Rock River 1000 Mile Challenge
The last month of the Rock River 1000 Mile Challenge should be the easiest, thanks to the Runner's World Holiday Run Streak — I'll have double the guilt trip to put the running shoes on and get going.
Where I stood as the calendar page flipped: about 855 miles. I'd hoped to finish November at a point where a single mile per day would get me to 900; instead, it'll take 1.5 miles a day to get there.
I'm not worried, though. I'll still break 900. And the challenge's full name on Daily Mile starts with "everyone wins." So being a member of the generation that proudly displays its participation awards, I'm perfectly happy with just having joined a challenge.
On a less sarcastic note, my old running buddy and supporter Doug finished November by truly winning the 1000 Mile Challenge: 1,002 miles achieved on Friday. There were injuries and training readjustments along the way, if I recall correctly, which makes it even more awesome. Way to go, Doug!
Where I stood as the calendar page flipped: about 855 miles. I'd hoped to finish November at a point where a single mile per day would get me to 900; instead, it'll take 1.5 miles a day to get there.
I'm not worried, though. I'll still break 900. And the challenge's full name on Daily Mile starts with "everyone wins." So being a member of the generation that proudly displays its participation awards, I'm perfectly happy with just having joined a challenge.
On a less sarcastic note, my old running buddy and supporter Doug finished November by truly winning the 1000 Mile Challenge: 1,002 miles achieved on Friday. There were injuries and training readjustments along the way, if I recall correctly, which makes it even more awesome. Way to go, Doug!
Sunday, December 2, 2012
Attempting a 2012 goal for the first time since February
Throughout the Holiday Run Streak – now at 11, assuming (safely) that I run today — I've thought to myself: "At least one of the single-mile runs I do should be fast." While I have no qualms about using one slow mile as a stand-in for a rest day, I don't want to baby myself, either.
Yesterday was my first such attempt. Having been out late the night before, my hopes were not high. I knew that, with moderate effort, I could most likely finish in less than nine minutes, though.
Off I went. The first quarter-mile, I succeeded in keeping the pace I do on my faster intervals. The wind and the yogurt I'd eaten pre-run were mostly vague irritants more than hindrances.
As I've mentioned before, in my four years of running, I still haven't nailed "don't go out too fast and totally wipe yourself out." During the second quarter-mile, I felt cautiously optimistic that this was a good pacing day; I wasn't going to sustain this pace for 5K, but it was comfortably hard rather than excruciating.
I turned around at the half-mile mark. No surprise, then, that my legs felt the heaviest during the third quarter-mile. My lungs weren't exactly happy with me, either. However, my ego was doing just fine, having seen that I'd done a little over a half-mile in 4:10. The very likely positive split wouldn't keep me from finishing under 9:00.
The desire to get this over with powered me through the final quarter-mile. I've found "you can do anything for two minutes" to be a pretty powerful positive self-talk, so I went to that well almost nonstop during the final 0.25. I was sucking air fairly hard, but even worse was how the morning's yogurt and the previous night's alcohol were sloshing around in my stomach.
Finally I hit 1.00. My time? 7:57.
Let me repeat: 7:57.
Back in February, I'd set three running goals for myself: finish the Rock River 1000 Mile Challenge, run a mile in 8:00 and average a 9:00 pace for a 5K (which I'd forgotten about, until re-reading my blog post).
At the time, I'm sure I expected to succeed in the first and fail at the second two. But as it stands right now, I've missed the first and nailed the second two. (Remember the Remembrance Run 5K?)
Plus, I've done more than survive the two speed challenges. I've finished maybe not with a smile, but with a great rush of endorphins and that ridiculous feeling that I can do anything once I get into some dry clothes and chug a big glass of water.
I'm still pinching myself: 7:57. I hope my gym teachers are reading this.
Yesterday was my first such attempt. Having been out late the night before, my hopes were not high. I knew that, with moderate effort, I could most likely finish in less than nine minutes, though.
Off I went. The first quarter-mile, I succeeded in keeping the pace I do on my faster intervals. The wind and the yogurt I'd eaten pre-run were mostly vague irritants more than hindrances.
As I've mentioned before, in my four years of running, I still haven't nailed "don't go out too fast and totally wipe yourself out." During the second quarter-mile, I felt cautiously optimistic that this was a good pacing day; I wasn't going to sustain this pace for 5K, but it was comfortably hard rather than excruciating.
I turned around at the half-mile mark. No surprise, then, that my legs felt the heaviest during the third quarter-mile. My lungs weren't exactly happy with me, either. However, my ego was doing just fine, having seen that I'd done a little over a half-mile in 4:10. The very likely positive split wouldn't keep me from finishing under 9:00.
The desire to get this over with powered me through the final quarter-mile. I've found "you can do anything for two minutes" to be a pretty powerful positive self-talk, so I went to that well almost nonstop during the final 0.25. I was sucking air fairly hard, but even worse was how the morning's yogurt and the previous night's alcohol were sloshing around in my stomach.
Finally I hit 1.00. My time? 7:57.
Let me repeat: 7:57.
Back in February, I'd set three running goals for myself: finish the Rock River 1000 Mile Challenge, run a mile in 8:00 and average a 9:00 pace for a 5K (which I'd forgotten about, until re-reading my blog post).
At the time, I'm sure I expected to succeed in the first and fail at the second two. But as it stands right now, I've missed the first and nailed the second two. (Remember the Remembrance Run 5K?)
Plus, I've done more than survive the two speed challenges. I've finished maybe not with a smile, but with a great rush of endorphins and that ridiculous feeling that I can do anything once I get into some dry clothes and chug a big glass of water.
I'm still pinching myself: 7:57. I hope my gym teachers are reading this.
Thursday, November 15, 2012
Should I streak this year?
Yes, I titled the post thusly in hopes people would click on it.
No, I'm not talking about the naked kind of streaking. Please keep reading.
I'm talking about Runner's World's holiday run streak, however, in which one runs at least a mile per day from Thanksgiving through New Year's Day.
(Does that mean pedicures and bonding time with the couch should be scheduled for Jan. 1 or Jan. 2? I'll need to clear that up.)
It's a strange thing for someone who hypothesized that her body is starting to whisper "uncle" to decide to do, which is partly why I'm only considering and not committing.
But on the other hand, it seems like the perfect thing for someone who's running just to run to sign up for.
I'm not training for any races, and barring a sudden surge of motivation, I'm not even following a thought-out regimen right now. (It's been on my to-do list for about two weeks.) A little structure — and really, this challenge is barely structured at all — might be welcome.
Additionally, I'm an abstainer, not a moderator. Like Gretchen Rubin says in her post, it's often easier for me to do something 100 percent of the time, rather than follow the nutritionist's 80 percent/20 percent rule.
The biggest test will be Thanksgiving Day itself, obviously, and though I know how my worst-case scenario run would fit in, I'm hesitant to stick my neck out and declare that the challenge is on. Check back with me on Black Friday.
No, I'm not talking about the naked kind of streaking. Please keep reading.
I'm talking about Runner's World's holiday run streak, however, in which one runs at least a mile per day from Thanksgiving through New Year's Day.
(Does that mean pedicures and bonding time with the couch should be scheduled for Jan. 1 or Jan. 2? I'll need to clear that up.)
It's a strange thing for someone who hypothesized that her body is starting to whisper "uncle" to decide to do, which is partly why I'm only considering and not committing.
But on the other hand, it seems like the perfect thing for someone who's running just to run to sign up for.
I'm not training for any races, and barring a sudden surge of motivation, I'm not even following a thought-out regimen right now. (It's been on my to-do list for about two weeks.) A little structure — and really, this challenge is barely structured at all — might be welcome.
Additionally, I'm an abstainer, not a moderator. Like Gretchen Rubin says in her post, it's often easier for me to do something 100 percent of the time, rather than follow the nutritionist's 80 percent/20 percent rule.
The biggest test will be Thanksgiving Day itself, obviously, and though I know how my worst-case scenario run would fit in, I'm hesitant to stick my neck out and declare that the challenge is on. Check back with me on Black Friday.
Wednesday, November 14, 2012
I'm ready to reach the finish line for 2012
A friend asked me a few days ago: "Are you excited for 2013 to arrive, or are you not ready for 2012 to be over?"
In a change from past "A Long December"-ish years, I couldn't say I was necessarily eager for 2012 to wrap up. At first.
When the cider started to kick in, I stood up to go to the bathroom and realized it hadn't fully taken effect yet: Though I did need to visit the ladies room, I still could feel all the knots that tied themselves up while I sat for extended periods of time. (A long night at the bar relaxes all knots, regardless of origin, though it might tie a few new ones the next day.)
If I work out for the first time in a while, those knots have tended to be in the quads or the hamstrings. Not this night — it was my new nemesis, the hips.
It's more tender than painful. It creeps up sometimes during, sometimes after a run. And it's relatively new to me.
Whatever it is started sometime after my move to Des Moines, and I'm pretty sure it wasn't during the first few months. It could've been September; it was definitely in play by October.
My best guess as to its origins is my unprecedented mileage this year. In 2010 and 2011, I basically stuck to biking during the summer, but this year, my job change worked out to summer running's advantage.
The way to test this theory would be to back off the running, which I would do — despite the great mental boost it is for me, especially during the fall — if it weren't for the 1000 Mile Challenge. As of this writing, though not as of the cider night, I've broken 800 miles and will reach 900, most likely.
So I'm not going to spend the next few weeks on the sofa. I've taken the first step of finding hip-strengthening exercises (now I need to actually do them), and I'm going to keep running until Jan. 1, 2013. Then it's couch time.
And so if this friend asks me again: "Ready for 2013?" I'm going to say yes. Not emphatically as in "I-hate-running-and-can't-wait-to-quit"; more accepting with a splash of regret, because while runner's hip isn't the greatest, runner's high is.
I realize that writing this makes me sound like an idiot who deserves any medical comeuppance. In my defense, I could tell when it was time to quit running on buniony, weak-jointed feet and wait it out. The way my hips feel is nowhere near comparable.
In a change from past "A Long December"-ish years, I couldn't say I was necessarily eager for 2012 to wrap up. At first.
When the cider started to kick in, I stood up to go to the bathroom and realized it hadn't fully taken effect yet: Though I did need to visit the ladies room, I still could feel all the knots that tied themselves up while I sat for extended periods of time. (A long night at the bar relaxes all knots, regardless of origin, though it might tie a few new ones the next day.)
If I work out for the first time in a while, those knots have tended to be in the quads or the hamstrings. Not this night — it was my new nemesis, the hips.
It's more tender than painful. It creeps up sometimes during, sometimes after a run. And it's relatively new to me.
Whatever it is started sometime after my move to Des Moines, and I'm pretty sure it wasn't during the first few months. It could've been September; it was definitely in play by October.
My best guess as to its origins is my unprecedented mileage this year. In 2010 and 2011, I basically stuck to biking during the summer, but this year, my job change worked out to summer running's advantage.
The way to test this theory would be to back off the running, which I would do — despite the great mental boost it is for me, especially during the fall — if it weren't for the 1000 Mile Challenge. As of this writing, though not as of the cider night, I've broken 800 miles and will reach 900, most likely.
So I'm not going to spend the next few weeks on the sofa. I've taken the first step of finding hip-strengthening exercises (now I need to actually do them), and I'm going to keep running until Jan. 1, 2013. Then it's couch time.
And so if this friend asks me again: "Ready for 2013?" I'm going to say yes. Not emphatically as in "I-hate-running-and-can't-wait-to-quit"; more accepting with a splash of regret, because while runner's hip isn't the greatest, runner's high is.
I realize that writing this makes me sound like an idiot who deserves any medical comeuppance. In my defense, I could tell when it was time to quit running on buniony, weak-jointed feet and wait it out. The way my hips feel is nowhere near comparable.
Friday, November 2, 2012
My 10th check-in on the Rock River 1000 Mile Challenge
I keep forgetting it's so late in the year; typing "10th" reminded me of it for the billionth time.
So through Wednesday, I've run or walked 778 miles this year. For some reason — maybe seeing a friend's "900" on Facebook — I thought I'd be closer to 800 than that, but it turns out I'm on track for my settling goal of 900 miles this year. (As long as I average 14 to 15 miles per week.)
It was a pleasant surprise coming after a startling one, but my sister was right: Spending six days in Europe (plus two in airports) will rack up some distance. Maybe what I think is rust on my legs right now is actually fatigue.
Anyway, to pre-empt anyone trying to convince me that 1,000 is still mathematically possible, I counted out the remaining weeks in the year and divided the remaining miles to 1,000 by that.
Again, it's freaking late in the year: There are eight full weeks, plus some change, left until 2013. It would take a weekly average of 27 miles to get there.
Out of curiosity, I checked to see whether I've hit that this year ... nope. Technically I haven't broken 26 in one week, though I'm sure that if I were a diligent pedometer user, that would change.
Where I'm at, though, isn't a disappointment. I neglected my bike all summer, that's true, but I've well surpassed my 2011 run/walk mileage, and I'll blow it out of the water by the end of the year.
So through Wednesday, I've run or walked 778 miles this year. For some reason — maybe seeing a friend's "900" on Facebook — I thought I'd be closer to 800 than that, but it turns out I'm on track for my settling goal of 900 miles this year. (As long as I average 14 to 15 miles per week.)
It was a pleasant surprise coming after a startling one, but my sister was right: Spending six days in Europe (plus two in airports) will rack up some distance. Maybe what I think is rust on my legs right now is actually fatigue.
Anyway, to pre-empt anyone trying to convince me that 1,000 is still mathematically possible, I counted out the remaining weeks in the year and divided the remaining miles to 1,000 by that.
Again, it's freaking late in the year: There are eight full weeks, plus some change, left until 2013. It would take a weekly average of 27 miles to get there.
Out of curiosity, I checked to see whether I've hit that this year ... nope. Technically I haven't broken 26 in one week, though I'm sure that if I were a diligent pedometer user, that would change.
Where I'm at, though, isn't a disappointment. I neglected my bike all summer, that's true, but I've well surpassed my 2011 run/walk mileage, and I'll blow it out of the water by the end of the year.
Tuesday, October 30, 2012
The final step back into my routine
Yesterday was a day full of back-to-normal activities. I drove, and on the right-hand side of the road. I spent American dollars. I took a long shower without flip-flops. And I went on a run.
As I shuffled up the road outside my apartment, my pace was deliberately slow for two reasons: the wind and the rust. I'd spent six days in London, sandwiched by a full day of travel on either side. And then it occurred to me that I didn't remember the last time I'd been on a run (excepting my failed attempt to grab a departing train).
The last true run before my Oct. 29 effort, it turns out, was Oct. 17. The following two days, I had meant to run, but life got in the way, and then after that it was either travel preparations or the actual trip (which, I had already decided, would not feature a run).
I felt a bit of regret, knowing it would put me behind on my 1,000-mile challenge, but it seemed like my Google Reader had been trying to send me a message. All the running blogs I follow were extolling the virtues of rest ... so I embraced my 7.5-mile week.
Still, it's a bit scary — at least for this nonnatural runner — to go so long without running. Each day that passes after a run seems to chip away at my motivation to get back out there; I'd taken nearly two weeks off. (Which isn't to say I was lazy — I estimated that I walked 22 miles over the course of my trip.)
Thank God yesterday's run went off with only the expected hitches, or, rather, stitches. I lost my breath and stride at the same spots I always do on this particular route, no matter what shape I'm in.
Once I hit the flat final stretch, I was mostly fine — I knew there'd be another run after this one. No pain, only mild and fleeting discomfort; no anger; and no excessive sweat (less than normal, in fact).
I'm unequivocally glad now that I took that time off. I had a few aches before I did, and I'm sure they'll return if I ramp up the mileage again, but I hadn't given myself the summer break I'd been used to in 2010 and 2011. Maybe fall break was a must for those muscles and joints.
And given the mild yearning I felt while watching Londoners run, my mind might've needed the time away to grow fonder, too.
As I shuffled up the road outside my apartment, my pace was deliberately slow for two reasons: the wind and the rust. I'd spent six days in London, sandwiched by a full day of travel on either side. And then it occurred to me that I didn't remember the last time I'd been on a run (excepting my failed attempt to grab a departing train).
The last true run before my Oct. 29 effort, it turns out, was Oct. 17. The following two days, I had meant to run, but life got in the way, and then after that it was either travel preparations or the actual trip (which, I had already decided, would not feature a run).
I felt a bit of regret, knowing it would put me behind on my 1,000-mile challenge, but it seemed like my Google Reader had been trying to send me a message. All the running blogs I follow were extolling the virtues of rest ... so I embraced my 7.5-mile week.
Still, it's a bit scary — at least for this nonnatural runner — to go so long without running. Each day that passes after a run seems to chip away at my motivation to get back out there; I'd taken nearly two weeks off. (Which isn't to say I was lazy — I estimated that I walked 22 miles over the course of my trip.)
Thank God yesterday's run went off with only the expected hitches, or, rather, stitches. I lost my breath and stride at the same spots I always do on this particular route, no matter what shape I'm in.
Once I hit the flat final stretch, I was mostly fine — I knew there'd be another run after this one. No pain, only mild and fleeting discomfort; no anger; and no excessive sweat (less than normal, in fact).
I'm unequivocally glad now that I took that time off. I had a few aches before I did, and I'm sure they'll return if I ramp up the mileage again, but I hadn't given myself the summer break I'd been used to in 2010 and 2011. Maybe fall break was a must for those muscles and joints.
And given the mild yearning I felt while watching Londoners run, my mind might've needed the time away to grow fonder, too.
Tuesday, October 2, 2012
My ninth check-in on the Rock River 1000 Mile Challenge
The further into the 1000 Mile Challenge I get, the more diligent I become about tracking my walking.
No, I don't log the distance from my work to my car, or my apartment to my car — though maybe I should — but if I'm going to save my sanity and stroll to an event rather than move my car a half-mile closer, or if I'm going to spend a few hours at a festival, yeah, I'm gonna record that. Particularly if I feel any sort of burn the next day.
It's really like saving your spare change here and there, but there were definitely a few weekends in September where that walking put me up over 20 for the week. The recent short-term goal has been to get closer to 20 than 15.
So anyway, through Sunday, I've logged almost 705 miles for the year. The weekly average to win creeps ever higher: I'd have to get 24-plus per week, and that's just not in the cards.
But to get to 900, it looks like about 16 or 17 per week will do the trick. I just have to keep remembering that running chases away the grumpies and the caloric remorse over beer.
No, I don't log the distance from my work to my car, or my apartment to my car — though maybe I should — but if I'm going to save my sanity and stroll to an event rather than move my car a half-mile closer, or if I'm going to spend a few hours at a festival, yeah, I'm gonna record that. Particularly if I feel any sort of burn the next day.
It's really like saving your spare change here and there, but there were definitely a few weekends in September where that walking put me up over 20 for the week. The recent short-term goal has been to get closer to 20 than 15.
So anyway, through Sunday, I've logged almost 705 miles for the year. The weekly average to win creeps ever higher: I'd have to get 24-plus per week, and that's just not in the cards.
But to get to 900, it looks like about 16 or 17 per week will do the trick. I just have to keep remembering that running chases away the grumpies and the caloric remorse over beer.
Friday, August 31, 2012
My eighth check-in on the Rock River 1000 Mile Challenge
First order of business: Happy 26th birthday to me!
If you'd asked me four or more years ago what I'd be doing on my 26th birthday, I never would've said: "Sitting in Des Moines, Iowa, and adding up how many miles I've run and walked — but mostly run — this year while my bike grew dusty and cobwebby."
Second order of business: That total is 612 through yesterday. Over Labor Day weekend, I might add some walking miles, but I'd rather post now and overdeliver instead of post later and underdeliver.
Apparently I've been averaging about 17 miles per week, which is below the 19ish that would've put me on pace for 1,000.
Though at 35 weeks into the year, falling two short a week puts me well off course, I'm pleasantly surprised at my weekly average — at this rate, I'll still break 900 miles for 2012.
It's a good thing I didn't give in to the moderate pessimism I felt the other day, after not running and checking Thursday's forecast (why so hot again?), and then assuming I was so far off course that it no longer mattered.
Checking my stats after putting in 6.2 miles was a much better call, creaky neck and tight hamstrings and sluggish muscles aside.
And no doubt the runner's high — I love that it still hits you, even during a crappy run and even only with tenths of a mile to go — was speaking ... but it did occur to me that fall and early winter will bring me my preferred running conditions.
Who knows what'll happen then. Yeah, there are out-of-town trips and holidays galore, but maybe I'll have more giddyup then. Or maybe I'll persuade myself to run the Des Moines Half, which doesn't much appeal to me now during the sluggish days of summer but might seem more doable when it's cooler.
If you'd asked me four or more years ago what I'd be doing on my 26th birthday, I never would've said: "Sitting in Des Moines, Iowa, and adding up how many miles I've run and walked — but mostly run — this year while my bike grew dusty and cobwebby."
Second order of business: That total is 612 through yesterday. Over Labor Day weekend, I might add some walking miles, but I'd rather post now and overdeliver instead of post later and underdeliver.
Apparently I've been averaging about 17 miles per week, which is below the 19ish that would've put me on pace for 1,000.
Though at 35 weeks into the year, falling two short a week puts me well off course, I'm pleasantly surprised at my weekly average — at this rate, I'll still break 900 miles for 2012.
It's a good thing I didn't give in to the moderate pessimism I felt the other day, after not running and checking Thursday's forecast (why so hot again?), and then assuming I was so far off course that it no longer mattered.
Checking my stats after putting in 6.2 miles was a much better call, creaky neck and tight hamstrings and sluggish muscles aside.
And no doubt the runner's high — I love that it still hits you, even during a crappy run and even only with tenths of a mile to go — was speaking ... but it did occur to me that fall and early winter will bring me my preferred running conditions.
Who knows what'll happen then. Yeah, there are out-of-town trips and holidays galore, but maybe I'll have more giddyup then. Or maybe I'll persuade myself to run the Des Moines Half, which doesn't much appeal to me now during the sluggish days of summer but might seem more doable when it's cooler.
Friday, July 20, 2012
Whoaaaaaaa, I'm halfway there!
This past Sunday, I broke the 500-mile mark for the year (that's running plus the walking I've been able to record), and I didn't even realize it until probably a day later.
It wasn't that I didn't know it was coming — at some point last week, I calculated the right-then mileage, and it was close enough where I thought, "Here comes 500!" ... and then promptly forgot.
My absent-mindedness probably worked in my favor here, however: I always want milestones to feel electric, to make me buzz with excitement, and inevitably that urge to note a special feeling means the moment falls flat. Guess I put too much pressure on the milestone.
Instead, the surprise of No. 500 gave me that sought-after jolt of accomplishment as I added up my previous-week and year-to-date mileage on Monday night.
Anyway, I notched 500 somewhere in the neighborhood south of my apartment complex during a nighttime run, so odds are good that I was focusing on not falling and on not running over any walkers (the sidewalks are normal-sized in this neighborhood, instead of extra-wide, as they are along some of the main roads in West Des Moines).
It was probably on the long, steady, slight incline, so I probably was also huffing and puffing and possibly swearing delicately. My overall effort that evening was strong, though: My splits were 9:43, 9:15, 9:30, 9:42 (is this it?) and 9:24. Not bad, considering the low light and high humidity.
Obviously, the title of the post is a reference to both the 1000 Mile Challenge and "Livin' On A Prayer." As I mentioned earlier, I'm unlikely to reach 1,000 miles, but I looked back at my 2011 wrap-up post to see how many running/walking miles I was able to record that year: 669, plus several outings during which I didn't have a tracking device.
So a few weeks past the year's halfway point, I'm at 75 percent of last year's total, and well on my way to surpassing the modest goal I mentioned in the early 2012 post (breaking 700 miles).
I'm pretty pleased with these numbers. They've come at a cost to my biking, of course, and a recent solo excursion has reminded me of what I'm missing, but next year's big adventure should compensate for that ...
It wasn't that I didn't know it was coming — at some point last week, I calculated the right-then mileage, and it was close enough where I thought, "Here comes 500!" ... and then promptly forgot.
My absent-mindedness probably worked in my favor here, however: I always want milestones to feel electric, to make me buzz with excitement, and inevitably that urge to note a special feeling means the moment falls flat. Guess I put too much pressure on the milestone.
Instead, the surprise of No. 500 gave me that sought-after jolt of accomplishment as I added up my previous-week and year-to-date mileage on Monday night.
Anyway, I notched 500 somewhere in the neighborhood south of my apartment complex during a nighttime run, so odds are good that I was focusing on not falling and on not running over any walkers (the sidewalks are normal-sized in this neighborhood, instead of extra-wide, as they are along some of the main roads in West Des Moines).
It was probably on the long, steady, slight incline, so I probably was also huffing and puffing and possibly swearing delicately. My overall effort that evening was strong, though: My splits were 9:43, 9:15, 9:30, 9:42 (is this it?) and 9:24. Not bad, considering the low light and high humidity.
Obviously, the title of the post is a reference to both the 1000 Mile Challenge and "Livin' On A Prayer." As I mentioned earlier, I'm unlikely to reach 1,000 miles, but I looked back at my 2011 wrap-up post to see how many running/walking miles I was able to record that year: 669, plus several outings during which I didn't have a tracking device.
So a few weeks past the year's halfway point, I'm at 75 percent of last year's total, and well on my way to surpassing the modest goal I mentioned in the early 2012 post (breaking 700 miles).
I'm pretty pleased with these numbers. They've come at a cost to my biking, of course, and a recent solo excursion has reminded me of what I'm missing, but next year's big adventure should compensate for that ...
Tuesday, July 3, 2012
My sixth check-in on the Rock River 1000 Mile Challenge
With the year halfway done, here's how I'm doing on Daily Mile's Rock River 1000 Mile Challenge.
Obviously, I should be at 500 miles ... and I've logged 461, or 39 off pace for the year.
I know objectively that this is a somewhat significant gap, as far as catching up goes, but when I think of how much I avoided summer runs in the past few years, I feel like patting myself on the back, high-fiving myself and buying myself a celebratory drink.
After all, I logged about seven-ish miles for the two weeks after my half marathon, which had put me within three miles of being exactly on track. Those two weeks were spent recovering from the race and moving 300 miles for a new, improved job, so I don't have any reason to berate myself.
That fortnight is responsible for about two-thirds of my shortfall; over the course of the following month, I came up short a few miles a few weeks, and that's it. So I'm well on my way to establishing the habit of running four-plus miles regularly, and I'm working on going past that more often.
Will this get me to 1,000 miles by Dec. 31? Maybe, maybe not — I have to average closer to 21 miles per week for the rest of the year. But it's not outside the realm of possibility, and I'm on track to break 900 if I maintain the status quo. That would still be worth celebrating.
Past monthly check-ins: January through April (at Get Running) and May (at Little Runner, Bigger City).
Obviously, I should be at 500 miles ... and I've logged 461, or 39 off pace for the year.
I know objectively that this is a somewhat significant gap, as far as catching up goes, but when I think of how much I avoided summer runs in the past few years, I feel like patting myself on the back, high-fiving myself and buying myself a celebratory drink.
After all, I logged about seven-ish miles for the two weeks after my half marathon, which had put me within three miles of being exactly on track. Those two weeks were spent recovering from the race and moving 300 miles for a new, improved job, so I don't have any reason to berate myself.
That fortnight is responsible for about two-thirds of my shortfall; over the course of the following month, I came up short a few miles a few weeks, and that's it. So I'm well on my way to establishing the habit of running four-plus miles regularly, and I'm working on going past that more often.
Will this get me to 1,000 miles by Dec. 31? Maybe, maybe not — I have to average closer to 21 miles per week for the rest of the year. But it's not outside the realm of possibility, and I'm on track to break 900 if I maintain the status quo. That would still be worth celebrating.
* * *
Past monthly check-ins: January through April (at Get Running) and May (at Little Runner, Bigger City).
Saturday, June 23, 2012
Cross-training across Des Moines
I haven't run the past two days, but it's OK — recovery days are also reconnaissance days, as it turns out.
On Thursday I again joined the Scheels bike group for a 30ish-mile ride (my total distance was 33.5 miles, but that includes biking to the meeting place and peeling off to go directly home at the end).
This group serves a couple of purposes for me: socializing; challenging myself in something at which I actually can improve; and, duh, guiding me through the Des Moines trail system ... in particular, showing me a fast way to access a nearby trail, without making me read a map.
With a slower pace and better weather, I had more mental energy to spend on observing the trail, as opposed to gluing my eyes to the next-to-last cyclist's wheel. The trees, the creek, the gentle breeze were all so refreshing and energizing as we whizzed through at 15 mph. And it hit me — why the heck was I running on shade-free sidewalks, especially when the sun was out?
Maybe, in addition to the timing switches I've been considering, I should consider changing locations, to the forested valley through which the bike group leads me. It's less than two miles from my complex; a full-grown (mentally full-grown) adult should be able to manage her time adequately enough to make a cool run there happen.
Friday, I took advantage of my early-bird downtown parking spot to stroll over to the Des Moines Arts Festival after work. (Yep, I counted that, plus a short morning errand, toward my 1,000-mile goal. Every mile, and every mile increment, counts.)
One of the timing switches I've been considering is incorporating more evening runs into my routine. On Friday and Saturday nights, I'm off work early, leaving me time to head home, eat, digest and then exercise while it's still light. Other days, when I leave at 9 p.m., I don't have that luxury — but it occurred to me that I could stave off both dehydration/heat stroke and running route boredom by bringing running gear to work and heading out right away.
The link between this and the art festival: My co-worker mentioned, as we passed the Western Gateway Park sculptures, how beautiful it is when the pieces are illuminated at night. Aha! A new, well-lit place to run!
I feel very satisfied with this cross-training/recovery combination.
On Thursday I again joined the Scheels bike group for a 30ish-mile ride (my total distance was 33.5 miles, but that includes biking to the meeting place and peeling off to go directly home at the end).
This group serves a couple of purposes for me: socializing; challenging myself in something at which I actually can improve; and, duh, guiding me through the Des Moines trail system ... in particular, showing me a fast way to access a nearby trail, without making me read a map.
With a slower pace and better weather, I had more mental energy to spend on observing the trail, as opposed to gluing my eyes to the next-to-last cyclist's wheel. The trees, the creek, the gentle breeze were all so refreshing and energizing as we whizzed through at 15 mph. And it hit me — why the heck was I running on shade-free sidewalks, especially when the sun was out?
Maybe, in addition to the timing switches I've been considering, I should consider changing locations, to the forested valley through which the bike group leads me. It's less than two miles from my complex; a full-grown (mentally full-grown) adult should be able to manage her time adequately enough to make a cool run there happen.
Friday, I took advantage of my early-bird downtown parking spot to stroll over to the Des Moines Arts Festival after work. (Yep, I counted that, plus a short morning errand, toward my 1,000-mile goal. Every mile, and every mile increment, counts.)
One of the timing switches I've been considering is incorporating more evening runs into my routine. On Friday and Saturday nights, I'm off work early, leaving me time to head home, eat, digest and then exercise while it's still light. Other days, when I leave at 9 p.m., I don't have that luxury — but it occurred to me that I could stave off both dehydration/heat stroke and running route boredom by bringing running gear to work and heading out right away.
The link between this and the art festival: My co-worker mentioned, as we passed the Western Gateway Park sculptures, how beautiful it is when the pieces are illuminated at night. Aha! A new, well-lit place to run!
I feel very satisfied with this cross-training/recovery combination.
Sunday, June 17, 2012
My fifth check-in on the Rock River 1000 Mile Challenge
At my old blog, Get Running, I'd been doing monthly check-ins on my progress in Daily Mile's Rock River 1000 Mile Challenge.
The goal is obvious; you can combine running and walking, but the description omits biking (which would make it pretty darn easy, IMO), so I haven't been counting that. "Everyone wins," according to the site ... however, I'm not sure I'll hit the 1,000 by Dec. 31.
But I digress. I punted on May's check-in because I'd quit my old job and was in the process of moving for a new one. Also, I lacked the energy, the time and the name for my new blog. So this entry gets a bonus week (the first full one in June).
Through those 22 weeks, I've run/walked 395.26 miles, which is, sadly and suddenly, way off-pace. I need to average about 19 miles per week, for a total of 423 miles through Week 22.
Almost 30 miles behind, with the halfway point of the year approaching. Not so good. Back in January, I was confident that training for a 10-miler and half marathon would've given me a cushion by the time hot weather arrived. Oh, that naive, foolish 25.42-year-old ... if only she knew what the 25.83-year-old knows now!
Wait, what do I know now, besides that my long runs weren't going to compensate for the two-week dry span that I suspect torpedoed my pace? (In my defense, I'd just finished a half marathon and was preparing for and executing a 300-mile move.)
Even before I confirmed my suspicions that I'd fallen behind, I'd been ruminating on my running behavior — specifically, my short/easy/just-get-'er-done run length. It's been three to 3.5 miles ever since I started running full time in spring 2008.
Several ingredients went into the realization that it was time to take that up a notch: reading other runners' lengthier workout summaries on Twitter; experiencing pleasant local weather and a fresh, new area to explore; eating cookies, ice cream, brownies and dark chocolate nuggets; noticing that I've long passed noob status and haven't ramped up speed or mileage; and, finally, knowing that I'd have to run six three-milers a week to stay on track with the 1000 Mile Challenge.
If I can make four miles my default distance, I can gain a little bit of ground on my challenge. I also then can start phasing in five- and six-milers as my midlength run distance.
With my new hours at my new job, this all seems slightly more feasible. Instead of wrapping up work at midnight or 1 a.m., I now head out somewhere between 6 and 9 p.m. right now, which during the hot summer days leaves me a decent window of daylight even after dinner.
So no distress calls on the 1000 Mile Challenge just yet — there's time to redeem myself and regain some ground.
The goal is obvious; you can combine running and walking, but the description omits biking (which would make it pretty darn easy, IMO), so I haven't been counting that. "Everyone wins," according to the site ... however, I'm not sure I'll hit the 1,000 by Dec. 31.
But I digress. I punted on May's check-in because I'd quit my old job and was in the process of moving for a new one. Also, I lacked the energy, the time and the name for my new blog. So this entry gets a bonus week (the first full one in June).
Through those 22 weeks, I've run/walked 395.26 miles, which is, sadly and suddenly, way off-pace. I need to average about 19 miles per week, for a total of 423 miles through Week 22.
Almost 30 miles behind, with the halfway point of the year approaching. Not so good. Back in January, I was confident that training for a 10-miler and half marathon would've given me a cushion by the time hot weather arrived. Oh, that naive, foolish 25.42-year-old ... if only she knew what the 25.83-year-old knows now!
Wait, what do I know now, besides that my long runs weren't going to compensate for the two-week dry span that I suspect torpedoed my pace? (In my defense, I'd just finished a half marathon and was preparing for and executing a 300-mile move.)
Even before I confirmed my suspicions that I'd fallen behind, I'd been ruminating on my running behavior — specifically, my short/easy/just-get-'er-done run length. It's been three to 3.5 miles ever since I started running full time in spring 2008.
Several ingredients went into the realization that it was time to take that up a notch: reading other runners' lengthier workout summaries on Twitter; experiencing pleasant local weather and a fresh, new area to explore; eating cookies, ice cream, brownies and dark chocolate nuggets; noticing that I've long passed noob status and haven't ramped up speed or mileage; and, finally, knowing that I'd have to run six three-milers a week to stay on track with the 1000 Mile Challenge.
If I can make four miles my default distance, I can gain a little bit of ground on my challenge. I also then can start phasing in five- and six-milers as my midlength run distance.
With my new hours at my new job, this all seems slightly more feasible. Instead of wrapping up work at midnight or 1 a.m., I now head out somewhere between 6 and 9 p.m. right now, which during the hot summer days leaves me a decent window of daylight even after dinner.
So no distress calls on the 1000 Mile Challenge just yet — there's time to redeem myself and regain some ground.
Subscribe to:
Posts (Atom)