Lance Armstrong, Antihero

From the beginning, the idea of Lance Armstrong the athlete was inseparable from the perception of him as a man. The 1999 Tour de France crowned a new champion and gave us fresh evidence that raw willpower, pure guts and grit, is enough to win in life. It was not so much that our champion survived a fierce cancer, which was admirable, but that he seemed to defy his own mortality by superior strength of character. With a titanic power of spirit, it seemed, he averted his own death and won the most important stage race there is.

And so, when we watched Lance Armstrong dominate the opening time trial in 1999, when we witnessed him assert his lead and cement his legacy in the Alps, we saw a man waging what appeared to be, for him, another life-and-death battle, and we were rooting for the man as much as we were the athlete. The sneer, the muscles, the grip on the bars—he appeared a prism of unbridled intensity, but more than that, he was indignant. Defiant. He competed like he was possessed, and he was determined to win. It was as if the black-and-white schematic of winning and losing drove him up those mountains as a compulsion, a matter of course.

Win is what he did—more often and more convincingly than any other cyclist in history. He won what is perhaps the most grueling endurance contest ever devised. And he kept winning. There were moments–Hautacam in 2000 and Alpe d’Huez in 2001 come to mind–that he seemed immortal.

Next to this colossal figure, other great athletes were exposed as mere mortals. Jan Ullrich had a classic Ben Jonson problem—he was a fine playwright, and at any other time he would have been the best, but by lousy luck he lived in the age of Shakespeare, who took the gold at every medley in town. When Ullrich looked to his right in the final minutes of the first time trial at the 2005 Tour (his last) only to see the Bard himself making the pass, the slowness that seemed to wash over his body was palpable, and you could feel the sadness and disappointment of coming second place.

Lance Armstrong met sport with the same objective that he met death: win at any cost. The will to win is a powerful human force, but like anything else, it can dement, corrupt, and destroy when unrestrained. And despite what we wanted to believe about Lance, the will to win, and the ability to, says little that’s instructive about character. One can hone the body to perfection while rotting inside.

Even before the dominoes of the peloton collapsed and revealed the dirty truth about cycling—that use of performance-enhancing drugs was de rigueur among the riders, that cheating was the norm—the ideas of the man and the athlete began to decouple as inconvenient realities emerged. There was the infidelity, the interpersonal strife, the bullying and the meanness. But we fought this decoupling for years, because we wanted to believe that Lance Armstrong was, at his core, at least half the man that he was the athlete—we wanted to believe there was something heroic at play, and heroes do not dump their wives on a beach.

We do not demand perfection from our athletic heroes, but we need competency. Lance, too, seemed to intuitively grasp what he should be as a person. There is now considerable irony in what he wrote in his early memoir: “I believed I had a responsibility to be a good person, and that meant fair, honest, hardworking and honorable. If I did that, if I was good to my family, true to my friends…if I wasn’t a liar, a cheat, or a thief, then I believed that should be enough.”

When we learned the scope of the lying and cheating, it disaggregated our notion of Lance Armstrong the man and Lance Armstrong the athlete, and it sullied both. That’s the tragedy in the fall of Lance Armstrong—his failures as a man eradicate his achievements as a sportsman.

Long before he won the Tour de France seven times, years before he experimented with endogenous erythropoietin protein, with testosterone, with masking agents, Lance Armstrong was a budding champion with an uncommon capacity to convert oxygen to energy—just a young kid with an exceptional aerobic metabolism. Here was an athlete with a massive engine and enough ego to require victory, who harnessed his physiological gifts to win races, and inspired all of us who watched him succeed.

The many wins of Lance Armstrong are now muted. Still, we cannot let his tragic frailty erase what we know of his greatness–his drive, his courage, his strength. We should strive to remember him not as the polluted villain he became, but as the champion he more often was. In the final analysis, we define ourselves more by our triumphs than our transgressions, but we are harder on our idols. That’s a mistake. Lance Armstrong, for all his faults, remains more good than bad, more winner than loser, more hero than antihero.

Advertisements

Marathon Training

