Horseshoe Lake 50K

Heat training and Oreo lips

On Sunday we did our last long run before the Bryce 100, the Horseshoe Lake 50K. It was a beautiful morning, with saturated light at clear views over the big blue Pacific. The race was sold out and I think there were close to 200 people at the start. I was drawn into all the excitement of "yay running" and went out too fast on the first climb, which resulted in being caught in a faster group for the punchy descents. Not wanting to get mowed down on the singletrack, I did my best to keep the pace by resorting to toe running.

I've done a bit of research on common causes of shin pain. There are a lot of different theories about which motions and/or tight muscles lead to tibial stress. My experiment of one so far shows that braking or landing hard with my forefoot, which is my tendency when descending or accelerating, seems to exacerbate the pain. Subsequently, slowing my downhill pace, shortening my stride, and deliberately engaging full foot strikes (trying to get that heel on the ground) brought quick relief. I was unhappy at mile six and suspected I would need to stop once I reached the first return to the start at mile 13. But at the half marathon point, after seven miles of mitigation efforts, I felt considerably better. I decided that continued experimentation with shin pain management would be more beneficial for my upcoming race than quitting early and hoping this will somehow work itself out in ten days. If it was a full-blown injury, I would certainly be more cautious. But this still qualifies as a minor nagging pain, and it doesn't seem to be worsening. Most sources I found say that shin splints typically take three to six weeks to go away, but it's possible to continue training during recovery as long as pain doesn't get worse.

Beyond that, the run was fairly uneventful. It was warm — probably into the mid-80s — but there was a nice breeze whisking along the ridge to take the edge off the heat. I felt strong, so my purposefully slowed pace caused some frustration and dissatisfaction ("I feel good. I can do better than this. But I shouldn't. But I can. Grrr.") In the aftermath, I feel my stride experimentation was beneficial, but there were plenty of points during the race when all I really wanted was to run faster — or climb faster, because a determined power-hike up a steep grade also involves getting up on the toes. But I dialed it back and finished strong, happy, and essentially pain-free. One week after the 50-miler, the Horseshoe Lake 50K was a good confidence boost in my endurance ahead of the Bryce 100.

I finished in 6:32. I raced this same course back in October and felt compelled to look up my former time, to see how it compared. Also 6:32. Apparently, getting stung by a wasp and minor shin splints cause me the exact same degree of pain-induced slowness.

I'm not planning to do any more running before Bryce. I'm headed out to Utah a week before the race to visit my family, and my dad and I are going to go for a few hikes in the Wasatch this weekend. The whole course is between 7,000 and 9,500 feet, so I could use all the pre-race acclimation I can get. My friends claim this is an unfair advantage, and they're right. But they're also all stronger runners than me, and the 34-hour cutoff looms.

I'm really looking forward to the Bryce 100. These 50K and 50-mile efforts are fun, but there's something intimately engaging about pressing through the night and emerging into a second day. Hundred-mile runs and multi-day bike races have their own life spans, and they always linger in my memories long after these smaller adventures fade into the distance. In a sense, long efforts are my way of extending my own life, because I live so intensely and experience so much in a relatively short time span. I often emerge feeling like I've made weeks, months, and sometimes years of individual progress. Many will argue that these efforts are inherently unhealthy, and they're not wrong. But in my opinion, the benefits of hundred-milers could never be quantified in any tangible way. From an outside perspective, they're nothing but stupid ... but inside, they're an integral part of an invaluable education.

And with that, I missed a week but I am still trying to keep track of my training for the summer. Blogs are good for that kind of tangible nonsense.

Week May 6-12
Monday: Trail run, 6.5 miles, 976 feet of climbing
Tuesday: 0
Wednesday: Road bike, 17.5 miles, 2,553 feet of climbing
Thursday: 0
Friday: 0
Saturday: Trail run, 50 miles, 8,799 feet of climbing
Sunday: 0
Total: 56.5 miles run, 17.5 miles ride, 12,328 feet of climbing

Week May 13-19
Monday: Road bike, 16 miles, 2,143 feet of climbing
Tuesday: 0
Wednesday: Trail run, 9.1 miles, 1,327 feet of climbing
                     Mountain bike, 8.9 miles, 1,844 feet of climbing
Thursday: Trail run, 7 miles, 1,675 feet of climbing
Friday: Road bike, 17.5 miles, 2,535 feet of climbing
Saturday: Mountain bike, 20 miles, 2,740 feet of climbing
Sunday: Trail run, 31.1 miles, 5,671 feet of climbing
Total: 47.2 miles run, 62.4 miles ride, 17,935 feet of climbing

