Showing posts with label hoka. Show all posts
Showing posts with label hoka. Show all posts

Monday, October 31, 2011

Week in Review: 23-29 October 2011, and Halloweeny 50K Race Report/Product Review

Getting back on track with the mileage thing:

23 October 2011: 20 miles (140 minutes), including an impromptu Diane Heiser-brand beatdown, as I joined her for pickups of ~4 minutes, 6 minutes, 4 minutes, and 2 minutes on the promenade. Almost hit by a car in the process, jeered by a group of guys in Fells when she dropped me on the 6, and saw a guy with a boa constrictor draped over his shoulder coming back on Monument Street. What a day . . .

24 October 2011: 15 miles (110 minutes), out, back, and along with the Fed Hill group, plus a little extra meander.

25 October 2011: 6 hard-fought miles (~40 minutes): 1 mile warmup, 2 miles warmdown, and about 3 miles of intervals on the track on "relay night." Mile (6:15-ish - bad), quarter, half, half, quarter, plus some jogging around. Last quarter in 68, which is the fastest quarter I've run in a long, LONG time (which is a feel-good, even though Diane ran a 64 and beat me in the last few meters . . . boo)

26 October 2011: 9 miles (65 minutes), easy with the group running from O'Donnell Square

27 October 2011: 7 miles, wandering in and around Patterson Park (50 minutes)

28 October 2011: 3 miles (25 minutes), test-running the Hokas in Patterson Park

29 October 2011: 30-ish winning birthday miles (probably more like 31), in about 5.5 hours (330 minutes) - see below.

Total Time: 760 minutes
Total Distance: 91 miles

Back to a solid mileage total. Good variety of speed, distance, and terrain this week, and getting beaten by the best on occasion, made this week productive and satisfying.

