Week 9, Jan. 6 to 12

At the mile 26 aid station of the Crystal Springs 50K. My favorite calorie source during a long run is cold sugary carbonated beverages, but the aid stations usually run out of soda later in these races. This volunteer/photographer just happened to capture that moment of joy when I discovered they still had Sprite. It's the simple things that make life.

Post-Fairbanks training panic spurred a high-mileage week of running, as my bikes sat woefully neglected on yet another unseasonably warm and dry January week. I've had several debates about my training approach with Beat, and the conclusion seems to be that any workout I do at this point will likely have little to no impact on my overall physical preparedness for the upcoming seven- to ten-day effort. Still, I tend to thrive on higher-volume endurance training; since I started this training block ten weeks ago, I have become progressively stronger as a runner. A fast-for-me 50K and an 80-mile week of trail running had no negative impacts in terms of pain or fatigue. I definitely wouldn't have been able to manage the same volume so naturally one year ago. This coming week I'm incorporating at least one "trailer-pull" and more bike rides, because actually, I can't neglect maintaining a bike base if I want to enjoy summer (not the mention the White Mountains 100.) The Iditarod will come and go and life will go on again, I hope. If I survive.

Monday, Jan. 6: Run, 1:28, 8 miles, 1,668 feet climbing. Average pace 11:07/mile. The first of three "bonk runs" this week, up the High Meadow Trail and down PG&E in Rancho.

Tuesday, Jan. 7: Run, 0:57, 5.7 miles, 635 feet climbing. Average pace 10:08/mile. Monta Vista with Beat. I became quite dizzy at mile four.

Wednesday, Jan. 8: Run, 2:50, 15 miles, 3,049 feet climbing. Average pace 11:23/mile. Black Mountain loop, also on the low-cal plan. Some light-headedness on the steep climbs between miles two and six. Felt much better after I worked through / ignored that initial low point.

Thursday, Jan. 9: Road bike, 1:30, 17.5 miles, 2,566 feet climbing. Montebello Road. I've started to use this ride as a recovery-type effort, but a flatter route might be better for this.

Friday, Jan. 10: Run, 1:04, 5.5 miles, 1,220 feet climbing. Average pace 11:55/mile. Run in Berkeley with Ann. She was dog-sitting an unruly dog who was impossible to control on a leash, so we cut the run short and jogged/walked back. I thought we'd do something longer and faster and was initially disappointed, but this turned out to be the perfect lead-up to a great race the next day.

Beat running at Crystal Springs. So smiley. :)

Saturday, Jan. 11: Run, 5:36, 31.1 miles, 6,611 feet climbing. Average pace 10:56/mile. Crystal Springs 50K. Probably my best 50K effort yet, partly due to having run this course enough times to have it "figured out." I sometimes let my imagination ponder how well I could nail a 50K if I ever specifically and effectively trained for that distance. But the truth is, I have negative interest in the speedwork it takes to get fast (injury fears) and too much love for the long haul. Plus, all these miles I do that speedsters refer to as "junk miles," I think of as "running that is actually fun for me." But I never say never.

Sunday, Jan. 12: Run, 2:44, 13.3 miles, 2,353 feet climbing. Average pace 12:24/mile. I waited a little too long to start this run, after all of the post-race zeal had worn off, and as a result struggled with motivation. Climbing up PG&E, I had one of those "I'd rather be doing something else" moments, and after that it was difficult to fight off the lazy urges. Plus, I left late enough in the afternoon, after only a small lunch, that the final half turned into the more miserable kind of bonk run. Still, I stuck with the plan, and had surprisingly little muscle fatigue from Saturday's race.

Total: 16 hours 9 minutes, 78.6 miles run, 17.5 miles ride, 18,102 feet climbing.

50K PR

After we returned from Fairbanks, I caught a touch of the training panic. Sled-towing was so hard, and I felt so slow, that I came back to California with a number of resolutions. I need more running! Less biking, more time on my feet! More back-to-backs! More hills! More weight! The weight goal is still in progress. I opted against running with a heavy pack because it's so hard on my knees. Then Beat acquired a bike cargo trailer that he is going to outfit with disc brakes to add resistance, and today I purchased 60 pounds of kitty litter for the purpose of hauling around in the trailer. As soon as he gets the brakes set up, we'll trade off a weight-training session here and there. If I can add just a little more strength-building and volume to my routine in the next three weeks, I'll feel more confident about my conditioning for the ITI.