Strava hubris

This was supposed to be a mellow pre-race spin up Black Mountain, but after just two miles I knew it was going to be a grind. My legs were empty, like an unseen force had drained out the muscles and injected them with gelatin. The week had been going great up to a point, but then it took a dramatic turnaround. What happened? "I blame Strava," I grumbled to Beat as I struggled to hold his wheel.

Speed. Most of the time, I prefer to pursue longevity-promoting balance. Do something at 100 percent of your capabilities and you might need a week to recover, but at 80 percent you can go for half a day, and at 60 percent exponentially longer. Eventually you come to the conclusion that if distance is your ultimate goal, speed isn't the way to go about it. Still, I admit that it's intriguing take something you do all the time and try to do it faster. Every once in a while, I get sucked into the temptation.

It started with the AMGEN Tour of California, and considering my own PRs on my favorite routes. I realized that just about every "record" I've set happened in the first year I lived here, between March 2011 and March 2012. I don't like to believe that I'm getting worse at biking, although every statistic and intuition I have points to the likelihood that this is happening. But I like to think that the abilities are still there, somewhere, hidden deep inside me, and they just need a little coaxing to come out.

For the record, I think Strava is ridiculous. I do. I did enjoy the record-tracking program right up until I started to receive those "uh oh" e-mails three times I day, informing me I lost the queen of the mountain / course record on yet another 0.2-mile segment. I was able to ignore these e-mails until a segment came through that was in Fairbanks, Alaska. My interest was piqued enough to check it out. This particular segment was none other than the Wickersham Wall, the seemingly vertical snowmobile trail up the Wickersham Dome that starts at mile 94 of the White Mountains 100. If I'm ever achieved a speed faster than 0.5 mph while pushing my bike up that thing, I'd be surprised. Queen of the Mountain? Bah. Strava's ridiculous. I pretty much stopped using it that day, although I do go back from time to time and mass-upload the Garmin data on my computer.

But there is one Strava segment I do care about, even if I don't like to admit it to myself — Montebello Road. At 5.2 miles with 1,941 feet of climbing, it's my go-to road climb and one of the few things I do that I can benchmark around every turn. My best time on this segment, according to Strava, is 39:08, achieved on February 6, 2012. It's good enough for 16th out of 163 women, and I'm fairly certain I can do better if only I tried. Okay, maybe I should do some road-cycling specific training first, but isn't trying enough? No? Well, on May 17, 2013, I set out to try.

The segment starts at about mile 3.4 of my regular ride from home to the Montebello gate and back. I always forget to check my watch at the turn, but it usually happens between minutes 12 and 15 depending on traffic lights, which means I need to hit 51 minutes or better to assure busting out a sub-39. This is the easiest thing to track, although I also have this notion that I need to keep my minutes-per-mile pace above 9:00 at all times. This is about the slowest I can go over the toughest mile to actually achieve the 8 mph average I need.

So that's the basic tracking system. The first mile is the steepest, though, and after that I'm too maxed out to understand my watch anyway. That's why I cling to the 9-minute-mile thing, because I can always look at that number and understand whether I'm moving faster or slower. So there I was, churning pedals, unapologetically gasping for air and shooting snot rockets, with eyes fixed solely on the prize — avenging 15 months of Strava mediocrity. I made it through the hard climb, raced over the flatter miles three through four, and tucked my head for the final climb when the numbers shot skyward. 9:10 pace. Then 9:34. Then 10:02. Oh no! I was melting down. My legs felt like they were shooting flames, and I couldn't imagine where I was going to find the overdrive to maintain my pace. And somewhere in the back of my mind, that little trail running angel came to sit on my shoulder and said, "remember that little training race you have on Sunday? The Horseshoe 50K? It's on Sunday. What are you doing?"

"I don't want my legs to die," I thought, so I gave up. I kept pedaling but I stopped looking at my watch. At the top, it read 53:41. "Hmm, if it's minus fifteen minutes to the bottom of Montebello, than it just might be good enough. Even if it's just minus twelve, it's not bad. But no, I stopped trying. It's not good enough. It's never good enough if you don't try."

I admit I haven't uploaded the track yet. Part of me does not want to know, at least not until Sunday's race is over. I can't believe I roped myself into a silly Strava race and now my legs admittedly feel pretty tired, when they were just fine for Wednesday's double-header and Thursday's 7.5-mile hill run on the Black Mountain trail. Speed. I get why it's needed to, you know, actually get faster. But it is hard on the body and in the face of longer distances, it seems like a bit of a waste. When you're trying to maximize gas mileage, it's probably not the wisest move to keep the pedal pressed to the floor.