I kicked off marathon training last weekend with my longest run ever (20 miles). For my long run, I employed a foolish strategy of taking no nutrition or fluids. This was intentional. A compelling comment on the fall marathon thread on Slowtwitch had me thinking–a poster had admitted to a curious method of letting himself “bonk” on long runs during marathon training in order to become familiar with hitting the wall and to practice pushing through it. That sounded really hardcore, so I was game to try it.

I found the wall around mile 17, and it was like nothing I’ve ever felt. Bonking on the bike is mostly a fatigued, crappy feeling that develops over time–the long run bonk felt musculoskeletal, and came on instantaneously. My legs were suddenly leaden and crampy and every stride felt forced. The final three miles were as hard as the initial 17, for which I settled in at around goal M-pace +~0:10 without too much trouble (definitely very hard, but manageable).

Now I know what marathoners are talking about. I think the forced bonk was actually a valuable exercise, though I wouldn’t wish it on another. The key is to not experience this during a marathon. If you are trained properly, and if you pace properly, you shouldn’t find it on race day. Here’s hoping.

What’s Next?

First, rest. And a lot of Chipotle burritos. Some booze and NFL and late nights. And a bit of a work block if you will–time spent focusing on my real job. Generally, healing physically and recharging mentally while unwinding a little bit to take my mind off triathlon. However, it will be good to get back out there–I am beginning to suffer from the condition known as post-Ironman (70.3) depression–the emotional and physical funk triathletes slip into soon after completing the athletic goal they’ve been focusing on for months. Google it–it’s sadly a real thing.

Run: Once I feel up to it, I will start training for the Philadelphia Marathon, which will be my first crack at the distance. I was on the fence for a while because I wasn’t sure my hip would cooperate for a running focus. Further, I am sure an open marathon is not the best thing for me as a triathlete. However, I want to experience 26.2 as a distance without 5-6 hours of exercise beforehand. And I like to run, so there’s that. My reach goal is to pop under 2:40, but that is contingent upon actually getting respectable run mileage completed while keeping in check all the various pains that running invariably inflicts. I know a sub 2:40 (and possibly sub 2:35) is in me in life, I just don’t know if I will be able to do the necessary training to get there in the next 6 weeks. I plan to keep the engine tickling over in cycling and swimming, but I won’t be logging much volume.

Swim: Then, I’ll let my running injuries heal as I put in a 6-week swimming block (*shudder*). This will consist of swimming nearly every day and logging upwards of 25-30 km per week. I may do some of this with a local master’s squad to keep it interesting. Unfortunately, I need to do this because a) my swim was by far my weakest split in my last race at Pocono and b) I have stopped seeing improvements with the 15 km or so I have been logging. Below, especially by looking at the 6-week moving average (the black line), you can see that I got a lot faster at first and a little bit faster as I increased volume, but this improvement has largely stagnated.

I haven’t done enough research to know what kind of training I need to do (e.g. should I really start doing strokes other than freestyle?), but I know simply swimming more is fundamental to every school of thought on fish development.

Bike: Finally, around the new year, it will be time to raise the left even as I fill the right on the bike–that is to say, I plan to work on my threshold power while doing a lot of endurance and sweet spot riding…a lot of riding in general, really, up hills and through valleys, on the road bike, on the tri bike, on the trainer…I may even join a few spin classes. My goal is to go into next season with a ironclad threshold power of 300 Watts. I like the roundness of that number, and it would represent a healthy improvement of about 5% compared to where I am now.

“The Beast” of St. Croix 70.3

Triathlon: In March and April, I’ll be hammering on all three disciplines during the most important build yet–and on a fourth discipline, too, which is heat training–in preparation for Ironman 70.3 St. Croix in May and Ironman 70.3 Eagleman in June. Both will be hot, both will be hard, and both fields will be stacked with top-caliber competition.

My early goal is to ride St. Croix at this year’s half-Iron power but with an Intensity Factor closer to 0.8 than 0.9 (i.e. at 80% of my threshold power) so that I can have a very strong run. The run at St. Croix (and the stifling heat and humidity) is notorious for chewing up athletes who push the very difficult and hilly bike–not just newbs either, many a top pro have crumbled during the last leg on that island.  If I can bike well but easy enough to set up a solid run (“solid” means under 1:25 given the anticipated conditions), it will set me up nicely in the age-group race.

