Showing posts with label training. Show all posts
Showing posts with label training. Show all posts
Sunday, July 14, 2019
Day 14 Week Two Blues
Week two is the hardest. Week one is great, you get to feel successful with each day of training; look at me I did it, I ran three days in a row! Week two you realize you have to do it again, and again for another 17 weeks. This week was hard but I'm glad that I got it done. I got the right number of miles in, sort of unconventionally, but I did it.
Here's what week 2 looked like:
Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Plan rest 3mi 5mi 3mi rest 9mi cross
Actual rest 2mi 2.5mi(w) track/2mi 4.54mi 2.23mi 8.9mi
Total: 22.27miles
I didn't cross train last week nor this week. Frisbee covers a lot of the other type of movements I need. I think when I have less frisbee I can work in more of a cross training workout into my routine. Tuesday and Thursday were both frisbee days. I did a track workout before a double header on Thursday and my quads were sore for the next few days. Wednesday was a walk, so not a run. I know part of my struggle is making sure I continue to do things every day when I can so I can't get too mad if it's a walk and not a run. As long as I get my miles in and make sure I hit my long runs I feel good about it. I thought the run I picked on Friday was 5 miles, when I double checked on mapmyrun.com I realized that the 5 mile route adds one small part that I didn't do. I'm mostly happy about my Sunday run. I ran a similar run last week but shorter (took out an extra section I added to get close to 9 miles) and I did it faster. I'm hoping this gets me slowly to a more comfortable feeling running "pace" runs.
Sorry nothing exciting or profound this week. Just wanted to make sure I kept to my accountability by posting what I did. Week 3 will be interesting. Next Friday, Saturday, Sunday is Master's Nationals so it will be a lot of frisbee. Hopefully I'll have deeper thoughts after that!
Saturday, July 6, 2019
Day 6 - I got 99 problems but mental hurdles ain't one
I've written a lot about the mental hurdles you have to get over to run races, especially long distance races. Not surprisingly the most common response I get when I mention running a marathon or an ultra marathon is "I could never do it". But you can! I was just talking with a friend about running and why I've always believed anyone could run. As well documented in "Born To Run" (the infamous book that convinced me I should try a 100 miler and a blog) humans are built to run. We were built to chase prey over long distances. What changed? Well we don't have to chase our prey, we don't even have to drive for prepackaged prey someone will drive it to you. We also have a lot of pavement which is just not really great on your body. We made shoes to help, but for anyone who's done a road marathon and a trail marathon you can tell pretty quickly when you have to walk down stairs the day after.
Part of the challenge of running long distance races is convincing your brain, tainted by society, that you can do it. I remember the first time I ran 10 miles, the first time I reached double digit miles. I couldn't believe it had happened and how easy it actually was. And after that, every run that came next; 13 miles, 18 miles, 26.2 miles, 50 miles wasn't impossible. You really do have to just do it and experience that you can do it and there you are. A lot of races are run with doubt. Doubt that you can finish, keep going, get over that next hill. A lot of races are also lost by poor training and injury. But you'd be surprised by how many times just thinking "I can't" gets in the way of finishing, and even more so, signing up for a race.
After I finished my first marathon I felt like I could do it again. After I finished my first 50 miler I know I could probably do anything as long as I didn't mind getting sick after. That's the belief that carried me through the Salida Race Through Time Half Marathon this March. That race was my first long distance trail race in I think 2012. I was terrified the night before. Wrong Way Ryan can attest to that. While him and the Bearded Wonder were out getting beers, I was laying in my bed obsessing over the race map. And I had trained for that race. I had done everything right. Fast forward to this March I "trained" with almost zero trail miles, drank beers with everyone the night before, and just sort of showed up and did it. I did it because the doing 13.1 miles wasn't the hard part. I knew I could do it, I had done it. I also knew I couldn't do it as fast as I wanted to so I paced accordingly.
It's that thinking that's gotten me pretty sloppy at training.
So part of this adventure right now is improving the other parts of racing. My brain is fantastically equipped to complete impossible tasks. My legs, not so much. So my mental hurdle is picking a training run over happy hour and running even if it's a league night. Or in the case of this past week, going on a run after happy hour. That was rough, so many burps. I have to get over the mental hurdle of missing social engagements and pushing myself along with frisbee. I'd love to see a running book dedicated to FOMO.
Here's how I did this week:
Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Plan: rest 3m 5m pace 3m rest 8m cross
Actual: 3.26m 2m 3.36m 5.53m Rest! 8.33m
Total: 22.38m
I ran on a rest day, Monday's are good nights for me to run because I don't have frisbee league so I think I'll likely continue with running on Mondays. I only did 2 miles Tuesday because it was frisbee league. I wore my garmin watch and it gave me 2 miles of running during one game. I consider that sort of pace work because it's a lot of sprinting. Wednesday was after a happy hour so I'm glad I at least got a run in. Thursday was a great hike. Hiking up hill is sprinting in disguise so I think that was a good alternative. Friday I actually rested! Saturday I did a long road run, it wasn't as fast as I want it to be so I'm hoping my times start to get better. Which I know means actually doing the pace runs. Sunday is cross training so I think I'll do a hike and/or some strength training.
So week one was ok. I got in more miles than required so I am glad I took one rest day. Hurdle of week 1 is over and I think I did ok. Maybe I manufactured a way to get over that hurdle in a non-traditional way, but considering where I've been I'm pleased.
Part of the challenge of running long distance races is convincing your brain, tainted by society, that you can do it. I remember the first time I ran 10 miles, the first time I reached double digit miles. I couldn't believe it had happened and how easy it actually was. And after that, every run that came next; 13 miles, 18 miles, 26.2 miles, 50 miles wasn't impossible. You really do have to just do it and experience that you can do it and there you are. A lot of races are run with doubt. Doubt that you can finish, keep going, get over that next hill. A lot of races are also lost by poor training and injury. But you'd be surprised by how many times just thinking "I can't" gets in the way of finishing, and even more so, signing up for a race.
After I finished my first marathon I felt like I could do it again. After I finished my first 50 miler I know I could probably do anything as long as I didn't mind getting sick after. That's the belief that carried me through the Salida Race Through Time Half Marathon this March. That race was my first long distance trail race in I think 2012. I was terrified the night before. Wrong Way Ryan can attest to that. While him and the Bearded Wonder were out getting beers, I was laying in my bed obsessing over the race map. And I had trained for that race. I had done everything right. Fast forward to this March I "trained" with almost zero trail miles, drank beers with everyone the night before, and just sort of showed up and did it. I did it because the doing 13.1 miles wasn't the hard part. I knew I could do it, I had done it. I also knew I couldn't do it as fast as I wanted to so I paced accordingly.
It's that thinking that's gotten me pretty sloppy at training.
So part of this adventure right now is improving the other parts of racing. My brain is fantastically equipped to complete impossible tasks. My legs, not so much. So my mental hurdle is picking a training run over happy hour and running even if it's a league night. Or in the case of this past week, going on a run after happy hour. That was rough, so many burps. I have to get over the mental hurdle of missing social engagements and pushing myself along with frisbee. I'd love to see a running book dedicated to FOMO.
Here's how I did this week:
Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Plan: rest 3m 5m pace 3m rest 8m cross
Actual: 3.26m 2m 3.36m 5.53m Rest! 8.33m
Total: 22.38m
I ran on a rest day, Monday's are good nights for me to run because I don't have frisbee league so I think I'll likely continue with running on Mondays. I only did 2 miles Tuesday because it was frisbee league. I wore my garmin watch and it gave me 2 miles of running during one game. I consider that sort of pace work because it's a lot of sprinting. Wednesday was after a happy hour so I'm glad I at least got a run in. Thursday was a great hike. Hiking up hill is sprinting in disguise so I think that was a good alternative. Friday I actually rested! Saturday I did a long road run, it wasn't as fast as I want it to be so I'm hoping my times start to get better. Which I know means actually doing the pace runs. Sunday is cross training so I think I'll do a hike and/or some strength training.
So week one was ok. I got in more miles than required so I am glad I took one rest day. Hurdle of week 1 is over and I think I did ok. Maybe I manufactured a way to get over that hurdle in a non-traditional way, but considering where I've been I'm pleased.
Monday, July 1, 2019
Day 1 - A fools errand?
I haven't posted in awhile mostly because I haven't really been running. I dabbled. I ran the Salida Half Marathon this June. Ill advised. I did the least amount of training one could do without finishing being considered a miracle. I did finish, I felt mostly ok. The most I ran three months before was 10 miles, on the road, super slow.
The other day I made a deal with myself that I would run a race this fall. To get to that point I am starting my training today and my goal is to stick to it and really do it. I've followed training programs before and by followed I mean "followed". I was terrible at sticking to the mileage, the pattern of running. The one time I did it, really did it, was when I trained for my first marathon back in 2008. 11 years ago to today; day 1.
I have a few goals.
1. Stick to the program as close as I can to make sure I get the milage in per week and honor the pace days, rest days, and days run in a row. For reference I'm going to use the Hal Higdon Novice 2 program.
Week 1 looks like this:
Monday Tuesday Wednesday Thursday Friday Saturday Sunday Total
rest 3mi 5mi pace 3mi rest 8mi cross 19mi
2. Report out on it. I probably won't post every day, but I will do my best to post once a week with an update on how well I'm staying on track.
3. Run a sub 4hr marathon. This one may not happen at the end of the 18 weeks. I haven't found a marathon that quite matches up There's a half thats pretty close so I may got for a sub 2hr half and use that to spring into a marathon within that month.
4. Get the courage to do another 50miler. I still want to get to at least one 100 miler in my life. To feel confident doing that I need to better my 50miler times. So I'd like to commit to signing up for a 50 miler by the end of this training.
I get inspired by reading about running. I just finished Peter Sagel's book "The Incomplete Book of Running". I'm going to start "What I Talk When I Talk About Running" by Haruki Murakami. I followed a lot of the Western States tracking this past weekend so I think I've got a good dose of inspiration.
So today is Day 1. The training program is 18 weeks. That's 126 days. I already messed up the schedule, today is a rest day, but I had time when I got home after work so I ran 3ish miles. I may look at switching rest days up.
The other day I made a deal with myself that I would run a race this fall. To get to that point I am starting my training today and my goal is to stick to it and really do it. I've followed training programs before and by followed I mean "followed". I was terrible at sticking to the mileage, the pattern of running. The one time I did it, really did it, was when I trained for my first marathon back in 2008. 11 years ago to today; day 1.
I have a few goals.
1. Stick to the program as close as I can to make sure I get the milage in per week and honor the pace days, rest days, and days run in a row. For reference I'm going to use the Hal Higdon Novice 2 program.
Week 1 looks like this:
Monday Tuesday Wednesday Thursday Friday Saturday Sunday Total
rest 3mi 5mi pace 3mi rest 8mi cross 19mi
2. Report out on it. I probably won't post every day, but I will do my best to post once a week with an update on how well I'm staying on track.
3. Run a sub 4hr marathon. This one may not happen at the end of the 18 weeks. I haven't found a marathon that quite matches up There's a half thats pretty close so I may got for a sub 2hr half and use that to spring into a marathon within that month.
4. Get the courage to do another 50miler. I still want to get to at least one 100 miler in my life. To feel confident doing that I need to better my 50miler times. So I'd like to commit to signing up for a 50 miler by the end of this training.
I get inspired by reading about running. I just finished Peter Sagel's book "The Incomplete Book of Running". I'm going to start "What I Talk When I Talk About Running" by Haruki Murakami. I followed a lot of the Western States tracking this past weekend so I think I've got a good dose of inspiration.
So today is Day 1. The training program is 18 weeks. That's 126 days. I already messed up the schedule, today is a rest day, but I had time when I got home after work so I ran 3ish miles. I may look at switching rest days up.
Saturday, May 26, 2018
How to make friends, influence people, and finish a 25mile race
![]() |
| Me hiding under the trail awning waiting for the race to start |
The weather was not ideal. It was reminiscent to the last time I ran this race although this time it was most definitely raining. So we were running in the rain while also running through the cloud that was raining on us. This is the plot of Inception 2.
![]() |
| Erin Bibeau photography got some great action shots! |
Oddly enough, I think the interesting weather played a significant part in my finishing and not feeling horrible. My final time was 6:42:14. Not amazing, but I didn't want to die at the end. The race was so wet, that there were parts unrunnable, at least for most people, which slowed everything down. Maybe I could have shaved 10-15min off with dry trails, but the forced slowness likely contributed to my lack of pain. I'm used to being on my feet for long stretches, but not as great at being on my feet for long stretches going fast. I had to take it slow, which translated into not feeling as fatigued when I'm at my slowest; uphill. I was woefully undertrained for this race. Very few trail miles and very few consistent weeks of runs. On paper I should have crawled across the finish line, but here I am, all smiles and mud.
![]() |
| Coming through the last stretch of trail before getting my mug! |
I'm not saying that my training should be mimicked. Having the experience of finishing long races, including this one, in the past mentally I knew I could finish. In distance running, physical training only goes so far. Mentally training your body to continue despite [fill in the blank] is the key to connecting it all through the last mile. It is also something that doesn't leave you as quickly as physical ability. I knew going in I wouldn't break a PR, or win my age bracket, and this time I was ok with that. I never once thought, I can't do this, I can't finish. That took years of hard miles and harder races to develop. That spark that makes me want to beat myself the next time I go out did get a little stronger.
Another significant part of my success comes down to three things: honeystinger, pickles etc, and PBR. I realized after my less than steller half marathons, that maybe I needed to revisit my fuel and calorie intake. I kept thinking "13.1 is so short I don't need to eat". False. Food is fuel and without fuel you putter around. I made a commitment to eat every 30min, with something more substantial at least every hour or as I got to aid stations. I stuck with Honey Stinger gummies while I was on the move and whatever I put in my mouth at the aid stations. This came out to be M&Ms, chips, pickles, cokes, bananas, and a quesadilla. I also celebrated the awesomeness of aid station volunteers, but drinking a small cup of PBR at mile 10. Definitely helped me get up the second big climb.
My next race is the North Fork 50k. Thanks to Wrong Way Ryan for getting me a free entry for being hands down the best aide station volunteer ever. I'm also not in the best training state for a 50k, but conquering Quad Rock give me the strength to know that I can physically get it done. And the chance of being covered, head to toe in mud, is highly unlikely. I think I have my fuel worked out more and keeping my body stocked with the energy I need to finish will be priority number one.
On a more feelings based note, while traveling for work this week, my coworker and were having general discussions about running and my upcoming race at North Fork. I was discussing my use of audio stimuli on road runs vs. trail runs (I do when I'm training miles on pavements, I never use it when I'm racing or running on trails). This brought up one of my joys of trail running and trail races; the people. You meet the best people when you're 4 hours into 32 miles and haven't seen an ice cube in what feels like days. Our discussion brought up a great memory I had a few years back running the North Fork 50k. In the stretch leading up to the last aide station before the finish, I ended up spending a lot of time with 2 women as we slowly made the climb up out of a gully. We were tired, almost 25miles into the race at this point. One of the woman was 70, she was worried about finishing within her goal time. Her goal time was important because her husband told her that if she couldn't finish this race within that time frame, she shouldn't (or couldn't) do a 100 miler she had planned on later that year. That got all of us focused on getting her to the finish so she could keep her goal alive. We talked about races, how running affects our partners and our social lives, how the other woman paced her friend while she was 7 months pregnant. We got to the last aide station and as she got her needs met and I sat down under the awning drinking the beer Wrong Way Ryan saved for me. I wished her well and told her I'd try to catch her on the way down. I did end up catching her about a mile before the finish and we finished that last leg together. As we rounded the corner into the finish I told her to go for it and she sprinted ahead to her husband cheering. I'm not going to lie, while running tends to make all of us weirdly emotional, this time I really had to hold back tears because it was just so awesome.
I'm really looking forward to North Fork. My time goal, yes I'm taking a leap and putting one out there, is 7:30. Hopefully that includes some beer before the last downhill. It's going to be hot, it always is. I got a good run in today, sweating through about 9 miles in 90 degrees. No stomach cramps and an ice cold Coke when I finished. Here's to new friends, cold beer, and 32 miles of smiles!
Labels:
50k,
awesome people,
badassness,
community,
fort collins,
gnar runners,
goals,
Honeystinger,
kircher,
mileage,
mud,
northfork,
PBR,
quad rock,
trail running,
training,
wrong way ryan
Tuesday, August 25, 2015
Doubt
One of my favorite Avett Brother's songs is Head Full of Doubt/Road Full of promises. It came to mind over the last two weeks on training runs. Doubt is a sneaky feeling. It never comes out in full force right away, it slowly seeps into your thoughts and waits until you acknowledge it and say the words; "I don't know if I can..." Then it feeds off of anything it can to plant itself firmly in your psyche.
The full force of running another 50 miler hit me as I ran around Cheesman Park two weeks ago. Although the race is a full three months away, as my legs moved at a sluggish pace, I started to doubt if I could take on a 50 miler again and finish. As soon as I let my brain wander towards doubt, the doubt monster started feeding on every fleeting thought that came bustling in: do you have time to train, what about food, what about pacers, what if it rains....what if you can't finish?
What if I can't finish?
What if I don't finish?
I've tried to be realistic about my abilities as a runner. I'm not fast, but I know my pace. What I lack in speed I make up for in knowing I can keep going despite the pain of an empty tank. The thought of not being able to finish something is a thought I ban from my memory. Doubt, like an ex-boyfriend who lives in your brain, needs a wall built around it. It's there you just hope that the wall is tall and sturdy enough to keep it contained. I let myself creep over that wall over the last two weeks and it's been a struggle not letting that doubt climb out.
I can't take back the doubt I had/have about not being able to do this race. I thought it, I can't unthink it, so that's what I have to deal with. A healthy dose of humility is not a bad thing. Fully accepting and embracing the difficulty of a race, event, task is a great motivator to do the work early on to be successful later. There's no 10 week couch to 50 miler program out there. If there was I would be highly skeptical. While the fear of a bad race is a good motivator at time, I felt the doubt start affecting my training runs and I knew I had to do something to turn that around.
First and foremost, I needed to get off the road. Road running isn't bad. I enjoy it from time to time. I indulge in lots of road races and Denver's mostly mild winter means I can run outside a good portion of the year. However, I suspected part of the doubt crept in because I haven't been doing any trail running. Even in Wisconsin I ran on the road. Sure it was around lakes with tall trees shading me, but it was still on pavement. Too much time to think about being too slow. Too much time to think about not running on the terrain the race will be on. Too much time to come up with reasons why I won't be successful.
My friend Tom and I took a Tuesday night and ran out at Apex Park. I was reminded how hard running uphill is when you've been neglecting it, but all that faded away as I darted through the Aspens and powered up the little climbs on Enchanted Forrest to be rewarded with fun rocks and root dodging on the downhills. This past weekend I was up in the Mountains and got to hop on a trail in Summit County and get some altitude training in. Not that I need altitude training for the 50 miler (the highest elevation we get to is 1890ft), but I needed to do something tough and finish it. I needed a success, to triumph over a run, shove any doubt in a sack and toss it aside. It felt good to be out and I needed a reminder why I love trails.

Doubt also reminded me I need to be more proactive about training. I recently took on an additional
contract research job which eats into my nights and even lunch time runs. I can't be quite so loose about when/where I run over the next few months because my "loose" time is limited. That's not a bad thing. It's just a time management thing I haven't had to be quite as strict about the last few months. Happy hours will suffer, but the lack of happy hours now will hopefully translate into Happier Hours on a trail December 5th.
I really wanted to write this post to help ease my mind about the fears I have going forward. Reading old posts I sound pretty darn optimistic about things and felt it was about time I admit that I'm not always 100% confident heading into races and life in general. Truthfully, my mind is not always Taylor Swift songs as I run. I think about why I run, if I'm having fun, if all of this is worth it to me. Right now the answer to the last question is still yes. As long as that is a yes then I'll keep fighting off doubt and lacing up my shoes. I'm still nervous about the race, but I'm excited for my training leading up to it. I'm so fortunate that I am able to do these crazy feats of athleticism and I'll get to the finish line one day at a time. California, here I come.
The full force of running another 50 miler hit me as I ran around Cheesman Park two weeks ago. Although the race is a full three months away, as my legs moved at a sluggish pace, I started to doubt if I could take on a 50 miler again and finish. As soon as I let my brain wander towards doubt, the doubt monster started feeding on every fleeting thought that came bustling in: do you have time to train, what about food, what about pacers, what if it rains....what if you can't finish?
What if I can't finish?
What if I don't finish?
I've tried to be realistic about my abilities as a runner. I'm not fast, but I know my pace. What I lack in speed I make up for in knowing I can keep going despite the pain of an empty tank. The thought of not being able to finish something is a thought I ban from my memory. Doubt, like an ex-boyfriend who lives in your brain, needs a wall built around it. It's there you just hope that the wall is tall and sturdy enough to keep it contained. I let myself creep over that wall over the last two weeks and it's been a struggle not letting that doubt climb out.
I can't take back the doubt I had/have about not being able to do this race. I thought it, I can't unthink it, so that's what I have to deal with. A healthy dose of humility is not a bad thing. Fully accepting and embracing the difficulty of a race, event, task is a great motivator to do the work early on to be successful later. There's no 10 week couch to 50 miler program out there. If there was I would be highly skeptical. While the fear of a bad race is a good motivator at time, I felt the doubt start affecting my training runs and I knew I had to do something to turn that around.
First and foremost, I needed to get off the road. Road running isn't bad. I enjoy it from time to time. I indulge in lots of road races and Denver's mostly mild winter means I can run outside a good portion of the year. However, I suspected part of the doubt crept in because I haven't been doing any trail running. Even in Wisconsin I ran on the road. Sure it was around lakes with tall trees shading me, but it was still on pavement. Too much time to think about being too slow. Too much time to think about not running on the terrain the race will be on. Too much time to come up with reasons why I won't be successful.
My friend Tom and I took a Tuesday night and ran out at Apex Park. I was reminded how hard running uphill is when you've been neglecting it, but all that faded away as I darted through the Aspens and powered up the little climbs on Enchanted Forrest to be rewarded with fun rocks and root dodging on the downhills. This past weekend I was up in the Mountains and got to hop on a trail in Summit County and get some altitude training in. Not that I need altitude training for the 50 miler (the highest elevation we get to is 1890ft), but I needed to do something tough and finish it. I needed a success, to triumph over a run, shove any doubt in a sack and toss it aside. It felt good to be out and I needed a reminder why I love trails.

Doubt also reminded me I need to be more proactive about training. I recently took on an additional
contract research job which eats into my nights and even lunch time runs. I can't be quite so loose about when/where I run over the next few months because my "loose" time is limited. That's not a bad thing. It's just a time management thing I haven't had to be quite as strict about the last few months. Happy hours will suffer, but the lack of happy hours now will hopefully translate into Happier Hours on a trail December 5th.
I really wanted to write this post to help ease my mind about the fears I have going forward. Reading old posts I sound pretty darn optimistic about things and felt it was about time I admit that I'm not always 100% confident heading into races and life in general. Truthfully, my mind is not always Taylor Swift songs as I run. I think about why I run, if I'm having fun, if all of this is worth it to me. Right now the answer to the last question is still yes. As long as that is a yes then I'll keep fighting off doubt and lacing up my shoes. I'm still nervous about the race, but I'm excited for my training leading up to it. I'm so fortunate that I am able to do these crazy feats of athleticism and I'll get to the finish line one day at a time. California, here I come.
Thursday, July 23, 2015
Do or do not, there is no try
![]() |
| Hopefully I"ll be drinking some Firestone Walker beer post race! |
to receive a call/text from my mom about it which will surely change after this post. Let's cut to the chase, the suspense is killing me....I signed up for another 50 miler! Yep the seed was planted a few weeks ago at Bull and Bush and it germinated on Saturday as I made my first venture out on a trail run post 50k. By Monday I had convinced myself it was a good idea and by Tuesday afternoon I was entering in my credit card info and shirt size. Here are the details:
The North Face Endurance Challenge
Where: Golden Gate National Recreation Area San Francisco, CA
Length: duh..50 miles
Date: December 5, 2015
A couple big things stand out for me regarding this race. First of all, I've never done a long race (or really any race) in the fall. I tend to cram all of my running in to the spring/early summer. Because of that schedule most of my training begins in the fall and ramps up in the early spring. In the past this was largely due to the Ultimate frisbee season and needing to be sprint/frisbee focused May - October. With the series getting pushed earlier each year and my gradual fade away from competitive ultimate the fall is becoming more and more enticing for races. Also the thought of running long distance in September/October sounds so much more refreshing than June/July. I'm not used to logging a lot of miles in the summer and that's about to change quickly. I did a quick draft training plan and looks like it starts for real on Monday!
I'm planning on putting in a bit more effort with longer runs this go around. Especially working on nutrition for longer runs. While I feel successful with my food intake as of late, one good 50k isn't going to make me forget one not so good 50 miler. I really need to test out a lot of different food combos on longer runs and the only way to do that is to...test out a lot of different food combos on longer runs. I've got a couple training races I'm eyeing to help with this; the Black Squirrel Half and/or the Blue Sky Marathon in Fort Collins. I'm also trying to coordinate a 30ish mile run over Kenosha Pass into Breck with my bud Carissa.
Second standout for me is location. In looking at my running history, I've only really run races on trails I'm familiar with. Almost every race I've done I either trained or did a shorter race on the same trails. The two exceptions being Sage Burner 50k and the first time I did Quad Rock. Salida I ran the half prior to the marathon and I ran so much of the North Fork course prior to the 50 miler almost nothing was a surprise. Here I'm not only running on unfamiliar trails, but in a completely different state, at a different elevation, and a course profile much different than the mountains of Colorado.
In addition to a new terrain, I'm out of my comfort zone for support. North Fork was 40 miles outside of Denver. My lovely crew was able to load me in to a car, into a shower, and into bed without having to negotiate much else. California means a hotel or some other sort of lodging and a plane ride (+airport security). Oh yes, and a crew...40 miles is much different than a plane ride away. I checked in with some friends and got enough potential interest that I felt comfortable pulling the trigger and signing up for the race. True, convincing people to come to California in December isn't hard. However, it's not all fun and games since I need people to help support/pace/reassemble body parts at the airport. So if you are thinking it's a vacation, you've got to reevaluate.
All in all this is going to be a challenge and I'm excited for it. I'm excited to tackle another 50 miler and do it on what will be a beautiful course. I've been all talk the last few weeks about races so I'm glad I made the commitment and put a race on the calendar. Do or do not, there is no try.
Wednesday, June 17, 2015
To the fella over there with the hella good hair...
Quad Rock 2015 in the books. And to answer Jessi and anyone else who's asked recently what I think about when I run; I apparently think about Taylor Swift songs on repeat in my head.
What a difference a month makes! Despite the race starting at 5:30am the heat was already a factor early on in the race. Great training for North Fork, but oof, I'm not used to such high heat for this race. I swear the "shady" areas I remember from last year turned out not so shady this time around. How I missed May and it's cloud cover. Again, I did not envy the 50 milers I saw slogging their way back up the course, except for Ryan, he strolls along chatty and happy as always as if he didn't have another 20 miles to run.
First and foremost, I finished. Albeit not as pretty as I would have liked. No, no stitches this year. I had a couple "oh shit" almost falls but managed to save it before body connected to rock (I did sort of bounce off a tree at one point, much to the amusement of the person behind me). My achilles held up for most of the race but had a temper tantrum about 2 miles shy of the finish. I rolled in, sneaking by the Catt cheer squad, but sort of awkwardly running trying not to put any weight/pressure on the ball of my foot. Yes I know, not running and resting would have been better. Despite that I do feel 100% ready for the North Fork 50k, I don't think I'd have that feeling if it wasn't for this race.
I'm really happy with my uphill work. I focused a lot on strong uphill running/walking and kept really great form for most of the race. This is probably the first time I've run Quad Rock not hating myself halfway through one of the big climbs. I actually felt strong after each climb. I ran the first down hill pretty hard and then committed to taking it a bit slower for the rest to make sure I wasn't killing my body. All in all it was a really great race. I'm not happy about my achilles, but "thems are the shakes" as they say and all I can do is ice and rest as I get ready for North Fork.
Catt really killed it this race. We had a great discussion about nutrition and bonking. I was skeptical about his fueling for the race. He's decided to eat V's (his 16 month old son) mushed up baby food pouches. To his credit they sounded sort of delicious and savory, none of the sickly sweet Gu combinations. My concern for him was the three pouches combined only had about 180 calories total (versus one of my bars that had 180 on its own). He did supplement with Vfuel gel which didn't make his stomach feel good but probably helped give him the calories he needed.
I want to acknowledge again why I choose to run despite being injured. In running, and ultra running, there's a fine line between pushing your body past being comfortable and doing serious damage. I wholeheartedly admit that runners often get this wrong. We are usually the first to tell someone else to rest and rehab and the last to actually do it for ourselves. Becca Hall (an amazing runner and winner for the Bucket Hat division at Quad Rock) posted a great article recently from outdoor magazine called Running on Empty. It looks at a condition called Over Training Syndrome (OTS). It has made me think more about the choices I make running, when to run, when to rest, etc. I am proud of myself that despite my stubbornness, I did not put on cleats and play frisbee Monday or Tuesday. It is really hard to take time off when all you want to do is train more and get better, but it's a lot better in the long run and I know this. I choose to run Quad Rock because I knew that not running it would have resulted in me making worse decisions the next two weeks feeling like I needed to get ready for North Fork. The lesser of two evils I suppose.
Final Results: 6:08:39, 127/197 and 39 overall for women. They only had 3.2 beer at the finish so Catt and I hydrated with that and then got real beer on the way home.
What a difference a month makes! Despite the race starting at 5:30am the heat was already a factor early on in the race. Great training for North Fork, but oof, I'm not used to such high heat for this race. I swear the "shady" areas I remember from last year turned out not so shady this time around. How I missed May and it's cloud cover. Again, I did not envy the 50 milers I saw slogging their way back up the course, except for Ryan, he strolls along chatty and happy as always as if he didn't have another 20 miles to run.
First and foremost, I finished. Albeit not as pretty as I would have liked. No, no stitches this year. I had a couple "oh shit" almost falls but managed to save it before body connected to rock (I did sort of bounce off a tree at one point, much to the amusement of the person behind me). My achilles held up for most of the race but had a temper tantrum about 2 miles shy of the finish. I rolled in, sneaking by the Catt cheer squad, but sort of awkwardly running trying not to put any weight/pressure on the ball of my foot. Yes I know, not running and resting would have been better. Despite that I do feel 100% ready for the North Fork 50k, I don't think I'd have that feeling if it wasn't for this race.
I'm really happy with my uphill work. I focused a lot on strong uphill running/walking and kept really great form for most of the race. This is probably the first time I've run Quad Rock not hating myself halfway through one of the big climbs. I actually felt strong after each climb. I ran the first down hill pretty hard and then committed to taking it a bit slower for the rest to make sure I wasn't killing my body. All in all it was a really great race. I'm not happy about my achilles, but "thems are the shakes" as they say and all I can do is ice and rest as I get ready for North Fork.
![]() |
| Catt and I relaxing in Jessi Witt's back yard post race with Lory State Park in the background. |
I want to acknowledge again why I choose to run despite being injured. In running, and ultra running, there's a fine line between pushing your body past being comfortable and doing serious damage. I wholeheartedly admit that runners often get this wrong. We are usually the first to tell someone else to rest and rehab and the last to actually do it for ourselves. Becca Hall (an amazing runner and winner for the Bucket Hat division at Quad Rock) posted a great article recently from outdoor magazine called Running on Empty. It looks at a condition called Over Training Syndrome (OTS). It has made me think more about the choices I make running, when to run, when to rest, etc. I am proud of myself that despite my stubbornness, I did not put on cleats and play frisbee Monday or Tuesday. It is really hard to take time off when all you want to do is train more and get better, but it's a lot better in the long run and I know this. I choose to run Quad Rock because I knew that not running it would have resulted in me making worse decisions the next two weeks feeling like I needed to get ready for North Fork. The lesser of two evils I suppose.
Final Results: 6:08:39, 127/197 and 39 overall for women. They only had 3.2 beer at the finish so Catt and I hydrated with that and then got real beer on the way home.
Thursday, June 11, 2015
Achilles Heel (Quad Rock Take Two)
Achilles heel is a deadly weakness in spite of overall strength. I'm not the fastest runner, but I'm very determined. Sometimes my determination gets in the way of good judgment. Read on...
So if you've been anxiously awaiting a recap of Quad Rock you'll have to wait longer. The race was postponed due to the insane amounts of rain we got in Colorado in May. For the integrity of the trails they canceled the race and rescheduled it for June 14th.
As much as I try to be flexible and not worry too much about planning every detail, I really hate when things get out of sync with my plan. When I go on a run I like to know exactly how far I'm going, or at least close to it. When I am planning for a race I want to have most of my big training runs planned out. It's awesome to be able to incorporate a race as a long training run because you get to practice being in "race mode" and you get a fully aided training run. So Quad Rock was perfect, it was just over a month before the North Fork 50k so I could get in a good long training run in race mode.
Well now it's this weekend, just 2 weeks before North Fork. Not ideal for a race, but not too bad for an aided training run. I had already resigned myself to treating it as a training run and not a race. Meaning no time goals, just focusing on time on my feet running trails. It was tough for me to accept this. Every year I've run Quad Rock I've shaved huge amounts off my finish times. It was exciting to think I could continue with this pattern. But alas, that's not in the cards for me so my goal for Quad Rock is to survive without any gashes on my limbs.
To add another little wrench into the plan, because why not, I am also coming in to this race a bit injured. Perhaps the universe is telling me something or maybe I'm just clumsy, but this is the second year I've hurt myself 3 weeks before North Fork playing frisbee. I thought I was doing it right, not playing a tournament, not practicing, just playing good ol'league. It's no one's fault that I got hurt, but if we did want to point fingers I would probably point them at a certain person who shall remain nameless who pump faked instead of throwing it to my wide open cut in the endzone. Long story short I thought I ruined my knee. Flashes of similar movements from teammates that resulted in ACL tears flashed through my mind. Coupled with a sharp crunch feeling with pain in my knee and I thought my summer was over in an instant.
Thankfully my knee, and as far as I know all tendons and ligaments, are intact. After the fear of an ACL tear subsided and I was able to bend and extend my knee without trouble and walk on it the next day without pain. I did however do something to my Achilles tendon. (My googling and talk with a PT friend leads me to believe it's Achilles tendinitis). This is largely a symptom of a nagging injury I've had for awhile so I can't really blame anyone for this. The abrupt cut and plant on my leg just brought it all to head. A smart person would not run this weekend. A certain smart person weighed the pros and cons and decided to run this weekend and she's going to be super careful.
My achilles heel may be my determination to push through things despite the risks. I was determined to play frisbee league even though firsbee is probably the worst thing to do along side distance running. I was determined to keep running long distances throughout May with the constant rain driving me to put in a lot of long pavement miles on shoes that really need to be replaced. And I'm determined to run the North Fork 50k.
Here's why I'm choosing to run this weekend. I am running the North Fork 50k. Unless one of my legs gets chopped off and I don't have time to get a replacement leg I'm running this thing. Right now that's my last big race until the fall and it's the one I've been focused on since I didn't get in to Leadville. I see my choices as the following:
- Run Quad Rock, rest/taper the next two weeks, Run North Fork
- Skip Quad Rock, rest/taper the next two weeks plus 5 days, Run North Fork
- Skip Quad Rock and North Fork and be sad :(
The only real choice is between one and two and here's why I'm choosing option one. For now the pain is manageable and is actually better when I'm moving versus not moving. The thought of not running at all from today to North Fork is just not something I think I can do and feel ok about North Fork. I would much rather get in a long fast "hike" this weekend and then let myself rest a bit over doing nothing at all. I feel like I can do a better, more successful, job at resting if I do Quad Rock. If I don't do Quad Rock I will be tempted to do things like play frisbee and run on pavement which are two things that I should most definitely not do if I want to heal myself.
I know there are a lot of people shaking their heads at me. Just know that I understand the risks and if I were on the other side I would probably be trying to convince this person to just take the rest of the month off and heal. But my achilles heel is my determination(stubborness) and it may lead to my downfall or it may just be an Achilles Heel that will heal.
Injuries aside, it's supposed to be beautiful up in Fort Collins this weekend and it should be a really awesome race! I'm excited to continue working on my nutrition and power walking up hill and am hoping there's a PBR waiting for me at at least one of the aid stations!
Friday, April 24, 2015
Change
Most people who know me know that I don't like change. I like to stay in my comfort zone, where I am happy and where I know what to expect. So, suffice to say, right now I am way out of my comfort zone. I just moved out of my happy little highlands hood to south Broadway. Nothing has made that sink in more than my running schedule. My "running schedule" which has been non existent since the Platte River Half-Marathon.
I have many voices that live in my head. Two of the most vocal lately are the rationalizer and the risk taker. The rationalizer has been shouting ever since the risk taker made us move neighborhoods. The rationalizer says it's ok that I haven't run that much because I'm moving and I have to pack, and unpack, and clean. The risk taker is quietly calling "bullshit". I know the risk taker is right, the real reason I haven't been running as much is because I'm scared. I'm scared for the very silly, but real, reason that I don't have routes figured out near my new place. What if I run down a street without a side walk?! How do I pick the perfect route?! What if I'm only one block away from an amazing run?!
I was spoiled at my old place. I could do a 5, 6, 7.5, 10.5 mile run through quiet neighborhoods and around nice lakes and parks. I knew exactly where I needed to be when the listener limrick challenge came on. Now I have to take 5 years of habit and throw it out the window for something new.
Yes I realize I'm being ridiculous. Especially since I now live within a stones throw from Wash Park. Any given day there are hoards of runners zipping a long the path, a DIRT path! I don't even have to confine myself to mostly pavement. I can run on dirt. But there is something comforting in looking at my training schedule, seeing the number 6, and knowing I can get home from work, throw on stuff, and be out the door. There is no planning, just tie my shows and zip out. Routine is nice, when you have little time to get miles in during the week not having to over think your run eliminates one of the hurdles to getting a run in on days you don't feel like it.
Routine is also the enemy. By worrying about where to run I'm neglecting a real benefit discovering new running routes. It's so easy to get complacent and plateau your training when you are running the same thing every week. I've been running the same thing every week day for 5 years. My body can run on autopilot for 10ish miles in my neighborhood without skipping a beat. Having to expand my routes and look at new paths mean I'm not only challenging my body but also my brain. I often lament, after races, that I wish I had trained more for this or that. I now have a perfect, although forced by necessity, opportunity to do just that. Mix things up and see if I can see the results in my next races.

On that note a little update on my races.
I did the Platte River Half a few weekends ago. It was a lot of fun! Jill and I ran most of it together which was fun to have someone to chat with during the race. I finished in 1:59 which was my goal (to be under 2 hours).
My next race is Quad Rock coming up May 9th! Just a few weeks away. I'll have a pre-race post up before that, but for now I have to get my butt in gear and get some miles in.
I have many voices that live in my head. Two of the most vocal lately are the rationalizer and the risk taker. The rationalizer has been shouting ever since the risk taker made us move neighborhoods. The rationalizer says it's ok that I haven't run that much because I'm moving and I have to pack, and unpack, and clean. The risk taker is quietly calling "bullshit". I know the risk taker is right, the real reason I haven't been running as much is because I'm scared. I'm scared for the very silly, but real, reason that I don't have routes figured out near my new place. What if I run down a street without a side walk?! How do I pick the perfect route?! What if I'm only one block away from an amazing run?!
I was spoiled at my old place. I could do a 5, 6, 7.5, 10.5 mile run through quiet neighborhoods and around nice lakes and parks. I knew exactly where I needed to be when the listener limrick challenge came on. Now I have to take 5 years of habit and throw it out the window for something new.
Yes I realize I'm being ridiculous. Especially since I now live within a stones throw from Wash Park. Any given day there are hoards of runners zipping a long the path, a DIRT path! I don't even have to confine myself to mostly pavement. I can run on dirt. But there is something comforting in looking at my training schedule, seeing the number 6, and knowing I can get home from work, throw on stuff, and be out the door. There is no planning, just tie my shows and zip out. Routine is nice, when you have little time to get miles in during the week not having to over think your run eliminates one of the hurdles to getting a run in on days you don't feel like it.
Routine is also the enemy. By worrying about where to run I'm neglecting a real benefit discovering new running routes. It's so easy to get complacent and plateau your training when you are running the same thing every week. I've been running the same thing every week day for 5 years. My body can run on autopilot for 10ish miles in my neighborhood without skipping a beat. Having to expand my routes and look at new paths mean I'm not only challenging my body but also my brain. I often lament, after races, that I wish I had trained more for this or that. I now have a perfect, although forced by necessity, opportunity to do just that. Mix things up and see if I can see the results in my next races.

On that note a little update on my races.
I did the Platte River Half a few weekends ago. It was a lot of fun! Jill and I ran most of it together which was fun to have someone to chat with during the race. I finished in 1:59 which was my goal (to be under 2 hours).
My next race is Quad Rock coming up May 9th! Just a few weeks away. I'll have a pre-race post up before that, but for now I have to get my butt in gear and get some miles in.
Friday, December 12, 2014
Idiots out wandering around
Now that I officially put my name into the Leadville 100 Lottery I need to get some serious training in. To help keep myself more accountable than my kitchen calendar, I'm going to update the weeks training hopefully each Friday. I won't be linking these posts to social media (other than this first one) so if you're super curious about my training you'll have to come here by your self.
I have some newer posts in the queue that I'm working on, so have no fear my philosophical musing on running will reappear once I get my writing and editing on.
WEEK ONE
December 7 - 13
Sunday: I was in Minnesota for my cousins wedding. Sunday's training consisted of eating brunch, taking a nap on my sisters love seat, going out to a fat italian dinner at a place my mom called "pantaloonees", and watching A Christmas Story the Musical. Yep...successfully training for the day after Leadville. (Author's note I did run 4ish miles on Saturday so that's not too bad for vacation)
Monday: I flew into Denver at 6:50am and went straight to work. I took a nap in my car. Came home and helped my mom set up her new iphone. Fell asleep before 9pm. Hey rest is important for good racing!
Tuesday: HILL REPEATS! 8ish miles up Rooney Valley trail followed by 10 shorts (5 running hard downhill 5 running hard uphill). The weather was amazing. I felt good overall, not much knee pain on the downhill which is a bonus. I'm still way slower than everyone else, but it was nice to have people at the top to run with.
Wednesday: 4ish miles during lunch. It was a struggle, the day after hills always seems harder and lunch runs are tough for me. I had some commitments after work so I wanted to make sure I got a run in even if it was a bit shorter.
Thursday: 6miles, normal loop in the hood. Felt a lot better than Wednesday.
Friday: Today is a rest day, I've had two cups of Denver Bike Cafe coffee so I'm pretty jittery.
Saturday: My training sheet says 18miles, but I haven't built up my mileage enough for that. To avoid injury the current plan is to try and do 10-13 miles on trail and then eat a lot of cookies and drink delicious beer at the ugly sweater cookie exchange party.
I have some newer posts in the queue that I'm working on, so have no fear my philosophical musing on running will reappear once I get my writing and editing on.
Leadville 100 / 2015 Running Season Training
WEEK ONE
December 7 - 13
Sunday: I was in Minnesota for my cousins wedding. Sunday's training consisted of eating brunch, taking a nap on my sisters love seat, going out to a fat italian dinner at a place my mom called "pantaloonees", and watching A Christmas Story the Musical. Yep...successfully training for the day after Leadville. (Author's note I did run 4ish miles on Saturday so that's not too bad for vacation)
Monday: I flew into Denver at 6:50am and went straight to work. I took a nap in my car. Came home and helped my mom set up her new iphone. Fell asleep before 9pm. Hey rest is important for good racing!
Tuesday: HILL REPEATS! 8ish miles up Rooney Valley trail followed by 10 shorts (5 running hard downhill 5 running hard uphill). The weather was amazing. I felt good overall, not much knee pain on the downhill which is a bonus. I'm still way slower than everyone else, but it was nice to have people at the top to run with.
Wednesday: 4ish miles during lunch. It was a struggle, the day after hills always seems harder and lunch runs are tough for me. I had some commitments after work so I wanted to make sure I got a run in even if it was a bit shorter.
Thursday: 6miles, normal loop in the hood. Felt a lot better than Wednesday.
Friday: Today is a rest day, I've had two cups of Denver Bike Cafe coffee so I'm pretty jittery.
Saturday: My training sheet says 18miles, but I haven't built up my mileage enough for that. To avoid injury the current plan is to try and do 10-13 miles on trail and then eat a lot of cookies and drink delicious beer at the ugly sweater cookie exchange party.
Wednesday, October 22, 2014
Shortest Fat Season Ever
There isn't much time to rest in between ultimate and running season. It's helpful that ultimate season keeps me in well enough shape that I can transition into running a bit easier, but mentally it can be a challenge. I'm basically trading one time consuming hobby for another. Add on the million other fun things to do in Colorado over the winter and the off-season of ultimate can be more of a time drain than the on.
I was lucky though to have a really good run first run so the mental hurdle of starting training wasn't too tall. It did get me thinking and I'd like to revisit a topic I've covered before; how to motivate your self to train when you really just want to sit on your couch, drink a beer, and watch House Hunters International on Hulu.
There are a few things that have helped me get out on a run in the past that I'm hoping to harness over the next few months. With the lessons I learned from the 50miler last summer I know I need to put in some longer hours on the trails and it's a bit daunting to think of the training road ahead. So this post is more of a self motivator, but I hope you can find something that may aid you going forward.
Sign up for a race
A great way to start running again is to sign up for a race. It gives you an end goal in mind, a finish line for training if that's what you need. It also motivates you to run for some higher purpose than just to run. I have a couple races on my docket for next year; Salida Run Through Time Marathon, Quad Rock 25mile. In addition to those I am hoping to get another crack at the North Fork 50miler and of course there's Leadville or another 100mile race. Those are all well and good, but they seem so far away. Even Salida, which is typically in March, seems far enough away that taking training seriously right now is difficult. I am looking into race that fall somewhere in the next few months to get me out and running, but sometimes even signing up for a race isn't quite enough of a push to get out on a Tuesday night.
Incentives.
I've admitted before that podcasts are my guilty pleasure when road running. On days when I'm feeling really sluggish or unmotivated it's an incentive to catch up on episodes of Wait Wait Don't Tell Me. I typically only allow myself to listen to these podcasts on runs and I've found it to be quite a good motivator. I also recently picked up some great beer from Minnesota (Bells Two Hearted and a selection of Surly) with the caveat that I put in some miles before I can truly enjoy them.
Feeling shitty
While it might sound counter productive, whenever I'm feeling bad, especially stomach stuff bad, a run usually helps. I'm sure there's some sciencey stuff behind it, but all I know is if I'm feeling bad running it out often works. It's still difficult to go out on a run, but with the potential of feeling better and being able to do more fun things because you're feeling better is a nice perk. True, sometimes you don't feel any better, but I rarely feel any worse.
Being Weird
I read a quote that was posted by Grandma's Marathon on facebook "The days when you least feel like running are usually the days you need it the most". When all else fails I will sometimes, literally, chant "you're going for a run" in my car as I drive home from work. I don't let myself think about anything else and I just repeat, outloud, that I'm going on a run. I am not sure what people in the car next to me think, but it usually gets me focused enough on running that there is no other option when I get home but to put my shoes on. Perhaps by putting it out to the universe it's harder to say no when you unlock your front door?
Truth be told I'm about 50 parts excited and 50 parts terrified for what I'm hoping to accomplish next year so I'm also trying to harness that into a motivation to run. Right now I'm up to 8miles for a long run which means I have a ways to go, but I'll get there. If anything, I've started a google doc for Leadville so hit me up if you want to join my crew and I'll put your name on the list.
Monday, June 9, 2014
Getting rid of setbacks, it's ok to divert
Life is full of things that get in the way of the plan, or sometimes even things that completely blow your plan up into little pieces. Thankfully for me my most recent occurrence is the former and not the latter, but it can still be frustrating.
Against my better judgment, as the start of any good story begins, I played ultimate last week. I was at a tryout for a team called Mesteno and stupidly rolled my ankle.
I say "stupidly" because I didn't roll it doing something awesome. I did it after I stopped and went to turn around to go back in line. I have pretty loose ankles, but I felt a pop as it happened. I immediately felt pain, hobbled over to the sideline and put it up with ice. The ice in this case was an ice block and a Tecate compliments of Tower. Tower made me drink the Tecate that was on my foot later, which I was ok with.
I rested a bit and then my next stupid decision was to go out and play more. It actually felt ok. I could "feel" it, but it wasn't hurting me to do normal frisbee motions. I iced more when I got home and did the typical athelete self diagnosis of looking up "how to treat a rolled ankle" on the internet. From my research I think I have a mild sprain. There wasn't significant swelling, but there's a little bruising. So ice, arnica, and rest. I'm not going to lie, it hurt the next day, but at least it didn't really look any worse.
It's been almost a week now and I'm happy to report that things are doing better in the ankle department. I purchased a beefy ankle brace for future ultimate endeavors which, if anything, puts my mind at ease. I went on a long training run on Saturday (22miles) at the race course and it felt fine. There were little pains here and there, but nothing more than the usual. The run allowed me lots of time to think about what happened is I realized that I hate the term "setback".
I don't like the word setback. On face value it oozes negativity. Hearing setback makes me immediately think, "it's going to set you back and that's bad". In reality, training is full of things that divert you from the exact plan; weather, sickness, injury, or forgetting your shoes. When something happens that disrupts training it's too easy to focus on the negative and what happened. It's most important to focus on what you can do in the moment and in the future. On Molly Brown we talked a lot about relevance/irrelevance, or things we have control over and things we don't. Being able to separate it out and realign your focus into what you can do in that moment means you're thinking with a forward motion in mind. It's irrelevant to focus on rolling my ankle, it is relevant for me to focus on how to protect it in the future and how I can heal myself to get out and start running again. Dwelling on it as a setback only focuses on what happened. I would rather focus on what can I do next.
The word setback immediately sounds like focusing on the past, or focusing on something I cannot change. Even saying the word implies the past. I can't change that I hurt my ankle, but I can focus on what to do today and tomorrow to continue to prepare for my race. So I took a day off, I kept icing, I bought a brace, then I put socks on, laced up my shoes, and ran.
Rolling my ankle caused me to modify my training for a few days, but there are countless other things that have done that throughout the course of my running career. Saying setback means I can't move forward, but acknowledging that sometimes things disrupt your training gives you the control to keep moving forward. Therefore I don't see this as a setback, I just see it as training. Just as a thunderstorm keeping you inside for the afternoon, or a deadline at work that has to get done when you're training for a race it's all part of the package. Maybe that's why training programs are so long, because we all know that at least once or twice you're week plan is going to get thrown and you have to adapt.
*I'm less than a month out from race day!
Against my better judgment, as the start of any good story begins, I played ultimate last week. I was at a tryout for a team called Mesteno and stupidly rolled my ankle.
I say "stupidly" because I didn't roll it doing something awesome. I did it after I stopped and went to turn around to go back in line. I have pretty loose ankles, but I felt a pop as it happened. I immediately felt pain, hobbled over to the sideline and put it up with ice. The ice in this case was an ice block and a Tecate compliments of Tower. Tower made me drink the Tecate that was on my foot later, which I was ok with.
I rested a bit and then my next stupid decision was to go out and play more. It actually felt ok. I could "feel" it, but it wasn't hurting me to do normal frisbee motions. I iced more when I got home and did the typical athelete self diagnosis of looking up "how to treat a rolled ankle" on the internet. From my research I think I have a mild sprain. There wasn't significant swelling, but there's a little bruising. So ice, arnica, and rest. I'm not going to lie, it hurt the next day, but at least it didn't really look any worse.
It's been almost a week now and I'm happy to report that things are doing better in the ankle department. I purchased a beefy ankle brace for future ultimate endeavors which, if anything, puts my mind at ease. I went on a long training run on Saturday (22miles) at the race course and it felt fine. There were little pains here and there, but nothing more than the usual. The run allowed me lots of time to think about what happened is I realized that I hate the term "setback".
I don't like the word setback. On face value it oozes negativity. Hearing setback makes me immediately think, "it's going to set you back and that's bad". In reality, training is full of things that divert you from the exact plan; weather, sickness, injury, or forgetting your shoes. When something happens that disrupts training it's too easy to focus on the negative and what happened. It's most important to focus on what you can do in the moment and in the future. On Molly Brown we talked a lot about relevance/irrelevance, or things we have control over and things we don't. Being able to separate it out and realign your focus into what you can do in that moment means you're thinking with a forward motion in mind. It's irrelevant to focus on rolling my ankle, it is relevant for me to focus on how to protect it in the future and how I can heal myself to get out and start running again. Dwelling on it as a setback only focuses on what happened. I would rather focus on what can I do next.
The word setback immediately sounds like focusing on the past, or focusing on something I cannot change. Even saying the word implies the past. I can't change that I hurt my ankle, but I can focus on what to do today and tomorrow to continue to prepare for my race. So I took a day off, I kept icing, I bought a brace, then I put socks on, laced up my shoes, and ran.
Rolling my ankle caused me to modify my training for a few days, but there are countless other things that have done that throughout the course of my running career. Saying setback means I can't move forward, but acknowledging that sometimes things disrupt your training gives you the control to keep moving forward. Therefore I don't see this as a setback, I just see it as training. Just as a thunderstorm keeping you inside for the afternoon, or a deadline at work that has to get done when you're training for a race it's all part of the package. Maybe that's why training programs are so long, because we all know that at least once or twice you're week plan is going to get thrown and you have to adapt.
*I'm less than a month out from race day!
Friday, February 22, 2013
Dealing with Disappointments
Running can be a lot of really positive things, but sometimes you can get really disappointed. There are varying levels of disappointment; a bad training run, some missed days of running, or a bad race. A race day disappointment is usually the one the lingers the most. Why wouldn't it be? A day after a bad training run you're pretty much over it because you've moved on to the next training run. But a race is THE RACE that you were training for and the next day you've got nothing but sore muscles, a t-shirt, and a medal to keep you company. There might be another race, but it's just far enough away to make you question whether or not you can get a refund for your entry fee.
In thinking about why race disappointments weigh on us more than training disappointments I started to think about my mentality going into a race vs a training run. In the training run you are thinking about your work and approach towards a race. Your miles are little nuggets of goodness that you bank, and on the day of the race if you did your work, you have enough nuggets to get you through (and you work hard enough that you use all of them). So if you have a bad day running, those are still deposits into your race day bank account. Sometimes bad runs are even better, because it teaches you as a runner that you can push your body through something and finish. I know I've relied on that at the end of the race, reminding myself how bad I may have felt that one training day and I made it. So a bad day running is just that; a bad day running. You take a shower, you eat some food, you move on.
A race, on the other hand, seems like so much more than just a bad day running. A race is the totality of all your running and training up until that point. So it's not so much a disappointment in a run, it's a disappointment with the weight of months of training on your shoulder. It's not one disappointing run, it is disappointment of all your runs. You question what you did or did not do. Having a bad race hurts more because in our minds we make it a lot more than just about that race. You wonder, did you invest all your foundation nuggets into sub-prime mortgages? In short, it really sucks to think you didn't do all that you could do before a race and you question any missed runs, any runs cut short, or even wonder why you skipped some of the fun stuff to go running.
How do you deal with these disappointments? As runners, we obviously figure something out because we continue to sign up for races and run in the rain so the trick is using the disappointment to your advantage. There are two types of race day disappointments; those you feel after the race and those you feel during the race. I've been "lucky" enough to experience both, and both have translated into something positive here's how:
1. Disappointment at the end of a race...
Let me first say you sort of know when you're going to be bummed at the end of the race. Something in your brain or your body knows that when you finish you're not going to finish in the way you imagined. Last year I ran the Canyonlands Half Marathon. It runs along side the Colorado River through the Canyon into Moab. It is a beautiful race and fairly easy. It is on the road and mostly downhill with a section that cuts through town. It's a great race to get a PR and I think a lot of people go into the race with that mentality. I was super excited to run it well. I had finally broke 2hrs for a half marathon the spring before so I was focused on getting somewhere around 1:50. The weather was so/so, no rain or snow but a pretty heavy wind ripped up through the canyon so that was going to be a challenge. At some points it was so strong I had to literally hold on to my hat to keep it from falling off and disappearing behind me. I didn't feel super well as I got started, but after about 2 miles in I fell into a groove. I was sticking with my pace I needed, even a bit faster so I felt ok despite my body not really feeling awesome. I remember I kept going through waves of feeling fast and great to feeling slow and tired. The last one hit as I came out of the canyon onto the road and it stuck. I knew I was cutting it close pace wise, but it didn't really set in until I saw the clock at the finish line and it was already at 2 hours. I knew I didn't have enough of a "gun time" cushion to even get me under 2 hours so I crossed the finish line feeling really bummed out. At least they had some fun chips to snack on and I nursed some of the disappointment with beers and disc golf in the evening.
At first I blamed the typical offenders - the weather sucked, the wind was really strong and it meant I had to work harder to go forward, I felt crappy to begin with so it just "wasn't my day", and that stupid section along the highway is a pain in the butt. Those are all factors that played into how I did, but I started thinking more about my training. Yes I had a goal of under 2 hours (preferably near 1:50). Yes I ran leading up to the race so I had the miles in. But...on all my training runs I never really made an effort to train for 1:50. I just trained to run a half-marathon. Most runners know that after a certain point you have to switch your training from being "just finish the race" to a goal time. This requires more than just saying your going to run it in this amount of time, you actually need to incorporate that into your training runs. So really, I finished the race exactly how I had trained for it. In fact I probably did a little better than I should have considering I never really trained to run at the pace I did. End of the race disappointments are tough, but they put into prospective what you expected to happen at the end of the race. I know now if I want to hit that time I need to do some pace runs and train to run it that fast not hope I can pull out that fast of a run.
2. Disappointment during the race...
It's really hard to get disappointed during a race and even more so when you have a lot more ground to cover before you can finish. I haven't had to face this feeling at mile 1 of a marathon thankfully, but I have gone through it and I think it's made me a stronger runner, especially with trail runs. I have heard that some people will just quit a marathon if they are no longer on their Boston Qualifying pace. I have no problem with that, we all run for different reasons. I don't think I could ever be that person just because if I've come that far I'm going to finish the race because I at least want to eat as much of the snacks at the end as I can. There are also some races where you don't get your t-shirt unless you finish and I like to hoard t-shirts.
When I was running Grandma's Marathon last year I wanted to badly to break 4 hours. I had been trying to the last couple years only to shave a minute or two off my time. I had done several trail races and felt like I was pretty strong and could do it. I started out with the pacer and was sticking with him for most of the race. But I got to about mile 18 and things started to go downhill. My legs stopped working and I was finding it harder to catch up with the pacer after the water stations. I finally couldn't do it and I knew that I wasn't going to be able to keep the pace I needed to break 4 hours. I was bummed, and I let myself feel bummed for about 2 minutes and then I kept going. I passed a bunch of college kids cheering the runners on holding out beers in a feeble attempt to get us to take a swig and I thought "what the heck" so I ran over and downed a beer. Once I did that I decided to just have fun the rest of the race and not worry about it. I'd be lying if I said my legs didn't hurt the rest of the way but the 4 hour number didn't seem to bother me that much anymore. I still managed to finish with an identical time from the year before and while I didn't hit my mark I turned the rest of the race into having fun and it worked. Yes I still want to break 4 hours, but sometimes you just got to let it go and drink a free PBR.
My point for all of this rambling is, we all get disappointed at some point running. Whether you're just out there on a Saturday going for a run or you're doing a race. You can plan perfectly for a race and get slammed at the start line with snow/rain/wind/stomach cramps/you name it. Bad races can teach us what we need to do in our training (that we might not see unless we blow up during a race). Bad races can also remind us that it's not all about your fastest time or breaking your PR it's about enjoying yourself for the 1/2/3/4....9 hours you're out running and you don't have to be anyone but you running. You don't have to make copies or fold your laundry. You don't even have to pick up after yourself (unless you're on the trail dude, leave no trace!). It's rare in life that we get that much undisturbed time to be within our selves and only for ourselves and if someone gives you beer along the way; bonus.
In thinking about why race disappointments weigh on us more than training disappointments I started to think about my mentality going into a race vs a training run. In the training run you are thinking about your work and approach towards a race. Your miles are little nuggets of goodness that you bank, and on the day of the race if you did your work, you have enough nuggets to get you through (and you work hard enough that you use all of them). So if you have a bad day running, those are still deposits into your race day bank account. Sometimes bad runs are even better, because it teaches you as a runner that you can push your body through something and finish. I know I've relied on that at the end of the race, reminding myself how bad I may have felt that one training day and I made it. So a bad day running is just that; a bad day running. You take a shower, you eat some food, you move on.
A race, on the other hand, seems like so much more than just a bad day running. A race is the totality of all your running and training up until that point. So it's not so much a disappointment in a run, it's a disappointment with the weight of months of training on your shoulder. It's not one disappointing run, it is disappointment of all your runs. You question what you did or did not do. Having a bad race hurts more because in our minds we make it a lot more than just about that race. You wonder, did you invest all your foundation nuggets into sub-prime mortgages? In short, it really sucks to think you didn't do all that you could do before a race and you question any missed runs, any runs cut short, or even wonder why you skipped some of the fun stuff to go running.
How do you deal with these disappointments? As runners, we obviously figure something out because we continue to sign up for races and run in the rain so the trick is using the disappointment to your advantage. There are two types of race day disappointments; those you feel after the race and those you feel during the race. I've been "lucky" enough to experience both, and both have translated into something positive here's how:
1. Disappointment at the end of a race...
Let me first say you sort of know when you're going to be bummed at the end of the race. Something in your brain or your body knows that when you finish you're not going to finish in the way you imagined. Last year I ran the Canyonlands Half Marathon. It runs along side the Colorado River through the Canyon into Moab. It is a beautiful race and fairly easy. It is on the road and mostly downhill with a section that cuts through town. It's a great race to get a PR and I think a lot of people go into the race with that mentality. I was super excited to run it well. I had finally broke 2hrs for a half marathon the spring before so I was focused on getting somewhere around 1:50. The weather was so/so, no rain or snow but a pretty heavy wind ripped up through the canyon so that was going to be a challenge. At some points it was so strong I had to literally hold on to my hat to keep it from falling off and disappearing behind me. I didn't feel super well as I got started, but after about 2 miles in I fell into a groove. I was sticking with my pace I needed, even a bit faster so I felt ok despite my body not really feeling awesome. I remember I kept going through waves of feeling fast and great to feeling slow and tired. The last one hit as I came out of the canyon onto the road and it stuck. I knew I was cutting it close pace wise, but it didn't really set in until I saw the clock at the finish line and it was already at 2 hours. I knew I didn't have enough of a "gun time" cushion to even get me under 2 hours so I crossed the finish line feeling really bummed out. At least they had some fun chips to snack on and I nursed some of the disappointment with beers and disc golf in the evening.
At first I blamed the typical offenders - the weather sucked, the wind was really strong and it meant I had to work harder to go forward, I felt crappy to begin with so it just "wasn't my day", and that stupid section along the highway is a pain in the butt. Those are all factors that played into how I did, but I started thinking more about my training. Yes I had a goal of under 2 hours (preferably near 1:50). Yes I ran leading up to the race so I had the miles in. But...on all my training runs I never really made an effort to train for 1:50. I just trained to run a half-marathon. Most runners know that after a certain point you have to switch your training from being "just finish the race" to a goal time. This requires more than just saying your going to run it in this amount of time, you actually need to incorporate that into your training runs. So really, I finished the race exactly how I had trained for it. In fact I probably did a little better than I should have considering I never really trained to run at the pace I did. End of the race disappointments are tough, but they put into prospective what you expected to happen at the end of the race. I know now if I want to hit that time I need to do some pace runs and train to run it that fast not hope I can pull out that fast of a run.
2. Disappointment during the race...
It's really hard to get disappointed during a race and even more so when you have a lot more ground to cover before you can finish. I haven't had to face this feeling at mile 1 of a marathon thankfully, but I have gone through it and I think it's made me a stronger runner, especially with trail runs. I have heard that some people will just quit a marathon if they are no longer on their Boston Qualifying pace. I have no problem with that, we all run for different reasons. I don't think I could ever be that person just because if I've come that far I'm going to finish the race because I at least want to eat as much of the snacks at the end as I can. There are also some races where you don't get your t-shirt unless you finish and I like to hoard t-shirts.
When I was running Grandma's Marathon last year I wanted to badly to break 4 hours. I had been trying to the last couple years only to shave a minute or two off my time. I had done several trail races and felt like I was pretty strong and could do it. I started out with the pacer and was sticking with him for most of the race. But I got to about mile 18 and things started to go downhill. My legs stopped working and I was finding it harder to catch up with the pacer after the water stations. I finally couldn't do it and I knew that I wasn't going to be able to keep the pace I needed to break 4 hours. I was bummed, and I let myself feel bummed for about 2 minutes and then I kept going. I passed a bunch of college kids cheering the runners on holding out beers in a feeble attempt to get us to take a swig and I thought "what the heck" so I ran over and downed a beer. Once I did that I decided to just have fun the rest of the race and not worry about it. I'd be lying if I said my legs didn't hurt the rest of the way but the 4 hour number didn't seem to bother me that much anymore. I still managed to finish with an identical time from the year before and while I didn't hit my mark I turned the rest of the race into having fun and it worked. Yes I still want to break 4 hours, but sometimes you just got to let it go and drink a free PBR.
My point for all of this rambling is, we all get disappointed at some point running. Whether you're just out there on a Saturday going for a run or you're doing a race. You can plan perfectly for a race and get slammed at the start line with snow/rain/wind/stomach cramps/you name it. Bad races can teach us what we need to do in our training (that we might not see unless we blow up during a race). Bad races can also remind us that it's not all about your fastest time or breaking your PR it's about enjoying yourself for the 1/2/3/4....9 hours you're out running and you don't have to be anyone but you running. You don't have to make copies or fold your laundry. You don't even have to pick up after yourself (unless you're on the trail dude, leave no trace!). It's rare in life that we get that much undisturbed time to be within our selves and only for ourselves and if someone gives you beer along the way; bonus.
Monday, February 18, 2013
Race Update
In my rant against Google and their silly decision to have no way to recover draft emails I mentioned writing an update on upcoming races and mileage. So here it is.
My Mileage has been so/so. I started a new job in December and that threw my running for a bit of a loop. I took for granted the leisurely runs I was able to take anytime I wanted to during the day. But I'm proud to say I've stuck with Hill Repeats and have kept up enough of a running schedule to feel like I'm not too far behind in the marathon training. Which brings me to races:
I wasn't able to do the snow shoe race in January. It ended up being the same weekend as a hut trip. Here's a picture:
It's probably for the better since I had never done a snow shoe race and I was able to instead get out on my new skis. My new skis which are totally awesome and I love them and can't wait to ski on them more.
I made the decision not to do the Moab Half-Marathon nor Grandma's Marathon this year. The Moab race just ended up conflicting with the Salida race and in choosing between the two I wanted to focus on the Salida Marathon as opposed to a road half-marathon. Which is good considering the additional races I've committed myself to. It was harder to not do Grandma's Marathon. It's such a special race to me for many reasons. But I know I'll be back so I'm not too bummed. I was planning on doing it if my sister had signed up, but we picked a different race instead. Again timing was a big factor. Jeremiah is running a 100 miler at the end of June and we're traveling to Virginia in July for his brother's wedding so a fall trip to Minnesota will be easier to coordinate provided I can fit it into the ultimate season...
Here is why my race outlook for this spring looks like:
Salida Run Through Time Marathon
Distance: 26.2miles
Date: March 9th, 2013
Goal Time: 5:30hours
I'm excited and nervous for this race. I haven't gotten in as much trail running as I would have liked for this race. But I have improved my uphill running via Hill Repeats so that's a good thing. I've gotten in one good 15ish mile trail run and I'm planning on getting in at least 2 more long runs between 15 and 20 miles which will be tough cause they will need to happen in the next two weekends. (news alert, I did get an 18mile road run in this past weekend so that made me feel a lot better!). My goal time may be a little ambitious considering my training, but I'll see how my next two long runs go and may need to adjust. I do think I can do it. My last two half marathon times for this course were in the 2:30hr range so giving myself an additional 30min buffer should be ok. The Quad Rock 25miler took me 6:30hrs last year, but it's a considerably tougher race. I think 5:30 is a good goal, but as long as I can get under 6 I will be happy.
Quad Rock 25miler
Distance: 25miles
Date: May 11th
Goal Time: 6:15hrs
I think this will be a really good race for me this year. Knowing the course now I can anticipate when I can run and when I need to walk. I remember there were some steep sections and it helps to know it and know roughly how long they are so I can feel comfortable walking. I just really like this race and had a blast last year. They had a local brewery at the finish and a bonfire so I am looking forward to hanging out to cheer Jeremiah on as he comes in for the 50 miler. The course will have a different look since they dealt with some pretty gnarly forest fires in the park last summer.
War Eagle Races 50K
Distance: 50K (31.25miles)
Date: June 2
Goal Time: 6:30hrs
So this is my "big race" of the season. A 50k which marks my first toe dip into the ultra running circuit. I know this because when I registered I got an offer to subscribe to ultra running. I'm actually really excited about this race. It was either this one or a 50k in Gunnison and because my sister decided to sign up for the 25k I signed up for the 50k. It's in Arkansas so I have the whole altitude "blood doping" thing to my advantage, but I'm still nervous. That's 5 miles longer than I've ever ran before and at the end of a marathon I could hardly think of running another 5 miles. It's hard enough walking the half a mile to my parents car parked at the Methodist Church. But I've already put the feelers out to people who have done some of these runs to figure out my training and my food intake for the race. Despite what my friend Ryan does, I think I'm going to not opt for the "all gu" nutrition and eat the shit out of some gummi bears and pretzels at the aid stations. I have an ambitious goal time. After the Salida race I may tweak it a bit. But really, my only comparison race is the Quad Rock and Jeremiah keeps saying that one is way harder than [fill in the blank with any race you can think of] so I think this is an ok time to shoot for. I have a while to train and I will have already bagged to long trail run/races before hand at altitude so really...what's 5 more miles between friends?
My Mileage has been so/so. I started a new job in December and that threw my running for a bit of a loop. I took for granted the leisurely runs I was able to take anytime I wanted to during the day. But I'm proud to say I've stuck with Hill Repeats and have kept up enough of a running schedule to feel like I'm not too far behind in the marathon training. Which brings me to races:
I wasn't able to do the snow shoe race in January. It ended up being the same weekend as a hut trip. Here's a picture:
It's probably for the better since I had never done a snow shoe race and I was able to instead get out on my new skis. My new skis which are totally awesome and I love them and can't wait to ski on them more.
I made the decision not to do the Moab Half-Marathon nor Grandma's Marathon this year. The Moab race just ended up conflicting with the Salida race and in choosing between the two I wanted to focus on the Salida Marathon as opposed to a road half-marathon. Which is good considering the additional races I've committed myself to. It was harder to not do Grandma's Marathon. It's such a special race to me for many reasons. But I know I'll be back so I'm not too bummed. I was planning on doing it if my sister had signed up, but we picked a different race instead. Again timing was a big factor. Jeremiah is running a 100 miler at the end of June and we're traveling to Virginia in July for his brother's wedding so a fall trip to Minnesota will be easier to coordinate provided I can fit it into the ultimate season...
Here is why my race outlook for this spring looks like:
Salida Run Through Time Marathon
Distance: 26.2miles
Date: March 9th, 2013
Goal Time: 5:30hours
I'm excited and nervous for this race. I haven't gotten in as much trail running as I would have liked for this race. But I have improved my uphill running via Hill Repeats so that's a good thing. I've gotten in one good 15ish mile trail run and I'm planning on getting in at least 2 more long runs between 15 and 20 miles which will be tough cause they will need to happen in the next two weekends. (news alert, I did get an 18mile road run in this past weekend so that made me feel a lot better!). My goal time may be a little ambitious considering my training, but I'll see how my next two long runs go and may need to adjust. I do think I can do it. My last two half marathon times for this course were in the 2:30hr range so giving myself an additional 30min buffer should be ok. The Quad Rock 25miler took me 6:30hrs last year, but it's a considerably tougher race. I think 5:30 is a good goal, but as long as I can get under 6 I will be happy.
Quad Rock 25miler
Distance: 25miles
Date: May 11th
Goal Time: 6:15hrs
I think this will be a really good race for me this year. Knowing the course now I can anticipate when I can run and when I need to walk. I remember there were some steep sections and it helps to know it and know roughly how long they are so I can feel comfortable walking. I just really like this race and had a blast last year. They had a local brewery at the finish and a bonfire so I am looking forward to hanging out to cheer Jeremiah on as he comes in for the 50 miler. The course will have a different look since they dealt with some pretty gnarly forest fires in the park last summer.
War Eagle Races 50K
Distance: 50K (31.25miles)
Date: June 2
Goal Time: 6:30hrs
So this is my "big race" of the season. A 50k which marks my first toe dip into the ultra running circuit. I know this because when I registered I got an offer to subscribe to ultra running. I'm actually really excited about this race. It was either this one or a 50k in Gunnison and because my sister decided to sign up for the 25k I signed up for the 50k. It's in Arkansas so I have the whole altitude "blood doping" thing to my advantage, but I'm still nervous. That's 5 miles longer than I've ever ran before and at the end of a marathon I could hardly think of running another 5 miles. It's hard enough walking the half a mile to my parents car parked at the Methodist Church. But I've already put the feelers out to people who have done some of these runs to figure out my training and my food intake for the race. Despite what my friend Ryan does, I think I'm going to not opt for the "all gu" nutrition and eat the shit out of some gummi bears and pretzels at the aid stations. I have an ambitious goal time. After the Salida race I may tweak it a bit. But really, my only comparison race is the Quad Rock and Jeremiah keeps saying that one is way harder than [fill in the blank with any race you can think of] so I think this is an ok time to shoot for. I have a while to train and I will have already bagged to long trail run/races before hand at altitude so really...what's 5 more miles between friends?
Wednesday, February 13, 2013
Running On Vacation: or a devil, another devil, and a demi-god
Running on vacation is hard. Basically anytime you get out of the rhythm of your "normal routine" it is hard to get back. For anyone who struggles with staying on a schedule of regular running, vacation is guaranteed to throw you for a loop. Basically there are three ways to look at running on vacation:
- The devil on your shoulder
- The other devil on your shoulder
- A demi-god (or demon, or idol, or joe bag o'donuts)
The first devil on your shoulder is the one that makes you feel bad for not running while you are on vacation. Of course you don't want to run while on vacation because it is much more fun to sleep in, roll out of bed and drink coffee in your pjs and hang out with your vacation friends/family/or no one. Maybe you'll go shopping, maybe site-seeing, maybe it's been an hour since you last ate so you go eat more. Basically vacations have their own timelines so it is hard to go against that timeline because sometimes you just "go where the wind takes you". You also don't want to be the buzz kill that ruins the vacation schedule because you are going out running. Sorry everyone, that trip to see the brewery sounds fun, but can you all wait 2 hours I have to go running. The devil on your shoulder says things like "you better go running, your family will be around when you get back", and "wow second breakfast, you better run that off later". If you listen to it you probably miss out on something everyone is doing, or you pass on that 3rd game of wii bowling and a 4th Bells IPA the night before because you have to run 15 miles the next day. But that devil reminds you as you strap on your shoes while everyone else is going to wander around Main Street "go on that run because if you don't you'll feel it at mile 22 in your next marathon".
The second devil doesn't give a shit if you run, in fact it encourages you not to run. It also wants to roll out of bed and watch that cable TV you don't get at home, those donuts that just appear on the counter from your dad, the craft beers only available in the Central Time Zone. You shouldn't run because you might miss something really really fun. Impromptu air rifle shooting in the backyard, a trip to Town to get food, a visit to some iconic place/statute/brewery. It reminds you that you can afford to miss a couple days of running so you should just live large and really embrace vacation. This devil says things like "why run when you can drink some Growler Beer and play yatzee" and "you spent all this money and time to visit your family/friends/place why do you want to spend it running?". If you listen to it you will probably have a lot of fun, and maybe a hangover. You will also have a hard time getting back in your groove when you get back home. When you have the small inclination to lace up your shoes that devil reminds you "don't go on that run, if you do you might feel better at mile 22, but what will you miss in the process?"
The demi-god/demon/idol/Joe Bags isn't powerful enough to sit on your shoulder like a devil or an angel. Joe Bags just sort of hangs out and throws out other options. Of course you don't want to spend your whole vacation running, but you also don't want to come back and realize you forgot how to tie your shoe laces. Old Joe Bags says "hey your nephews are taking a nap you could squeeze in some hill work", or "your sister wants to go on a run so you could do that with her". Joe Bags doesn't care how many miles you run, just fit it into when you have time and it works with what's going on around you. Joe Bags never gives you a disapproving look if you have another beer, but he does laugh a little when you slog through a short run the next day because of it. Don't mistake Joe Bags for a softy, if there is a time and a place to fit the run into your vacation he'll remind you of it. But he won't try and manufacture time if it's not there. He'll be there at mile 22 in your next marathon helping you forget the pain in your legs saying "Remember when you visited such and such place, how much fun it was?"
You can really choose which one you listen to. A lot of it depends on what you are trying to get out of running. If you are sponsored by Newton and you're trying to win part of the purse in the next race then you might error on the side of Devil 1. If you still have a long couple months of training to go before your race you might error on the side of Devil 2. But a lot of us run because we like running. We sign up for races because it helps us keep running on days we don't feel like it, we love new shirts, we love to visit new places, or we love hearing 100's of watches beep simultaneously at each mile. Running and training can feel like a job sometimes, so it's not a bad thing to take a vacation from running or just a vacation from a strict schedule. I remember taking a trip to Arkansas before my first marathon for my nephews baptism. The trip fell the weekend the training plan scheduled the long run, the 18 miler. There really was no opting out of that, if you've ever run a marathon you know how important it is to knock out those long runs, especially at the end of your training. But the heat of Arkansas in the summer required the run to start early and it also got me out of having to do picnic party prep. Alternatively, I just went to visit Arkansas again at Christmas and didn't stress out about staying with my running schedule. I was still able to run a couple days and didn't feel like a total dud when I got home. The miles sort of felt like "bonus" miles that I didn't have to do, but got to do.
Missing a couple runs will not ruin your race, nor will a couple of days a marathon champ make. It's your whole training schedule and the totality of the runs you've done. No don't be a total slog and do nothing for 2 weeks just because your on vacation. But you can make your running part of your vacation and if you can you should.
The demi-god/demon/idol/Joe Bags isn't powerful enough to sit on your shoulder like a devil or an angel. Joe Bags just sort of hangs out and throws out other options. Of course you don't want to spend your whole vacation running, but you also don't want to come back and realize you forgot how to tie your shoe laces. Old Joe Bags says "hey your nephews are taking a nap you could squeeze in some hill work", or "your sister wants to go on a run so you could do that with her". Joe Bags doesn't care how many miles you run, just fit it into when you have time and it works with what's going on around you. Joe Bags never gives you a disapproving look if you have another beer, but he does laugh a little when you slog through a short run the next day because of it. Don't mistake Joe Bags for a softy, if there is a time and a place to fit the run into your vacation he'll remind you of it. But he won't try and manufacture time if it's not there. He'll be there at mile 22 in your next marathon helping you forget the pain in your legs saying "Remember when you visited such and such place, how much fun it was?"
You can really choose which one you listen to. A lot of it depends on what you are trying to get out of running. If you are sponsored by Newton and you're trying to win part of the purse in the next race then you might error on the side of Devil 1. If you still have a long couple months of training to go before your race you might error on the side of Devil 2. But a lot of us run because we like running. We sign up for races because it helps us keep running on days we don't feel like it, we love new shirts, we love to visit new places, or we love hearing 100's of watches beep simultaneously at each mile. Running and training can feel like a job sometimes, so it's not a bad thing to take a vacation from running or just a vacation from a strict schedule. I remember taking a trip to Arkansas before my first marathon for my nephews baptism. The trip fell the weekend the training plan scheduled the long run, the 18 miler. There really was no opting out of that, if you've ever run a marathon you know how important it is to knock out those long runs, especially at the end of your training. But the heat of Arkansas in the summer required the run to start early and it also got me out of having to do picnic party prep. Alternatively, I just went to visit Arkansas again at Christmas and didn't stress out about staying with my running schedule. I was still able to run a couple days and didn't feel like a total dud when I got home. The miles sort of felt like "bonus" miles that I didn't have to do, but got to do.
Missing a couple runs will not ruin your race, nor will a couple of days a marathon champ make. It's your whole training schedule and the totality of the runs you've done. No don't be a total slog and do nothing for 2 weeks just because your on vacation. But you can make your running part of your vacation and if you can you should.
Friday, November 9, 2012
Running Motivation
Mileage total this week (Sunday-Friday) = 22.5miles
Total Miles since Ultimate Season ended = 35.5miles
I skipped Sunday and Wednesday.
Last week I only really count as half a week since I was in Florida I got 13miles in (Running Wednesday, Thursday, and Saturday).
I've had a pretty successful running week thus far and I'm happy to report that I think of gotten back in to the rhythm of running which is not easy to do. A lot of people have a hard time getting into running because in all honestly it's not that much fun to do on a consistent basis when you first get started. Sure that first run is invigorating, you feel awesome cause you just did a run. Then the next day comes and you realize you have to do it again because the run yesterday only counted for yesterday. I've always found it easier to run with a schedule that is usually tied to a race. For example it's easier to say "I'll run those 10 miles because I don't want to die during the marathon" than it is to say "Oh hey, it's -20 out I think I'll run 10 miles". So obviously a good way to get in to running is to get yourself committed (monetarily) to a race and tell everyone you know you're doing it. Why tell everyone you're doing it? Because of a few things: they won't get mad at you when you're busy and can't hangout because you're on a run, they don't judge you when you eat a 10" pizza* by yourself because you'll probably run it off, and they will ask about it and your training. People will ask you how your training is going, so you can't be a liar liar pants on fire and say you've been running when you haven't. So go on that training run because nobody likes a liar. But beware, that doesn't mean they want to hear you talk about your training, they are just confirming that you are still their weird friend who pays money to run races.
But what do you do when you don't have a race to set up a training schedule for? Like I do right now. Which is not totally true since I have some races in the queue I just haven't paid my entry fee yet. When you get in to running you're sort of always training because you are trying to get faster so you can get a certain time. However, it's still not easy to get yourself excited to go out multiple days in a row. I was finding this really hard right after Ultimate ended. I wanted to give myself a fat week to just laze around, but I couldn't. I needed to jump in or I would continue to find a reason to not go for a run. So I just did it, I went on a short 3mile run and set myself up for miles of fun in the coming months. I was jazzed on Wednesday, so proud of myself as I wrote a three next to the date on the calendar, imagining all the mileage totals I'd be racking up. How pumped I'd be to tell the world in this blog how much I've been running. Then Thursday came and I realized that three I wrote can't also count for today. Thus I had the fight in my head, "do I really need to go running". If you've run you've probably had this same internal conversation; "you did run yesterday, and your body is still recovering from ultimate, and you deserve to ease into it....etc". No I had to ignore it. I needed something to out shout the voices in my head. Would it be rock and roll? Hip Hop? Could I blast it out with some Thrift Shop echoing into my head from my ear buds? No I needed something more. Something that would block those thoughts out for good so what did I choose? What was my secret weapon?
You guessed right! Peter Sagal and the crew of "Wait Wait Don't Tell Me" the NPR news quiz. A couple things to quell you naysayers. First of all Peter Sagal is a runner. He actually had a great article in Runners World about training for the Chicago Marathon to beat his PR. He's run a lot of races and he chronicled his journey along with some great pictures. There was one of him peeking out from a port-o-potty but I couldn't find it so you get some nice white thighs instead. I also knew that I had a buttload of Wait Wait Don't Tell Me podcasts on my ipod that were begging to be listened to. I wanted to listen to them so I made a deal with myself - you can listen to the podcast, but you have to go on a run. It was prefect because podcasts are about 45minutes long and I needed to go on a 5 mile run. So that has been my secret weapon all week. Listening to NPR. The most obvious choice to inspire any athletic endeavor. I'm sure it also amuses those I see while on my run as a blond haired runner hops by giggling to herself about something Mo Rocca just said.
But really if you need to find motivation to get yourself out there maybe you need to give yourself another incentive not a punishment for not running. For me it was getting to listen to a great podcast. For you it could be a book on tape, or maybe you love sour gummy worms and you stash them in your pocket and you get to eat one every half mile, or maybe you want to look at Christmas lights in your neighborhood. Running is fun, and after you get into your routine it's pretty easy to want to go out for a run because it just becomes a thing you do. But there's nothing wrong with combining it with something else fun.
*who am I kidding, I can't finish a 10" pizza by myself. Although the guy at Hops and Pie last night did say when I ordered it "is that all you want?".
Total Miles since Ultimate Season ended = 35.5miles
I skipped Sunday and Wednesday.
Last week I only really count as half a week since I was in Florida I got 13miles in (Running Wednesday, Thursday, and Saturday).
I've had a pretty successful running week thus far and I'm happy to report that I think of gotten back in to the rhythm of running which is not easy to do. A lot of people have a hard time getting into running because in all honestly it's not that much fun to do on a consistent basis when you first get started. Sure that first run is invigorating, you feel awesome cause you just did a run. Then the next day comes and you realize you have to do it again because the run yesterday only counted for yesterday. I've always found it easier to run with a schedule that is usually tied to a race. For example it's easier to say "I'll run those 10 miles because I don't want to die during the marathon" than it is to say "Oh hey, it's -20 out I think I'll run 10 miles". So obviously a good way to get in to running is to get yourself committed (monetarily) to a race and tell everyone you know you're doing it. Why tell everyone you're doing it? Because of a few things: they won't get mad at you when you're busy and can't hangout because you're on a run, they don't judge you when you eat a 10" pizza* by yourself because you'll probably run it off, and they will ask about it and your training. People will ask you how your training is going, so you can't be a liar liar pants on fire and say you've been running when you haven't. So go on that training run because nobody likes a liar. But beware, that doesn't mean they want to hear you talk about your training, they are just confirming that you are still their weird friend who pays money to run races.
But what do you do when you don't have a race to set up a training schedule for? Like I do right now. Which is not totally true since I have some races in the queue I just haven't paid my entry fee yet. When you get in to running you're sort of always training because you are trying to get faster so you can get a certain time. However, it's still not easy to get yourself excited to go out multiple days in a row. I was finding this really hard right after Ultimate ended. I wanted to give myself a fat week to just laze around, but I couldn't. I needed to jump in or I would continue to find a reason to not go for a run. So I just did it, I went on a short 3mile run and set myself up for miles of fun in the coming months. I was jazzed on Wednesday, so proud of myself as I wrote a three next to the date on the calendar, imagining all the mileage totals I'd be racking up. How pumped I'd be to tell the world in this blog how much I've been running. Then Thursday came and I realized that three I wrote can't also count for today. Thus I had the fight in my head, "do I really need to go running". If you've run you've probably had this same internal conversation; "you did run yesterday, and your body is still recovering from ultimate, and you deserve to ease into it....etc". No I had to ignore it. I needed something to out shout the voices in my head. Would it be rock and roll? Hip Hop? Could I blast it out with some Thrift Shop echoing into my head from my ear buds? No I needed something more. Something that would block those thoughts out for good so what did I choose? What was my secret weapon?
You guessed right! Peter Sagal and the crew of "Wait Wait Don't Tell Me" the NPR news quiz. A couple things to quell you naysayers. First of all Peter Sagal is a runner. He actually had a great article in Runners World about training for the Chicago Marathon to beat his PR. He's run a lot of races and he chronicled his journey along with some great pictures. There was one of him peeking out from a port-o-potty but I couldn't find it so you get some nice white thighs instead. I also knew that I had a buttload of Wait Wait Don't Tell Me podcasts on my ipod that were begging to be listened to. I wanted to listen to them so I made a deal with myself - you can listen to the podcast, but you have to go on a run. It was prefect because podcasts are about 45minutes long and I needed to go on a 5 mile run. So that has been my secret weapon all week. Listening to NPR. The most obvious choice to inspire any athletic endeavor. I'm sure it also amuses those I see while on my run as a blond haired runner hops by giggling to herself about something Mo Rocca just said.
But really if you need to find motivation to get yourself out there maybe you need to give yourself another incentive not a punishment for not running. For me it was getting to listen to a great podcast. For you it could be a book on tape, or maybe you love sour gummy worms and you stash them in your pocket and you get to eat one every half mile, or maybe you want to look at Christmas lights in your neighborhood. Running is fun, and after you get into your routine it's pretty easy to want to go out for a run because it just becomes a thing you do. But there's nothing wrong with combining it with something else fun.
*who am I kidding, I can't finish a 10" pizza by myself. Although the guy at Hops and Pie last night did say when I ordered it "is that all you want?".
Subscribe to:
Posts (Atom)