Speed is fun, though. Oh, sub-39-minute Montebello. I will get you, and prove to you I can still ride a bicycle. Someday.

Over the slump?

Recovery is a difficult equation to solve. For most of April I felt blah. I had a difficult time with regular running routes, acquired hints of a minor injury, took it sort of easy but not really, and then ran a fifty-mile trail race. And this week, ever since the morning after the fifty miler, I've felt great. Minimal soreness, no new aching in the shin, and an abundance of energy. It seems all it takes is one fun endurance adventure to reset my psyche — "Oh, right, we really enjoy this stuff. We're not tired, not tired at all. Carry on, body." And my body, since it's way stronger than my mind regardless of what my egotistical mind likes to think, just shrugs and says, "Oh, okay." And off we go.

I have continued to take it easy for the sake of my shin. There's also the matter that I am decidedly in taper mode now. I have one more long run this weekend and then I have to focus on being prepared for the Bryce 100 on May 31. There was a miniature scandal this week when the race director decided to reroute the course to hit more singletrack and more scenic areas around Bryce Canyon. After measuring the new course with his GPS, he shifted the elevation profile from 14,000 feet to 26,000 feet climbing — a *significant* difference. Panic ensued. And just as I and other participants were coming to terms with the change and getting excited about the climby new course, the RD returned with an "oops, my bad, I had some other people analyze it with mapping software and there's only 18,500 feet of climbing." So ... who knows? In a way, it doesn't matter. I've attempted hundreds with 2,000 feet of climbing and 18,000 feet of climbing and 23,000 feet of climbing and they were all really, really hard. Usually climby courses work out in my favor, because I'm a much stronger hiker than runner.

But I had a great run today. Headed out at 1 p.m. and it was actually somewhat cool, about 75 degrees. I kept my effort level just below "zone out" (when I am working too hard to think about anything) and wrapped up 9 miles and 1,800 feet of climbing in 1:29. Then I saw an e-mail from my friend Leah about going riding in the evening at Skeggs. Sure, why not?

Every time I ride at Skeggs, I wonder why I don't spend more time there. It's beautiful, steep, often misty and damp from coastal fog, and full of flowing singletrack. But then I come to a technical section like this and narrowly avert disaster doing something silly. I am starting to come to terms with the reality that I am not hard-wired for technical mountain biking. I've always felt a disconnect with my sense of balance (i.e. clumsiness) and these movements don't come naturally to me. It would take a lot of practice to gain the proficiency I need. Technical running trips me up too, but at least at running speeds, when I fall (frequently), I just get banged up. When I make a mistake at mountain biking speed, (less frequent) falls have sent me to the hospital. Leah disagrees with my assessment and thinks I just need more practice.

But we had a great ride. Some of the climbing sections put me deep into the red zone, so when I checked my GPS, I was surprised to see that our route was only 9 miles with 1:48 riding time. It did have 2,300 feet of climbing, and a decent amount of downtime (while I played with my new camera.) Still, it makes me smile that I was able to run 9 miles faster than I could ride 9 miles today, and the ride felt considerably harder. Maybe Leah is right that I don't practice mountain biking often enough.

But yes, I received a new camera yesterday. Beat gave it to me as a surprise, for no real occasion — so it was a very nice surprise. It's a Sony Nex-5R. I've been using a Sony Nex-3 as my primary camera for three years now, and have been really pleased with it. Although it doesn't come on all my adventures, it has taken its fair share of abuse in the past three years. I've used it in dust storms and rainy days and temperatures down to 25 below. But it's not one of those tough cameras — it's a medium-sized point-and-shoot with several near-DSLR capabilities, and interchangeable lenses. The Nex series is a good choice for anyone who wants some of the features of a DSLR without the expense or bulk. It's been a great camera for me.

I'm still getting used to the Nex-5R so I didn't necessarily have it on the best settings for my "shoot" this evening. I also couldn't figure out the macro settings, so you don't get to see a picture of the cool wasp exoskeleton that Leah and I found. But I had fun playing with my new camera today, and hope it will see its fair share of adventures.

Looking back toward Skyline Ridge and Skeggs during the drive home. You can see all that fog we were riding around in. It was decidedly cool — around 50 degrees with some fierce winds — and felt wonderful. A great day for a 9-miler-times-two run and ride.