While you can’t control who shows up and who performs on race day, I’d be remiss if I didn’t state flat out what my macro goals are for St. Croix (or, failing that, for Eagleman): the Kona slot. That’s right, I said it…I want to race the biggest and most important race in long-course triathlon on a pristine tropical island against the best triathletes on the planet. I want to do the full 140.6. But I want to own the half Iron distance first and prove that I’m ready to go long and that I’m ready to take the heat. St. Croix is like a mini Kona–my performance in the Virgin Islands will either confirm or deny my readiness for Hawaii. (Ironically, I may be so broke from these races, plus Vegas 70.3 World Champs in September, that I can’t afford Kona, but I guess that’s what credit is for.)

Most importantly, I want to keep having fun with this thing. Towards the end of this season, I was feeling awful physically and burnt out mentally. Sometimes you just need to go out and enjoy a bike ride or a run and forget about what it says about you as a human.

Ironman 70.3 – Pocono Mountains Race Report

Pre-Race / Goals: In late June, I scribbled down some specific time goals for this race (my end of season “A” race). I kept this paper pinned up at my office. I knew the bike target was a stretch, since I had averaged roughly 21 mph and 22 mph in my first two Olympic-distance bike legs (my first two triathlons, raced without power)–so I was aiming to ride much faster for more than twice the distance. I thought that such a ride would trash me were I even physically capable, so I penciled in a 1:25 half marathon, which I knew was well within reach if I could maintain my run fitness though the fall.

Original Goals

It was cycling, however, that was the weak link. In the weeks that followed, I invested money, time, and sweat in my cycling–I bought a power meter and set out on harder and longer bike rides than I’d ever done before. I had to learn to push on the pedals–by focusing on power, I was logging my hard rides with an average heart rate almost 20 beats higher than I’d ever seen before for long rides. At the beginning of power training, I figured 225 watts would be a reach goal for Pocono and would likely get me close to my goal time. But I surprised myself out there–the numbers on my rides were progressing almost linearly through the end of summer. I did a 20K time trial at 298W, indicating a threshold power 15 watts higher than I’d pegged prior. I logged an 82-mile, four-hour ride in the Poconos at 238 watts followed up with a hard trail run. At Delaware Diamondman, my dry run/dress rehearsal for Pocono, I managed 251 watts (~3.9 W/kg) for 52 miles (course was short) and had a decent run.

Everything seemed to be set, except my first half Iron in Delaware levied a heavy toll. Despite taking more rest than I ever wanted to or thought I would need, I just couldn’t train like I had been training. Race power felt arduous and forced, whereas before it felt steady and smooth. Even during easy “active recovery” workouts, my heart rate was much higher than it should have been for my fitness. I crumbled completely during several sessions–I could run 6-minute pace for a few short miles before fatigue permeated my quads and hamstrings and crippled my stride, after which I’d be tired for days–and I wondered if I hadn’t burnt out my body right before it mattered most. I tried to rest as much as possible without losing my fitness…I focused on good sleep and good eats–I even had a few salads, so desperate were these days.  “Sharpening” workouts–fast intervals at threshold or V02 max leading up to a key race–were out of the question.

Pre-Race Logistics

So I went into Pocono worried as hell about a blowup–even in my shakeout ride the day before, my legs were wooden and flimsy like driftwood. Every data point I had indicated a poor race was coming. But to paraphrase a Chuckie V comment, a heart rate monitor cannot measure heart and a power meter cannot measure will power…my goals remained: swim strong, ride 245 watts average or around 250W normalized, and run a low 1:20s half marathon. Secondarily, I hoped to qualify for the 70.3 World Championship in Las Vegas. In the back of my mind, I thought that if I felt great out there (like I did in Delaware) and was able to pump higher than planned wattage, and depending on the days others were having…an amateur title was within the realm of possibility.