On Saturday we ran the Crystal Springs 50K, a pleasant trail run through the redwoods along Skyline Ridge. The course is almost identical to the Woodside Ramble 50K that I ran a month ago (directed by a different race organizer), but I do love running these trails, and Beat and I enjoy participating in these events as fun, well-supported training runs. When I caught up to Beat on the first long climb, he had already found a cute girl to run with, Celine (Beat often makes friends during races, both male and female, because running makes him happy and thus chatty and friendly. I find this endearing, even when his new friends are cute girls.) Celine looked to be in her early 20s, was running her first 50K, told us her dad worked for Google, and seemed enthralled with Beat's tales of derring do. We all ran together for about five miles before they dropped me on the descent into Wunderlich Park.

As I padded the soft dirt along Salamander Flat, it occurred to me that I was nearly 15 miles into this race, and yet hardly felt it. Somehow the first half just coasted by, so I decided that for the second, I was going to put in a decent effort. Nothing crazy — I'm not trying to injure myself with untrained speed. But I could work a little bit for it.

Beat teased me when I passed them again on the second long climb. "I can't descend worth anything so I might as well run the uphill," I called out as I motioned them to follow. They nearly caught up when I was snacking at the 20-mile aid station, but I didn't see them and took off again before they arrived. The next section is six miles of rollers. I passed quite a few people during this segment, some running the marathon distance at a slower pace, but at one point I passed a woman who had slowed to walk one of the short uphills. She blazed past me on the next downhill, and after that I noticed that any time I got close to her again, she'd speed up. "She's racing me!" I thought, and then, "Okay, it's on."

We passed each other a few times — she couldn't quite hold me off on the longer ascents, but she was more willing to let go on the descents. Finally I started to feel embarrassed about our leapfrog game, and decided just to keep her in sight. As such, I sometimes got a little rest on the climbs, and her downhill speed would spur me to take a few more risks on the descents. It was a lot of fun — relaxing and thrilling at the same time.

The final five miles has two short climbs, but it's mostly a long descent. I assumed I'd never see her again, but thought I should at least try. I managed to maintain the shadow all the way through the final mile, a much more gradual descent on a gravel road. When it was nearly flat, she started to slow. My legs felt surprisingly fresh. I pondered engaging a sprint to the finish, but the prospect of racing a random woman for one less notch in the standings seemed too embarrassing. I just can't bring myself to behave that way, which is one of many reasons I'm not much of a racer. As we coasted into the finish, I noticed the clock read 5:36. My initial reaction was that I'd mis-read the number, because that would be 15 minutes faster than I've ever run a 50K, and that didn't seem likely. You have to run hard to run fast(er), right? But as I strode back around to watch for Beat, the clock was still in the 5:30s.

Celine came in a couple minutes later, informing me that Beat was a minute or so behind after she surged to the finish, wherein Beat accused Celine of disrespecting her elders. "Mid-fives, is that pretty good for a 50K?" she asked. "It's fast for me," I answered, "and I think it's great for a first 50K trail race on a hilly course." Beat came in at 5:42, and we headed to the barbecue table just as Celine's dad approached to pick her up. Beat recognized him instantly because he was Patrick Pichette, Google's CFO. In all those hours Celine didn't share that detail. She was very down-to-earth — just a young woman from Montreal who was studying in Scotland with aspirations to become a surgeon, visiting her Google-employee father at their home in San Francisco, and running a 50K for fun. She would be running a 15K with her dad in the city the following day. I encouraged her to check to see if she won an age-group award, and that's when I learned she was 19. Nineteen! Girl's going places.

Oh, the woman who finished 8 seconds in front of me was third female, 12 minutes behind first place. Missed the podium by that much, ha!