Now, the race report, and product reviews (man, this thing is going to be jam-packed - if you're just interested in the Hoka Mafate Trail Running Shoe and Nathan VITABand reviews, skip straight to the bottom now):

For my birthday weekend, my original plan was to run back-to-back 50Ks, in keeping with the tradition that I started last year of running a mile for each year (where last year's event was a wandering 29-mile loop around some of my favorite places in Baltimore City). This year, the Halloweeny 50K and the Fire on the Mountain 50K were scheduled as back-to-back races on my birthday weekend, so I had planned to run them back-to-back, in honor of 30 being a big year and a nice round number, for whatever that's worth. I was also planning to try to go under 5 hours for each of them, or under 10 hours total. But, as we shall see, the best laid plans of mice and men (especially mice, and even more especially, men dressed as women dressed as mice) . . .

In any case, at 5:05 a.m. on Saturday, Octoher 29th, my cell phone alarm rudely awoke me after a night of warm, sound, cat-free sleep in my own bed. I spent the last 10-ish minutes of still being 29 tending to my three cats and starting to put on my costume (which, for those still not in the know, was Karen Smith from the movie "Mean Girls" dressed as a mouse for Halloween, in keeping with the monologue in the movie about Halloween being an excuse for girls to dress like sluts without retribution, and that the "hardcore" ones dressed in lingerie and animal ears). My costume, which cost about $15 (total of $6 for women's size XS running skirt and size M running tank on deep clearance at Target, $5 for blonde wig, $3 for mouse ears, and $1 for a roll of pink ribbon to use as accents for the outfit), proved more complicated to put on than I had thought - apparently it's not easy being a girl. Somehow, I managed to take an hour and a half to get out of the house, in spite of laying things out the night before (maybe I should have stopped noticing things out of place and fixing them before I left).

The drive out to Gathland State Park for the race was a bit harrowing, as it was alternately snowing/sleeting, and people were choosing either to ignore this fact and drive 90 mph as if nothing were wrong, or panic and drive 40 mph as if there were already a foot of snow on the road. I arrived at the parking lot at about 5 minutes to 8 a.m., when the race was supposed to start, only to find that due to the snow, the start had been moved to the pavilion a little less than half a mile up the hill. I drove up the hill and checked in right around 8 a.m.; fortunately for me, due to the changed start location, the start time was pushed back 15 minutes to account for anybody who had gone to the original start location and been re-directed. After a pre-race briefing with more course directions than anybody could possibly remember all at once, we were off.

To back up for a second, because this was a "fatass" event, the event was not postponed to a later date due to weather. As a "fatass" (no entry fee, no t-shirt, no awards, no wimps), participants take their ability to navigate the course and their safety into their own hands, since the course is not marked, race-related medical help is not available, and the event is not sanctioned by the park. Given this background, although a little over 100 people signed up for the race, only 41 actually showed up, and, with the ever-worsening conditions (more about that later), only about 10 people actually finished the entire race.

I headed down the white-blazed Appalachian Trail (AT) section up to Weverton Cliff, behind Sean Andrish and another faster runner. The snow was coming down, the rocks were getting slippery, and it was a gradual uphill. I stopped to put on a jacket and re-tie my shoes, and Sean ran out of sight, so I held my pace once I got running again, was passed by a guy dressed as a nun and another guy not in costume, both of whom I passed by the end of the first AT section. I came into the first aid station looking like this:


Time to fly, indeed, turn sheet in hand.

Not super-fast up the mountain, but definitely rolling down the backside, where the snow had turned to light rain. The next section was "easier," following the AT down to the C&O Canal Towpath (of JFK 50 fame), but on the Towpath, the snow had turned to freezing rain, flooding the path and ensuring that I would not be even remotely dry for the remainder of the race. So a theoretically flat, fast 3-ish miles on the towpath became a slower, colder, wetter slog than I would have liked. Sean and his fast friend passed me on the towpath coming back from the aid station, about a quarter-mile from aid, which was a little bit of a blow to morale, as I had hoped to make up a little more distance here.

Due to the cold temperatures, and the tiny skirt I was wearing, leaving more leg bare than is optimal under these conditions, I didn't dawdle at the aid station, and headed back down the towpath as quickly as possible. The turnoff, on the second footbridge to the left, came sooner than I had passed Sean, which led me to believe that he had decided that enough of this was enough, and simply turned around and headed back to the start, bypassing most of the race (this later turned out to be true). This left me in first place, apparently 5-10 minutes ahead of the second-place runner, heading up what appeared to be a rough section of trail. The volunteer on the other side of the footbridge directing runners up the trail was reluctant to try to give me directions (which, in retrospect, would not have been a huge task - how difficult is "green trail, to a left on blue, to a left on red, turn around at overlook, red to green back to the towpath" to remember for an hour or two?), and, a bit frustrated with this, I began climbing the steep green trail/fire road, and worrying about how my increasingly frozen hands were going to pull out the turn sheet to keep me on track. The soaking-wet cloth gloves, which I had balled my hands into and tucked into my jacket sleeves, were doing very little to keep my hands warm, and only the fact that I had my hands balled up, recirculating body heat to the extent possible under those circumstances, was keeping me from frostbite. Any attempt to take the turn sheet out had to be completed within a couple of minutes, or else my crippled fingers may never work again.

As the snow came down harder, the green trail turned more narrow and winding, and it occurred to me that, based on prior review of the turn sheet, there was a potentially difficult turn-off on the green trail to the blue trail, and I may have gone too far and passed it. Struggling with frigid fingers, I pulled out the turn sheet, and, sure enough, the distance that I had gone seemed a bit too long, and so I turned around, brushed the snow off of an info sign along the way, and found that it was the Naval Battery location that the turn sheet mentioned was what you would see if you went too far.

Back on course, I headed further uphill, to encounter my first downed tree, due primarily to the freak snowfall on the trees, which were more leaf-covered than they typically would be when snow starts here. I then realized two things: 1.) Those shotgun-like sounds that I had heard earlier in the race were the sound of trees falling under the weight of the snow, and 2.) the tree which had freshly fallen in the path (only the slightest hint of snow on it) had fallen in the path while I was off-course, and, had I not missed the turn, I may well have been under this very large tree when it fell. As if all of this was not nerve-wracking enough, I was struggling to pull on my soaked cloth gloves and to tuck my hands into my sleeves after I exposed them in order to read the turn sheet. This slowed my progress up the hill, as I attempted, mostly with my teeth, to pull on the gloves to protect my fingers. As I progressed up the hill, a trail of footprints became apparent, and I began to wonder, since Sean had turned around, and was running with another person anyway, if the runner in second had passed me while I had spent about half a mile off-course. I decided that it was cold enough that I was just going to follow the footprints, even if they were on the wrong path, since whoever was out on foot probably didn't want to stay out in these conditions for a long time, no matter where they were going, and there would likely be help wherever they were.

All of this caused me to slow and be more cautious, and it was on the rocky downhill at the end of the blue trail to the red trail that the second-place runner passed me. He had been following my footprints, apparently, and had sped up for the same reasons that I was being more cautious. We decided to stick together, and he let me borrow an extra pair of socks and a Gore-Tex glove cover to keep my hands warm. The gentleman, Tom Kubicz, dressed in a much more weather-appropriate medieval costume, turned out to be a professor of Oceanography at Johns Hopkins Homewood campus (my undergrad alma mater), so we quickly had fodder for conversation as we descended to the overlook, then back onto the red trail, onto the green trail downhill (flying down this relatively tame trail section), and back down to the C&O Canal Towpath to the aid station where all of this mayhem had started. We also passed the gentleman whose footprints I had been following, who turned out to be a hiker with a dog (explaining the frequent animal tracks next to the footsteps), coincidentally on the same path that we were following.

I waited for Tom at the aid station, since he was taking longer than I would have, because the next section, through Harper's Ferry, was subject to complicated directions, and with minimal access to my turn sheet in the accelerating wintry mix, it seemed best to use the buddy system here. We went down the towpath, right over the canal bridge, slightly right up a set of stone stairs to a trail to more stone stairs to a graveyard to the right, through the graveyard and to the left, up a road and through a college gate to the left, back down onto the trail, down to the road and left again to loop back across a "no-bike" bridge to the right, onto a footpath which led us back to the towpath - phew! Got all that? In better weather, this would have been a lovely scenic tour of the town, and even in this weather, with more functional fingers, I could have gotten a few neat photos out of this, but at this point, I was too cold to fully appreciate any of it. We turned right on the towpath to head back to the first aid station, and the puddles had only gotten bigger and colder since we had left them last. In spite of our friendly banter, the towpath seemed interminable, although maybe it's not apparent from this picture of us heading back:


On the towpath - Lord and Lady of the Freak October Snowfall?

We reached the last aid station together, and at this point, a couple of new things were apparent: 1) Sniper and Chris, who had been patiently "crewing" for me this entire time ("crewing" which mostly consisted of making jokes about my costume and providing general moral support, so that I wouldn't think about how conditions were steadily getting worse), had firmly established my alter-ego's name as "Gerta," the steroid-pumping German, due to comments from Pam, a race volunteer, about how muscular my legs were, and 2) it was now officially too cold for that silly skirt. Tom and I left the aid station together, but Tom said that he was fading, and told me I could take off and run faster if I wanted, since I was cold, and motion was the best way for me to stay warm at this point - I wasn't insulated nearly as well as Tom was.