Swim: Going into the swim, I had hoped to find the legs of Bill Robertson, who I chatted with before the race. I knew Bill had outsplit me by about 30 seconds on the swim at the Red Bank Tri in May (before he went on to claim 2nd overall and crushed the bike). My swimming had improved since then, so I thought I could keep his pace. The start was a whirlwind of flying arms, and I had no sooner earned some space from my wave than I caught up with the slower swimmers from previous waves–the Clydesdales and the like, who created frustrating obstacles. I saw a white cap (my wave) to my right and swam roughly in line with it until the turnaround, then made an effort to bridge over to it. As it turned out, I found myself on the legs of an Xterra wetsuit, and I surmised it was Bill. I followed him through the end as we weaved in and out of slower age groupers. The swim was more an obstacle course than anything, so it wasn’t physically taxing, but we got out of the water with a solid split around 25 minutes (it may have been a bit short). Frankly, I was disappointed not to have had a chance to really swim hard and reap some reward from those exhausting, god-forsaken pool sets, but my swim fitness at least ensured I was fresh starting the bike.

BikeI hustled through transition, hoping to sneak out and get a jump on Bill since I knew I needed it with his bike skills (he split ~64 min to my 71 at Red Bank). I tore out of T1 and down the 4-mile descent, which I knew from riding the course required no brakes and no time on the hoods. Despite weaving around terrified riders while screaming “on your left” repeatedly (and crossing over the double yellow lines numerous times to avoid catastrophe), I set a new downhill speed record at nearly 52 mph, around the same max Jordan Rapp achieved at Leadman…I’m finally growing some balls for descending.

Flying Dismount #Fail

Then I went to work. In line with my recent training, my legs felt absolutely terrible. I was holding race power (~250W) but it required constant attention to my Garmin and troubling strain. Thirty minutes into the ride, I thought I would be dropping out of the race. I’d ridden 15 miles at race power and my legs felt like they’d seen 80. What kept me encouraged was the thought of my girlfriend Emma and parents waiting to cheer me on at mile 35, and also my speed–my 5-mile splits were reading faster than I’d anticipated given my power output…I tried to convince myself that my power meter was off, then, failing that, that my new latex tubes and race tires were working overtime to save my powerless prime movers. If I could just get through this bike ride…

I did, and it hurt like hell, and my legs felt like crap, and I hated weaving around 500+ riders, many of whom had no business being on the left side of the lane. And I hated the downhills where power, then confidence, flagged. And I hated watching my average power drop below 245, to 244, to 243, to 241…but I finished the ride and, despite having had no strong running under my belt in weeks, I thought I just might have the residual fitness to crush it out there.

Run: The crowd support through T2 was a big boost–having my own supporters there and high-fiving my dad early in the run had me jazzed. I saw my bike time (~2:21) was phenomenal given how I’d undershot my power goals, and I calculated that with a good run, a sub 4:15 time was within reach, which meant the high likelihood of an age-group win and a fighting chance at an amateur title. My first half mile flew by at 5:40 pace, then I settled into a more comfortable rhythm around six flat with my heart rate in check around 175. I had also been holding my hydration for quite a while–I had just cleaned my bike!–and it was a nice load off when I let that go around mile 2, right around when I saw Jesse Thomas cruising to victory…seeing him charging forward with a commanding lead–it was a motivating sight.

Hauling out of T2

Even though my legs were in pain, I felt aerobically strong–it was just a question of cramping, general muscular fatigue, GI issues, and electrolyte deficiency (i.e. the unknowns in any endurance event). After some cola at mile 3, I could not take more fluids, and the thought of a Gu repulsed me. I set my sights on competitors up the road, who were few and far between but close enough to create a game as I reeled them in. The turnaround seemed like it would never come, but when it finally did, I was pretty sure I had a good race wrapped–I was on pace for a 1:21 half marathon if I could even split, and the run back to the finish was rolling but net downhill. I just needed to open up my stride on the the descents and keep within myself on the climbs.