The plan was to finish the 50K with plenty left in the tank, and then put in another moderate run on Sunday. I fluctuated with my ambitions but ended up running a 13-miler on the steep PG&E loop at Rancho San Antonio. This "tired-legs" run mainly suffered from flagging motivation and subsequent laziness, but for the most part I felt good. Little to no soreness in the legs, no issue at all with feet, some "bonkiness" (sudden blood sugar crash, felt fine before and wasn't thrilled about low-energy running this time around), and subsequent minor gastro issues.

I am pleased that I was able to run a personal best 50K time, comfortably, having fun the whole time. Tonight I was able to meet with "Sea Legs Girl" Tracy, who was interviewing at Stanford, for dinner in Palo Alto. Amid engaging conversation about overtraining patterns and life in the Bay Area, the topic turned to what part of my winter training could have helped me become faster when my entire focus has been long-term endurance building. I speculated that I'm still feeling the after-effects of the Fairbanks training, where pulling around a 30- to 40-pound sled on difficult terrain helped build uphill strength. I can actually go back and compare mile-for-mile splits to previous races on the Crystal Springs course, and almost all of my extra time was gained on the climbs, and by effectively negative-splitting the final half. If pulling a sled makes me a stronger uphiller, I still wonder whether running lots of hills can make me a stronger sled-puller. My brain expresses doubt but my heart wants to believe. Mostly because I just want to keep running. 

Like rolling waves

This week, I have been experimenting with "bonk" running. This wasn't entirely intentional — basically, I got caught up in what I was doing during the day, skipped lunch, and then headed out in the late afternoon for a run without snacks. Monday was eight miles of one long climb and descent, running on what felt like the fumes of a long-ago-incinerated breakfast. Tuesday was six with Beat, and for two of those miles I was downright dizzy. "What a hopeless carb burner I am," I thought. "But at the same time, it's not really that much worse without carbs."

Beat is still considering the experiment of walking unsupported to Nome, nearly a month on only the supplies he can carry in his sled. It's a baffling goal but also a potentially valuable learning experience toward becoming an expeditioner, for which Beat has aspirations. This has led to multiple discussions about high-calorie density foods — such as pounds and pounds of peanut butter — and the art of burning fat for fuel. Like most people I carry plenty of this around, but consider fat a terrible energy source for strenuous exercise. It's like looking at a pit of smoldering coals and saying, "You know what would really get this fire going — a huge, wet log!" Body fat or dietary fat — it's all slow-burning and sluggish.

Still, becoming a more efficient fat burner — or at least developing more confidence in what my body can already do — has the potential to enhance my own long-distance experiences. In the case of the Iditarod, I could lighten my load by subsisting on more energy-dense foods, and I potentially wouldn't have to stop and eat as often — always an intimidating chore in the deep cold. My mouth wouldn't get as torn up by constantly gnawing on frozen sugary foods, and the slow burn might aid in keeping my body temperature more consistent. It's a little too late in the game to switch to a low-carb plan. But at the same time, I would benefit from slightly curbing my carb dependency — if only to get a feel and an appreciation for running on fumes, which, for better or worse, is likely to become my default state in the Iditarod.

On Wednesday I set out a little earlier than usual, only about five hours after breakfast instead of eight, which, — after I'd defined my early-week runs as goal-oriented, rather than simply being too lazy to make lunch — felt like cheating. I laced up my Hokas and filled up a 20-ounce bottle with water, stuffed a camera and wet wipe in the hand-hold pocket, and set out. The plan was six miles. Dark clouds settled over Black Mountain as a mist of light rain wafted on the breeze. It's getting to the point of drought here in California that I tend to become irrationally excited about "bad" weather and irrationally grumpy about "good" weather. By the cut-off,  I was buzzing with happy hormones and feeling a strong desire to chase those dark clouds up the mountain. Instead of turning left, I continued climbing.

The grade steepened, and even as these undefined urges drove me forward, a haze settled over my brain. This is the real benefit of a bonk run; there's less glucose to fuel my over-active imagination, and all of the little nagging voices and unsettling or distracting thoughts begin to lose steam. What remains, interestingly, is persistent forward motion, as though that were survival instinct — "keep going." Fog obscured the top of the mountain, and I kept going.

My little water bottle was almost empty by the time I reached the summit,. The dark fog had lifted, but small pellets of rain still drove through the wind. I was only wearing a T-shirt and knee-length tights and it was fairly cold, plus I was thirsty, but still I opted to skip the half-mile spur to the backpacker camp and continue the long way down the mountain. The nearest water fountain was eight miles away. "Sometimes it's good to see how far we can go with just our shoes and our water bottle," I thought. "Or, you know, a sled filled with forty pounds of survival gear."

I enjoyed the descent immensely. There was a kind of lightness to my body, a fluidity to my movement, a freedom to simply run unburdened by anything but an empty water bottle. Hunger gnawed at my stomach and thirst trickled into my patchy thoughts — but there was no immediate danger and thus no immediate concern. We can't go forever without food and water, but in most situations, we can go a lot longer than we think.

I filled up my bottle at the farm and drank with deep satisfaction — I wasn't dehydrated yet, but just thirsty enough to truly appreciate the water. Ten minutes later, the run came to an abrupt end at my car, 15 miles after I started. It was somewhat disappointing, because I felt like I could keep going and wanted to.

I did feel slightly guilty for spending an unplanned two hours and 45 minutes of a Wednesday afternoon, just running — but at the same time, grateful for the ability to do it. "Yes, it is amazing the places one can go with shoes and a water bottle," I thought. That kind of fluid, seemingly effortless motion — rolling over terrain like waves in the ocean — is the reward of not getting too weighed down by the process.