I scrambled ahead up the hill, up the tight switchbacks, with Tom not too far behind, competitive drive being what it is. Eventually, I lost sight of him, at about the same time that the course began to level out a bit (although it was still a gradual uphill), and also at about the same time that I realized that I probably wasn't eating enough, and was now playing a balancing game between level of exertion required to generate enough body heat to keep warm, versus energy to move forward. Or, some of the energy that I needed to move forward as fast as possible needed to be diverted to warming my body, but if I didn't keep moving foward, I wasn't going to get the benefit of the waste heat from forward progress. This was going to make the last 6 miles interesting. Although that doesn't sound like a lot of distance on paper, in practice, in drastic enough circumstances, anything can happen (see: 2011 Holiday Lake 50K, last two wobbly miles that took half an hour to complete). To add to the intrigue, the harder snowfall had now brought down so many trees that for a solid mile of the course, there was a downed tree in the path, without exaggeration about every fifteen feet. At the rate these were coming down, it was hard to believe that there would still be a forest when this was all said and done.

Nevertheless, I kept the faith and slogged through (briskly, as though Diane were chasing me, and ready to pass me at any second - ha!), passing a few more runners who had turned back early (including a very large guy - around 5'7" and 200 pounds - ambling towards the finish in a long-sleeved shirt and shorts, apparently unaffected by the cold . . . sometimes some extra body fat is convenient), and finally, a couple of hikers who confirmed that, in spite of the fact that I hadn't seen a white marker on the snow-covered trees in an uncomfortably long time, I was near the parking lot and the pavilion. I motored downhill, and sure enough, within a couple of minutes, it turned out that those car-like sounds that could have just been wind or airplanes were what I had wanted them to be, and I rolled into the pavilion, about five and a half hours after this whole ordeal began, first man, woman, and mouse to finish.


Finishing this silly thing, with a random dog. Also, note no exaggeration with respect to the snowfall.

Then the cold really set in, and I looked more like this:



Tom showed up about ten minutes later, second to finish, and we congratulated each other the best we could, given that we were both exhibiting signs of the early stages of hypothermia.

Overall, it was nice to begin my fourth decade with a win, but in particular, with a win under these conditions. It takes more than speed to finish first in a Fatass - it takes a lot of guts, self-sufficiency, and awareness of your environment to persist and make it to the finish in spite of minimal aid and no course markings. Furthermore, because Fire on the Mountain wasn't cancelled until a couple of hours after I had finished, I had been deliberately holding back a bit, under the assumption that I was going to have to run another 30-ish miles the next day under similar conditions, so I had been doing only what I needed to to get through the race in a timely fashion, win or otherwise. It was nice that that strategy turned out as well as it did, and saved my legs enough to allow me to run a 2-hour, 17-mile run the next day in the relatively warm, dry confines of Baltimore City, around M&T Bank Stadium during the Ravens game - my first stadium run this year during a game, and a huge come-from-behind win for the Ravens (down 24-6 when I passed the stadium at halftime, with folks in purple shamefully streaming out).

So that's the race, but you're probably also curious about the gear. If you are, here goes:

Hoka Mafate Trail Running Shoe Review:

In the above pictures, you probably noticed the giant, goofy shoes that I was wearing, and wondered "what on earth?" I was wearing the Hoka Mafate Trail Running Shoe for this race, the first time I had ever worn them, save for a three-mile shakeout the day before in Patterson Park just to make sure that there was nothing catastrophically wrong with them.

In the pantheon of increasingly wacky shoes these days, these are some of the wackiest, with their oversized sole and bright colors. The concept is that the thicker sole allows for more cushioning, and, in spite of the appearance, a near-barefoot 4mm heel-to-toe drop (most shoes come in at around 12mm), which, combined with a wide, slightly rockered outsole, allows for more natural running form, and saves your legs on potentially punishing downhills, while also allowing you to run faster than you otherwise would. All of this is supposed to justify a lofty $150 price tag. So, did it? (Note that I will answer this hypothetically, as I paid far less than $150 for these . . .)

Well, first off, the claims about flying downhill are warranted. The first picture in this post is pretty characteristic of how I was handling the downhills in this race. The cushioning, rockered sole, and positioning of the foot allow for a little extra "slop" in the heel-braking that inevitably occurs on the steepest downhills to keep you from face-planting. Once you're comfortable with the height off the ground, and convinced that the shoe is wide enough to provide a stable platform on which to land (because it is), you can really fly on the downhills, as the tag line suggests - they force you to engage your lower back and butt more, which helps save your quads.

That said, in my experience, they were a wash on the flat C&O Canal Towpath, and on the uphills. Some people have claimed that they are too "mushy" uphill, but I didn't notice a difference, although I am generally strong and adaptable when it comes to climbing, so I might not be the best judge of that. In this case, a flaw with the shoe, probably particular to my foot, came into play. Because the back of my heel is unusually flat, it tends to slip in shoes with a pronounced rounding in the back of the heel (which is probably ideal for people with more "normal" feet). The slippage for me in the Hokas was pretty bad, to the point that in spite of my lacing tricks, my heel was eventually slipping significantly on almost anything that wasn't a downhill. Over the course of a lot of miles, fighting the shoe this way was tiring.

As far as tread and grip on terrain, this race exercised the shoe over a lot of different surfaces - road, gravel, puddles, snow, ice, rocks. Although out of the box the shoes were a little slippery on flat, wet surfaces (I almost took a dive on the linoleum behind my front door when I was running back to the house after tossing out a bag of cat litter in the park before leaving for the race), once the race began, and the shoes were "christened," the grip improved, and, for not having an outsole specifically tuned to any one surface, these were some of the better-gripping shoes that I've ever worn (heel slippage aside, of course).

Also, these were the "waterproof" version of the shoe, and, like every waterproof shoe, that works only until your socks get wet. As deep as some of the puddles were, wet socks, and ultimately wet shoes, were inevitable. I will say, however, that after close to 6 hours in the shoes by the time I finally got them off at the finish (including 4 hours of being pretty soaked), I somehow had almost no signs of pruning or trenchfoot, so they must have at least kept the water to a minimum.

Overall, because of the poor heel fit, I definitely would not have paid full price for these. But, with a better upper fit (which, within a few minutes of putting them on, I'm sure you can determine whether or not the shoe works for you that way), these are awesome trail shoes, and definitely worth considering for long trail races. My legs didn't feel terribly beaten-up the next day (they were good enough for a relatively fast 17 road miles), which I can't totally attribute to the shoes, because, again, I was running just fast enough not to freeze, but I suspect that the shoes helped, if for no other reason than I didn't have a single bruised toenail or blister. (And, with respect to bruised toenails, being a little higher off the ground reduces the risk of stubbed toes, probably.) For me, these are an effective heel mod away from being a great trail shoe. And, for Hoka, this is another "podium" for your shoes, you know, if you care as much about those things as your website claims. ;)

Nathan VITABand Review

As people apparently read this silly blog now, sometimes companies send me free stuff to test out, and usually, I'm remiss in reviewing it. But it's a new year for me, and I'm turning over a new leaf, so here's my review of the Nathan VITABand, provided to me for free by Nathan:


Here's me wearing the VITABand, just before all of that stuff above happened.

The Nathan VITABand is a Livestrong-style bracelet with a unique identifying number on it that you can link to an online profile with your medical history and emergency contact information. In the event that you, say, foolishly venture out into the cold, snowy wilderness underdressed, run out of food and water, and freeze to death, somebody can at least identify your corpse. (And if you're still alive, they might even be able to call the number on the bracelet and get you appropriate help.) The bracelet can also hold chips with your info written on it, so that the person who finds you doesn't have to call the phone number on the bracelet to ID you, and a pre-paid debit card chip, which you can use at places that accept pre-paid, touchless payment methods. Fancy.

I had just received the bracelet a couple of days before the race, so I didn't have either of the chips for it yet (they come in the mail once you fill out your profile online), but I figured that since it matched my outfit (it was hot pink - not sure if it comes in different colors), it was at least a fashion statement, if not a precaution in the event of a catastrophe on a mountain. So I really can't vouch for it saving my life, but I can offer some initial impressions:

Good:

- Pink color looks cool, is highly visible, and supports breast cancer awareness ('tis the month . . .)
- Lightweight
- Easy-on, easy-off
- Fits securely
- Holds a lot of information in a neat little package

Bad:

- Time-consuming data entry online (but basically a one-time thing)
- Subscription service ($20 per year; not backbreaking, but still not free)
- Cats think that it is a small snake and try to chew on it (mine has teeth marks in it now, and is missing the placeholder "debit" chip . . . although that's better than missing a real chip)
- Pre-paid debit service is as useful as touchless debit is available and as much as you pre-pay (which I typically do not do)

But all things considered, this is a compact, sturdy ID system, probably the best on the market in that regard. The subscription fee might be cause to balk, but at the same time, it's not terribly expensive for a little peace of mind. I wish that the touchless payment was credit, as opposed to pre-paid debit (personally, I would me more likely to use it if it were credit), but they could probably modify that without having to modify the bracelet itself. If you can keep it away from curious cats, and the subscription model doesn't bother you, this is arguably the best bracelet of its type out there.

And with that, I've written more than my share of words for the week. Now, back to running . . . :)

Sunday, February 20, 2011

13-19 February: Week in Review, MMT 100 Preview


FIRE!
Okay, I didn't mean to clear the crowded theatre, but apparently, this stupid website really, REALLY wants me to, since no matter how many times I try to post this picture from this weekend's MMT Training Run at the END of this entry (the count is at about 5 now), it stubbornly inserts it at the BEGINNING, and adds three extra spaces after each paragraph for good measure. If this is some easy problem to solve, and you're laughing at me right now for not being able to fix this, then at least I've managed to entertain. (And wherever it winds up, or whatever horrific website it probably links to now, since who knows what else this website insists on insidiously breaking, it's still a cool picture.)
But if you're still reading . . . the business:

13 February: 10 miles (73 minutes), Canton/Fells/etc.

14 February: 6 miles (45 minutes), Patterson Park

15 February: Butcher's Hill reps (4, in 2:52, 2:51, 2:54, 2:56), 9 miles (60 minutes)

16 February: 3 miles (23 minutes), APG

17 February: 7 treadmill miles (10:00/mile, 10% grade), +1 mile warmup/warmdown (77 minutes total)

18 February: 6 miles in the morning (45 minutes), 9 miles in the evening (65 minutes), Patterson Park

19 February: 32-ish miles, MMT 100 Training Run #2 (6 hours, 42 minutes)


Total Time: 790 minutes
Total Distance: 83-ish miles

So, in summary, slight mileage bump-up, good distance, good intensity. Overall, a good week.

Also, on Friday, 18 February, I was accepted for Badwater 2011 - more about that in another post, but for now, suffice to say that I'm excited, and thank you to Natural Vitality Sports, my sponsor for this event.


. . .


This wouldn't be a typically verbose post if I ended it there. So for the rest of your attention span, I'm going to carry on about the Massanutten Mountain Trail 100, the greatest 100-miler I never ran (but am excited to finally be running for real this coming May). Get ready for disorganized discussion of the course, my race strategy, and maybe some other stuff that doesn't quite fit.

In the interest of qualifying myself for this mini-dissertation, I completed the Old Dominion 100-miler in 2008 (from which MMT 100 plagiarizes parts of its course), paced runners at MMT in both 2009 and 2010 (2009 was the year of the torrential overnight downpour), and ran substantial portions of the course during my attempt at The Ring in September 2010. Oh, and there was the training run this past Saturday (http://www.vhtrc.org/events/academy/two/). For those of you who can't be bothered to click on the link, the training run covers about 30 miles in the middle of the course, which contains a mish-mash of terrain - everything from gently rolling gravel roads to rocky, technical, semi-exposed single-track, for a grand total of nearly 6,000 feet of climb (and around 5,500 feet of descent). All in all, a fair representation of the course as a whole.

The 6 hours and 42 minutes that it took me to complete this 30-ish mile section of the course doesn't sound too eye-popping. However, considering that I was running at "100-mile pace," this went very well. I ran (a conservatively estimated) about 2 miles off-course when I missed a turn onto the yellow trail heading towards Shawl Gap, and debatably took a wrong turn on the orange trail on the Veach Gap Ridge (opting for the leaf-covered, narrow, cliff-face-style exposed low road, as opposed to the wide, gentle, comfortable horse trail on the high side). Subtract about 20 minutes for shooting the breeze and having pictures of my cut-up MT100s next to somebody's giant puffy Hokas taken at the aid stations, and for taking pictures of the Shenandoah River and a fire in the valley and posting them to Facebook during the run, and add in a little bit of extra hustle assuming that I don't screw up my nutrition during the race, and I'm looking at a very comfortable 6 to 6.5 hours to finish what I would consider a very representative third of the race, a pace that would put me on track to finish between 18 and 20 hours. (Incidentally, the course record is something like 17:40).

All of which sounds outlandish for a city slicker who exhibits an occasional dislike of trails. And of course, there are a few things that could throw a wrench in the works: the weather (it's been brutally hot and unbearably cold there, all in the same race), poor nutrition, some really horrible section of trail that I forgot about, a stupid decision that causes me to get injured during the race, getting lost, probably a lot more things that I can't think of off the top of my head right now. With methodical preparation and good ol' common sense, the effects of these can be minimized, and rest assured I'll be compiling and cross-checking this list with appropriate mitigation strategies prior to race day.

But let's focus on why I think such an aggressive finishing time is achievable. First, I'm gradually coming around to the "trail running is the only kind of running" camp, although I will never give up my late-weekend-night runs around Canton, Fells, and the Inner Harbor (the drunken hecklers are too funny, and the homeless people usually say nice, encouraging things to you, when they're not shouting random racial slurs), and I refuse to grow a beard (I'm not sure that I could in the first place). In particular, I love the trails in the Massanuttens, as I've now amassed sufficient memories on them for the thought of a late-night, headlamp-guided, caffiene-addled rock stumble to get the adrenaline and endorphins flowing. In fewer words, mega-positive mental state about this race, but not the kind that's totally disconnected from reality. Yes, at times it might be miserable and hurt a lot, but for the thrill of power-hiking a steep incline, then reaching the top and barreling down a rock-strewn mountain at breakneck speeds, it's more than worth it. It's compelling enough that I now go out of my way to run on the grass in Patterson Park, or wherever else would otherwise be too "urban" to simulate trail running.

Second, patience and consistency are my strengths, and I believe these are also the key to running well at MMT. In many ways, MMT can be an infuriating race, especially for the front-running types that insist on dropping sub-6 minute miles where they can early in the race. By and large, the trail sections are very rocky and technical, and require a huge amount of coordination and patience to navigate successfully. When you're playing "track meet" from the start, you're chipping away at that reserve that you're going to need when you're sleep-deprived and trying to wade through a sea of rocks at mile 93. I've seen broken-down runners in 100-milers, but the breakdowns at MMT have definitely been the worst. Burn yourself out too soon, and you'll pay dearly at the end of this one.

Third (and following closely on the heels of the second point), I proved to myself this past weekend at the training run that the kind of effort needed to run sub-20 hours at MMT should be within my limits. I finished the training run feeling as though I could do it again (and again), and ran 9 miles the next day, without any significant soreness or lingering effects of the run. All this by fast-hiking the climbs, letting momentum carry me on the downhills, and settling into a steady pace on the flats. Overall, I felt as though I had a good, consistent effort level dialed in for the duration of the run.

Taking all of that into account, my race strategy: Stay steady, let the inevitable "track meet" at the front of the pack go on without me. Comfortable 7-ish minute miles on the flats, power-hike the uphills at about 15-minute miles, roll the downhills at whatever gravity will allow, within the limits of my knees and quads. (And definitely no walking the downhills, as that is a sure way to wreck my knees and quads.) 200-ish calories per hour, mainly in the form of gels, wear the Nathan bottle belt (as I have better balance with this than I do with a bottle in my hand on the steep downhills) and the MT100s (unless I can sufficiently break in the MT101s). Enjoy the day, gradually reel in the people who went out too fast, and if I don't feel completely wrecked in the last 10 miles or so, give it everything I have left. And do something cool after the race (TBD).

In conclusion, if you were wondering why this post is entirely in red, it's because in addition to not putting my picture where I want it, this stupid website also insists on changing the font size and font color semi-randomly in various sections of this post, and, honestly, I give up. Red on black = visible. Whatever, blogger. I guess you got paid, so does it really matter?