With a mile to go there was one short but cruel hill, on which I caught two runners and surged past them. It was a regrettable move, as my stomach immediately developed a piercing side stitch that felt like a knife in my abdomen. I slowed as I approached the finish, but when I turned the corner for the home stretch, the crowd noise was deafening and I sprinted home with everything I had. After crossing the finish line, a volunteer approached me and made a joke about the hills–I wanted to laugh but the senses were drained from my body, and I stumbled, almost falling over. I was dizzy with fatigue, but I was finished. I had run under 1:21 for the half marathon, logged a total time under 4:12, won the Men’s 25-29 age group (qualifying for Worlds), garnered the overall amateur title, and beaten a chunk of the male pros.

Finished

Postscript: Despite my trepidation heading into my key race and my fatigue issues during, I had nearly achieved my pre-race goals, and blew to shreds the targets I’d set in June. In just a couple short months, I have become a real cyclist–the development of which I am most proud. From my first tri in May, where I split a pedestrian 71-minute 40K bike leg, to where I am now, with an approximate threshold power of ~4.4 W/kg–I have bridged a wide chasm. There’s still much work to be done–by way of comparison, Jesse Thomas swam several minutes faster than I, and he’s known as a poor fish who learned as an adult; he rode 10 minutes faster and probably 50-75 watts higher (his threshold power is likely more than a full W/kg above mine); and my run is not comparable to his either (he ran sub 1:15). Even with the last leg being my strength, 22 miles per week average run mileage is not going to cut it as I look up the leader board.

Coincidentally, it has been exactly one year since I officially (in my mind at least) entered this sport, having started my training log on October 1, 2011. 533,000 swim yards, 5,600 bike miles, and 1,150 run miles later, I have found something important in triathlon: a vocation that is as uplifting as it is debilitating, that crowns psychologically as it crucifies physically, that makes me weary beyond words and cripples me, even as it bestows strength and self-assurance, and ultimately makes me better. It has been a good year in the sport–the first, I hope, of many.

Training Week: 9/8-9/14

Swim: 17,600 Yards (4:02) 
Bike: 145 Miles (6:48)
Run: 23.5 Miles (2:54)
Total*: 100 Points (13:44)
————————————————————————

Swim: It looks like I did a lot of swimming this week, but very little of it was hard, so I feel like it was significantly less. I capped the week with a 5K pull in the pool–by far my longest straight swim ever, and with a buoy between my legs. It felt like doing a really boring long run (it took almost 80 minutes). I got the idea in my head while looking at the Leadman 250 race, which includes a 5K swim–I wondered what swimming that far would feel like, and I was trying to let my legs recover so I turned it into a pull workout. I probably won’t be doing this again any time soon.

Delaware Diamondman Bike

Bike: After the Delaware Diamondman on Sunday, my legs were more or less trashed all week. I logged a moderate 55-mile ride in the middle of the week, but the high power just wasn’t there.

Run: On Monday and Tuesday, my quads were so tender I was having issues going up and down stairs and walking back and forth between my apartment and the office, so running was out. By Thursday, the sharp pains had subsided and I completed my typical hill session, though my legs were still carrying quite a bit of fatigue.

Total: Following Sunday’s race and in advance of my season finale 70.3 on September 30th, this week didn’t contain a whole lot of training. I am a little disappointed in the slowness of my recovery from the race, but since it was my first half iron distance I probably shouldn’t be surprised. With two weeks to go until Pocono 70.3, the hay is pretty much in the barn, even though I would have preferred to stuff a little more in there with some harder workouts this week.

*I have a non-standard system for quantifying my training output. (Swim Miles x 4) + (Bike Miles / 4) + Run Miles = Total Points. Listed time is time spent swimming, biking, or running, not rest between intervals, walking, etc.

Race Report: Delaware Diamondman Half Iron

Goals: My general goals for this race (my third tri and first half) were to get a great workout in, to experience the half Iron distance for the first time in a low-key venue, and to test my nutrition (mainly water and Gatorade as needed, a 600-calorie bottle of Maltodextrin-enhanced Ironman Perform on the bike, SaltSticks, and a gel during the run). My specific goals were to swim steadily, average 235-240W on the bike, and run well. I didn’t have any time goals in mind for the run because it was an offroad/cross country style course (that turned out to be long) but I wanted to have a strong final leg.

Pre Race: The 4:15 a.m. wake-up call came and went, and over the next two hours, I methodically ate breakfast (oatmeal cooked in almond milk with two bananas, half a Clif bar, and coffee), loaded the car, drove to Delaware, and set up my transition area. The water temperature was 0.5 degree below the cutoff of 78, so it would be wetsuit legal.

Cocked and Loaded

After the pre-race meeting, which started about 10 minutes late, the athletes walked the 3/8 mile from the transition area to the lake. Since everyone was together, I wasn’t rushing to the starting line even though it was already well past the posted start time. When we arrived, the announcer was already corralling athletes in my wave (which was first). My wetsuit wasn’t even all the way on yet, and I hurriedly put my arms through when the announced balked “90 seconds” as I was still 100 yards from the line.

Then, at literally the last minute, I realized all the shoes lined up at the edge of the lake were placed there by athletes who were planning to slip into them after the swim for the trek to T1. I had planned to run barefoot as I thought others would. Luckily, I had my shoes. So I had to rush to arrange my laces in such a way that I would be able to get into them easily. Then I sprinted for the line putting on my cap and goggles as I ran. I arrived with less than 15 seconds to spare. Amateur hour.

Swim: I was lined up all the way to the left, and by coincidence started right next to the token uber swimmer (at every triathlon, there is at least one former collegiate or stud club swimmer, who may or may not be a good triathlete but destroys the field in the water). Had I been more prepared for the start and more aggressive at the gun, I might have gotten on his feet. Instead, I opted for a more relaxed start, thinking that I’d leech off a less torrid pacer. Soon, I realized the next best swimmer (merging in from the right) was quickly fading and was going to be too slow for me, so I forged ahead. For the first 500 meters, the top guy couldn’t have been more than 15-20 meters ahead, but when you’re already pushing and trying not to go hypoxic, bridging that gap is extremely difficult.

At the turn buoy (roughly 800 meters), the margin to the leader was insurmountable and I was feeling fatigued in my shoulders and overheated in my wetsuit. Doubts started to creep into my mind about blowing up on the first leg in my first half Iron. On the return, I concentrated on maintaining a more relaxed pace and sighting off the splash of the leader’s stroke (with the sun immediately ahead, it was nearly impossible to see the sparsely placed buoys). With about 400 meters to go, I was feeling terribly hot and slowed down perceptibly. The leader seemed to double his margin in the last section. After what seemed like an eternity, I was on shore to cheers and encouragement. Delirious and stumbling around, I almost put on another athlete’s shoes (seriously though, who else has bright yellow shoes?). I struggled to pull down my wetsuit, which I was dying to get out of, as I was jogging toward T1.

My swim split, inclusive of the jog to T1, was 29:47, so I was likely out of the water in around 27 minutes, about what I’d hope for and expect for a wetsuit swim.

Bike: The lead man, who had put 90 seconds into me on the actual swim, had a poor jog and T1, and I arrived at the mount line just as he took off. At the outset of the bike, my legs felt strong but my heart rate was out of control and I was still feeling a bit seasick, if you will. I just concentrated on keeping my power numbers under control (the urge to push 300+ watts and take the lead was strong). I settled into a rhythm and passed authoritatively within a couple miles, and from that point on I had a lead vehicle escort to clear traffic.

Sky High Heart Rate at the Bike Start

It was then I realized I felt good–damn good, actually, given that my power was at 260W+. My peak 20-min power was between 5 and 25 minutes (263W) and it felt reasonable. For the next 20-25 miles, there was nobody in front and nobody that I could see behind. Although I knew the field wouldn’t be deep, I knew there would be some studs (as there always are) and there would be others gunning for the win. With data from my Garmin and a skewed-by-willpower perception of exertion, I had a savage internal dialogue about whether or not I was going too hard.

On one hand, I had rested and my legs were feeling strong, and with the competition effect perhaps my target wattage had been a low ball. I thought of an interview with Andy Potts in which he mentions that his physiology is unique such that his half Iron race power is 30W higher than what he pushes in training. On the other hand, I had pushed 251W for 56 miles in training just weeks prior–on these same roads, no less–and had written accordingly:

The [251W] effort took its toll–I felt trashed at the end despite proper fueling. Had I needed to, I doubt I could have run a fast half marathon in that state. So I learned something important with the workout: my 235-240W target for half-Iron competition is probably right, even though I’m capable of better.

My heart rate started to come down (+1 for the keep pushing side) but my perceived exertion rose predictable as the miles clicked by (+1 for the tone it down side).

Devil: “If you slow down, you’re torched. So what if you’ve spent some time at the pool…the uber cyclists are coming for you. All you’ll see is the back of a Super 9 sailing away to victory if you ease up now. You’ll never catch them on the run.”

Angel: “You are the uber cyclist, man. You’re pushing 4 Watts per kilo. That’s more than enough. Settle it down to 3.8 so you can bring it on the run.”

And so it was for the first loop…then, during the back half of the race, my legs started to get crampy. Stupidly, I had decided to leave my SaltSticks in T1 since it was a cool day. I began feeling twitches in my calves and hamstrings, and getting out of aero (for a couple sharp turns) caused my right hammy to seize up entirely, and I had to coast and stretch several times. Besides the cramps, I was tiring but not dramatically so–250W required roughly the same strain as 260W had at the start. My heart rate was within a reasonable range and I just concentrated on staying comfortable and relaxed while holding 235+ and easing down to 200W as my hamstrings periodically threatened revolt. The last section was strong (250W+) as I was thrilled to be close to getting off my bike.

All said and done, I’d pushed an average of 251W (3.9 W/kg) for 2:08 at an average speed of 24.3 mph for 52 miles (the course was well short of 56, which I knew from having ridden the course). This was far and away the fastest ride of my life–my recent bike fit was already paying dividends.

Run: Coming into T2, I knew strategically that if I could keep my cramps at bay and not crater spectacularly, I would likely take the race with what I knew was my strength. I took a long time in T2 swallowing several SaltSticks, putting on socks, and drinking some more Malto/Perform. As I was about a mile down the road, little did I know the chase man had scalped 80 seconds of my lead during transition alone–my 2+ minute T2, and his 40-seconds one, could have been decisive factors in a different race–and he was a good runner too.

I took advantage of the first couple miles being flat and dry to cruise at 6-minute pace. My lead biker cleared the path, which was still crowded with sprint competitors, allowing me to focus on maintaining a steady pace. I could feel the liquid sloshing around in my stomach–not comfortable–and could not take any more fluids. With an early out-and-back section, I got a split on #2 and #3, who were running together and looked like they were absolutely crushing it out of T2. They were three-minutes from the turnaround, so roughly six back. I had a workable margin.

Seeing the other top guys motivated me to push hard for the next stretch, the cross country section of the course, which had short, punchy little hills with terrible footing–having rained the night prior, water puddles and slick mud were everywhere. I nearly lost it completely on a couple spots and my pace slowed drastically. The racing flats I’d worn were clearly meant for the roads. As my Garmin showed splits in the 6:15 to 6:25 range for the next 4 miles, I kept reminding myself everyone was on the same course and would be slowing too.

At around 7.5 miles there was another opportunity for a split on the chase group, and I was hopeful that with the pace I was pushing through the terrain, I’d be opening up my lead on second and third. This was not the case, as I clocked about 3:10 to the turnaround point (6:20 back). I’d made up only 20 seconds in 4 miles of hard running–these guys were running around the same speed as I. However, I knew that they too were checking the split and, in about 3 minutes, would see they weren’t making up any time at all. This would be harder news for them than it was for me.

Having seen the competition, I flew through the next 1.5 miles in 9:10, leaping aggressively over puddles and working the sides of the trail.  By around 10 miles, the split on #2 was 3:30 (7 minutes back), and #3 had faded from contention.  It was good news, because I was toast. To no avail, I took in a gel with 25 mg of caffeine in hopes of maintaining some semblance of a respectable pace. I hadn’t been able to take in fluids for about an hour. Mile 11 was around 6:50, which I knew was about my “stumbling home exhausted” pace from recent long runs. Miles 12 and 13 were worse yet. I hit 13.1 in around 1:25 and I wasn’t even close to the finish line–it was a cruel, cruel trick.

The consensus was that the course was 13.7 or 13.8, or roughly 5-minutes long, but I finished in 1:29:48, staggering into the chute at what felt like 9-minute pace, dehydrated and exhausted…but pleased with my race. My total time was 4:11:27.

Postscript: Taken together, the race was good. Performance wise, I was second out of the water for the men (third fastest overall), split the fastest time on the bike, and eeked out the fastest run split despite the late crater. I was able to stand on top of a triathlon podium for the first time and received a nice Polar running watch.

I learned a lot, but I made some critical mistakes. Ultimately, given how I finished the run, I may have gone about 5-10W too hard on the bike and/or cooked it a little too much in the first half of the run. I should be capable of a sub-1:20 half marathon (on normal terrain), and I don’t think my performance Sunday was equivalent (maybe 1:22 to 1:23). I need to work on transitions and carry the proper supplements at all times. The cramping, while a big concern because it can ruin a race, may have had more to do with my new fit utilizing the hamstrings in a different way (and not being accustomed to the strain) than any mistake on my part, but I need to investigate it further and try to recreate it and contend with it in training. I clearly need to work on my transitions. Since I’m not concentrating on the Olympic distance, I figured I could get away with weakness in this (unglamorous) aspect of triathlon, but transitions are important in long course, too. The Men’s 30-34 age group at the World Champs was decided by 16 seconds. Overall, this was a good race, but there’s plenty to improve upon.

Training Week 9/1-9/7

Swim: 10,100 Yards (2:17) 
Bike: 60 Miles (3:00)
Run: 32 Miles (3:46)
Total*: 70 Points (9:04)
————————————————————————

Swim: I didn’t get in nearly the swimming I had hoped for this week. The water at the Jersey shore was not only rough but filled with Jellyfish, and I stupidly decided not to bring my wetsuit. I could feel the slimy backs of the jellyfish with my hands as I swam. Disgusting. So I bagged a few days of swimming–not the end of the world–but I managed to get over 10K yards in three pool workouts during the back half of the week. I have started using a pull buoy for some sets–I find that isolating my upper body strengthens my pull and the buoy teaches me to keep my hips elevated. Not sure whether this is normal, but I can pull within a few seconds per 100 of my regular steady state swim pace.

Bike: I also decided not to bring my bike to the shore, so I missed my regular long ride. Two sweet spot-heavy sessions of 90 minutes each were all I could manage, as I was really dragging this week and hoping to have somewhat fresh legs for the half-Ironman in Delaware on Sunday.

The highlight of the week was getting a professional fit on my bike. I feel much better and more dialed in on my bike–it turns out my seat was almost 2 cm too low, which is a ton. Most importantly, I am now in a position that will both yield better power production and be more aerodynamic. I have only ridden with the new fit once outdoors, but I noticed a big difference.

Run: I kicked the week off with a 17-mile long run in Island Beach State Park in Jersey. Since I got a late start, the humidity quickly became stifling and I only had one short water stop planned. I clicked off some good miles in the middle, but only averaged 6:35 pace with a heart rate that would usually merit about 30 seconds per mile faster. The dehydration (and lack of electrolytes, probably) really affected me during the run and afterward–for a couple days following, my legs were feeling beaten down. Runs that deplete like this definitely detract from (and aren’t necessary for) half Ironman training, as I had to can a cycling workout due to the lasting fatigue. However, since I am considering a fall marathon and had the next day slotted for rest, I thought I could make it work. Lesson learned.

Total: This was a disappointing week of training. I planned to head into the Delaware Diamondman weekend having completed both a substantive week of training and feeling somewhat fresh. But I was feeling run down and dead legged, and in order to stay healthy and feel strong going into the race, which I am treating more as a dress rehearsal/key training effort for Pocono 70.3 later this month, I missed several workouts. However, sometimes it’s important to listen to your body and take the rest; part of training is knowing when you should push more and when you need to lay off.

*I have a non-standard system for quantifying my training output. (Swim Miles x 4) + (Bike Miles / 4) + Run Miles = Total Points. Listed time is time spent swimming, biking, or running, not rest between intervals, walking, etc.