Orny's Cycling Journal

It was the most of times; it was the least of times. My 2023 cycling year was very noteworthy, but in ways that were mostly peripherally related to riding my bike.

Welcome to the new hometown!

On the downside, I began the year off the bike for two months due to our move from Pittsburgh to Austin and subsequent discovery of a fatal crack in my beloved primary bike of the past ten years. Then I lost another month in September for a warranty replacement of the rear wheel on my new, successor bike. I only completed one century – my fewest since 2007 – and vomited right after finishing it. Throw in a couple frustrating flat tires, the challenge of navigating a new town, and the harsh reality of turning sixty years old. 2023 provided a litany of disappointments, and my Fitness and distance numbers reflected it.

But there were a lot of major high points, too. I got a brand new bike that I love, at a steal of a discount! I replaced my old, frail bike GPS with Garmin’s newest model, which has tons of cool new features and reliable battery life! I enjoyed meeting local cyclists and exploring my new hometown of Austin, and even got to bike on a Formula One race track! At my first Livestrong century, my old grammar school friend Scott came down from New Hampshire; it was also my first event as an official member of Team Kermit, and I got to ride with several old and new Pan-Mass Challenge friends who had flown in from Boston!

From an athletic standpoint, 2023 wasn’t a superlative year, but a decent one. And I’m pleased by all the memorable stuff that did happen.

My Original 2023 Goals

At this time last year, my bike and all my cycling gear was locked away in a moving van in an unknown location somewhere between Pittsburgh and Austin, while Inna and I spent our last couple days in Pennsylvania at her mother’s apartment.

Therefore I had no idea what cycling in Austin would be like, or even what our lives would look like when we got there. So it made no sense setting any specific goals for 2023. The new year was going to be imperfect, but that meant that whatever I did achieve would be gravy.

However, I did list four general themes that I thought would be foremost. They were:

Moving and Orienting in Austin

I knew this year’s biggest change would be finding my niche in a new city, and I did okay, as outlined in my Austin On-Ramp blogpost. However, I still need to put more energy into this, in every category of knowledge. I explored a few group rides, but there are several more that I haven’t. I’m familiar with a few bike shops, but still haven’t found “the one”. I’ve done a couple big event rides, but nowhere near as many as usual. Similar to my move to Pittsburgh in 2015, I’ve leveraged Strava’s Flyby feature and other riders to find some good routes for solo riding, but my options are still extremely limited. So orienting myself and finding my crew is still a work-in-progress.

All smiles on a scorching Friday Truancy group ride

Showing off the new 2023 Æthos

Celebrating another XP-filled Tour of Watopia on Zwift

Another looming concern with the move was coping with the Texas heat, and the summer of 2023 delivered, with no less than 78 days above 37°C (100°F). I continued to ride through it, but limited myself to short rides first thing in the morning… Except for the Friday Truancy group ride, which – despite being the most congenial group ride I found – was often a challenging mid-afternoon scorcher!

I knew I couldn’t commit to riding 10,000 kilometers this year, but thought I might be good for 8,000 KM – the same as last year – which I surpassed. In actuality, I rode at an 11,000 KM per year pace for nine months of the year, but couldn’t ride at all for the other three.

Amusingly, in last year’s writeup I mused that “I might go and buy myself a new steed”. That happened unexpectedly at the start of the year, right after the move, when a local shop discovered a crack in my old bike’s frame. More about that below, where I talk about the year’s purchases.

18th Pan-Mass Challenge and $125,000

I kinda knew that I wouldn’t be able to do a remote PMC ride this year. I had no idea what I could use for a route, what the August heat would be like, whether I’d have the time to do the required fundraising, or if I’d be in physical shape for 300 KM over two days. So I bagged it, and rode a lesser substitute: joining the PMC’s visiting Team Kermit to ride Austin’s Livestrong Challenge in September. Goal deferred; I’ll reconsider this in 2024.

Zwift Level 60

I also didn’t know how much I’d use the smart trainer in Austin, but I did rack up 3,400 indoor KM, which was was more than 2022. Although it can be prohibitively hot or cold to ride in our uninsulated and unheated garage, Zwift incentivized me by creating new roads and moving the Tour of Watopia from March to October. And in December I completed my fifth year on their platform.

I advanced from Level 53 to Level 58 on my slow and painful trudge toward Zwift’s pinnacle: Level 60. Then, with a month left to the year and 85% of the way through Level 58, Zwift moved the goalposts. On one hand, they made it easier to reach Level 60 by reducing the amount of XP needed to level up by about 75 percent. But at the same time, they made it harder to reach the top XP level by tacking on forty new levels, from 61 to 100!

The easier leveling let me zip through Level 59 and reach Level 60 in a matter of days, even finishing the year on Level 62. Although I achieved my goal of reaching Level 60, it’s just not as satisfying because Zwift made the last couple steps much easier to achieve.

Health and Turning 60

On the other hand, no one made the “Turning 60 years old” achievement any easier. I definitely checked that one off, and my flagging on-bike performance showed it, as I discussed in this blogpo.

Fortunately, my time in the saddle wasn’t limited by my health. A heart monitor investigating my cardiac palpitations produced a mostly clear result, with the interesting side-note of registering a sleeping low heart rate as low as 37 BPM! Otherwise there were the usual inconveniences: threw my back out, saddle sores, saddle abrasion, and the joys of colonoscopy prep.

The biggest health question I faced was how to manage heat and hydration in order to avoid problems like I experienced on September’s Livestrong century ride. Before moving to Texas, I could easily do a century without paying much attention to that equation, but now it’s something I really need to solve.

Charts

This year I made my Fitness charts a little wider, and added red vertical lines denoting significant dates. These make it a little easier to see major changes and some context for why they happened.

Let’s begin by comparing 2023 to previous years.

There’s really three things to note here. First, due to the move, I started 2023 at my lowest level of Fitness (as measured by CTL) since January 2017. Second, 2023 continued a clear trend of decreasing Fitness highs from my recent peak in 2021. As any stock analyst will tell you, a sequence of lower highs and lower lows makes for an unhappy trendline.

And finally, my level of Fitness in 2023 was quite similar to 2018, which was my last year without an indoor trainer; a year that was hampered by tons of travel, record-setting rain, plus malaise and fatigue following the intensely challenging Dirty Dozen ride the preceding fall.

That comparison to 2018 is extremely apt. If you count by Fitness or long rides or number of hours on the bike, 2023 was my worst year since 2018.

So let’s take a closer look at how 2023 unfolded in detail:

The year breaks down into five distinct periods: down, up, flat, down, and up; all of it swerving above and below the grey line that represents my average Fitness level throughout the year.

I didn’t ride at all in January, while we were still unpacking from our move. In February, I brought my beloved, ten year old bike to the shop for a major overhaul, only to learn that there was a crack in the frame. I put a few miles on my old folding bike while I waited for Specialized to decide whether I was eligible for their Assisted Replacement Policy, and then procure and assemble my new steed. After more than two months off the bike, my Fitness was at a six-year low, way behind where I’d normally be.

Then the “up” phase. When I finally received my new Specialized Æthos, I rode every day for two months straight, as shown by my steadily increasing Fitness in March and April. When my consecutive rides streak ended on May 1th, I was well ahead of my usual training, and at my peak Fitness for the whole year.

I rode regularly during the summer months from May into September, but coped with the Texas summer by only doing short rides, early in the morning, and focusing on the cheeky goal of being the rider who did the most ascents (within 90 days) of the notorious Ladera Norte climb. With no major events and low riding volume, my Fitness plateaued just below my seasonal average. Summer ended with a secondary Fitness peak in September following the Livestrong Challenge, my only imperial century of the year.

But my planned autumnal riding came to a screeching halt when I discovered that during the Livestrong ride, a rock strike had broken my carbon fiber rear wheel rim. I spent the next month off the bike completely, my Fitness plummeting again while I waited for Specialized to get me a warranty replacement.

Once that was fixed, I was back where I’d been in March: spending most of the fourth quarter recovering the Fitness I’d lost during my hiatus. But similar June’s recovery, I ended the year at a tertiary Fitness peak, well ahead of my wintertime average, and that will carry over into the nascent 2024 season.

In the end, it was a year dominated by stops and starts, but I still accrued a respectable 8,250 KM of riding.

The Centuries

I rode with Team Kermit at the Livestrong Challenge

Ornoth limping across the finish line

Pæthos at autumnal Lake Austin

But it was a terrible year in terms of long rides. Between bike repair woes, lack of fitness, unfamiliarity with the area, and prohibitive Texas heat, I only attempted one imperial century in 2023. That’s the fewest I’ve done in sixteen years, since 2007.

In fact, I only did seven rides over 100 KM (62 miles): four Zwift fondos on the indoor trainer, a ride down to the Veloway and back, the Fire Ant metric, and my one century, which was:

9/10: Livestrong Challenge

While I only did one – and suffered tremendously, vomiting shortly after finishing – at least it was noteworthy. It was:

• My first and only century of 2023
• My first imperial century in 11 months
• My first century in Texas
• My first century on my new bike: Pæthos
• My first century with my new Garmin Edge 840 Solar bike GPS
• My first event as an official member of Team Kermit
• My first Livestrong ride

Noteworthy Purchases

In contrast, 2023 was an incredibly productive year for the “procurement department”. With so many new toys, I’ll try to keep it brief…

Topping the list is my new bike: Pæthos, a Specialized Æthos that Specialized gave me an unexpectedly generous discount on. It’s been a very worthy addition, carrying on the performance endurance lineage that my previously-favored Roubaix model abandoned when it went all comfort/gravel/gimmicky. I’m slowly transitioning my kit to match its understated “Chameleon Oil Tint / Flake Silver” (aka black & white) design. My only complaint was the short-lived carbon wheels, which Spesh replaced after the rear wheel broke on its first century ride. Otherwise it’s been a complete delight. In-depth review here.

With a new bike came a handful of new accessories. Hearing rumors of fragility, I picked up a spare seatpost clamp and derailleur hanger in case of breakage. Frustration with flat tires led me to pick up a bunch of spare inner tubes, a CO2 dispenser, and a new Lezyne mini-pump. The latter frees up the bottle cage mount that my old frame pump occupied, so I have finally added a second bottle cage, which will be handy for long rides in the Texas heat. Also a handful of plastic disc brake spacers.

There’s been lots of regular gear replacement as well, including a new Garmin HRM-Dual heart rate monitor, and two new pairs of Craft bibshorts. The new bike needed to be supplied with 28mm Conti GP5000 tires, and a new set of name tag stickers (this time in white, to match Specialized’s own logo decals).

After the bike, another huge development was upgrading my bike GPS head unit from my decrepit old Garmin Edge 820 to the long-awaited new Edge 840 Solar. It too has been an absolute delight, so it also warranted its own separate in-depth review. Since that writeup, Garmin has added the ability for the head unit to display images and photos in incoming text messages.

In addition to new daily-wear bibshorts, I gained a couple other bits of new kit. A jersey from the Buddhist Bike Pilgrimage: a ride I completed back in 2012. And a 2023 Livestrong Challenge jersey, which I earned for surpassing $500 in fundraising. And my very own 2023 Team Kermit jersey and bibshorts. The team uniform even included my very own Kermit the Frog stuffed doll for mounting on my helmet: a traditional (but decidedly non-aerodynamic) part of the team kit.

My most recent purchase was an Ekrin Bantam cordless massage gun, which has been delightful to use, but its effectiveness and safety are still under evaluation.

And finally, the most notable addition to my indoor pain cave was Zwift’s Play controllers. These mount to your handlebars and offer lots of shortcut buttons for in-game actions. But the most useful function they provide is the ability to steer, allowing you to position your avatar in or out of the draft or take an optimal line through corners.

Big sky fulla giant Ornoths at the Fire Ant Tour

Bike night at the Circuit of the Americas

Red Bud Isle (more green than red, akshually)

Additional Highlights

Naturally, moving to a new city produced a lot of new experiences. I rode a challenging Fire Ant 100k up in Gatesville. I got to ride on Austin’s dedicated cycling circuit, the Veloway. I spent two evenings “zooming” around the Circuit of the Americas: Austin’s Formula One grand prix track. I joined more than a dozen Friday Truancy group rides. And it was great hosting old and new New England friends on Team Kermit rides in the lead-up to the Livestrong Challenge.

Flats – and a non-functioning frame pump – were a problem this year. I had to call a Lyft rideshare to get home after a quadruple snakebite on Blue Bluff, and also walked to The Peddler for repairs after taking a screw on 51st in Mueller. Hence all the new flat-repair equipment mentioned above.

I’m tempted to list out the two dozen Strava “Local Legend” achievements I earned by being the person who rode a segment more than anyone else in a 90-day period, but that’d be a waste. I’ll just mention the two biggies: becoming LCL on Austin’s infamous Ladera Norte climb, and the Friday Truancy ride’s spiker up the Arpdale to Cedarview Kicker.

In terms of Zwift highlights, the indoor training simulator released several enhancements. You can now capture short videos of your ride and share them directly to Strava. They added their new Climbing Portal, the Scotland world, the southern coastal road in Watopia, and introduced the Zwift Play controllers and the Repack Rush steering challenge. As mentioned above, they moved the popular double-XP Tour of Watopia to the fall, and introduced some major (and frankly asinine) changes to the XP system when they unveiled new levels 61 to 100. And there are rumors of more changes in the works.

Blogposts

• 2/10: Clowning Around In Austin (riding the folding bike post-move)
• 3/7: The Pæthos Æxpert (a brand new bike!)
• 5/4: Jalapeno Ketchup (spring catch-up post)
• 5/10: VC Sniper! (name decal vendor recc)
• 6/15: Fire Ant Cookout (first Texas 100k event)
• 7/5: Austin On-Ramp (first impressions of riding in Austin)
• 8/6: Legend on the Ladera (Ladera Norte Local Legend)
• 9/19: The Edge of the Sun (new Garmin Edge 840 Solar GPS review)
• 9/21: It's Not Easy Being Green in the Face (Livestrong Challenge & century ride report)
• 11/4: The Aging Cyclist (cycling as a sixty year old)
• 12/3: ‘Tis the Season (autumnal catch-up post)
• 12/31: 2023: Austin City Limits (my year in review: you’re reading it!)

Goals for 2024

Ornoth’s 2023 cycling calendar/log

My 2023 Strava Year in Sport summary

I knew that 2023 was going to be a chaotic year. Looking forward to 2024, I don’t know if I can plan on it being much better. I’m still learning about Austin and what is gonna work for me here, so most of my goals remain pretty vague.

More 100k and Century Rides

For various reasons, I haven’t done as many event rides as I hoped, so next year I’d like to do more. There’ll probably be another Livestrong ride, and I’m hoping to do the two-day Texas MS Ride in April, and possibly a repeat of the Fire Ant metric. Instead of limiting myself primarily to 100-mile events, as I’ve done previously, I’m thinking of signing up for more 100-kilometer rides, which seem more prevalent and feasible for a sixty year old riding in Texas heat.

Find My Group Ride Niche

I just don’t fit anywhere in Austin’s group ride scene, which is mostly divided between flat-out hammerfests for active racers, and short, plodding social rides for non-athletes. I’m hoping someday I’ll find a ride that splits the difference, much like Pittsburgh’s Team Decaf ride or Boston’s old Quad Cycles rides. There’s got to be more mid-tier endurance and charity riders like me in this area; but where are they?

A Big Pan-Mass Challenge

2024 is kind of a big year for both me and the PMC. It will be the organization’s 45th ride, and they will celebrate surpassing the immense and impressive $1 billion fundraising threshold. For myself, it would be my 18th ride, and bring my own fundraising to over $125,000. And it’d be my first PMC as a sixty year old.

I’m committed to ride, but still stumped by what it will look like. A 300 KM solo ride in August heat doesn’t sound very feasible. I’d consider returning to Boston for the in-person ride, but that’s impossibly expensive, between airfare, hotels, car rental, and transporting my bike. Plus the $6,000+ fundraising minimum is far beyond my current ability, and I’ll have to personally cover any shortfall. I could extend my Livestrong Challenge weekend riding while fundraising for the PMC instead of the Livestrong Foundation… But that’d be in October, rather than on the traditional PMC weekend in August.

There’s just no good option, but the decision needs to be made now, as the traditional PMC route will sell out before the end of January. I wish there was a better choice.

Conclusion

So 2023 was a mixed bag. I turned sixty, said goodbye to my beloved primary bike, was off the bike for three months, skipped the PMC, and only attempted one imperial century. But I also had fun exploring my new town, rode with Team Kermit, got a snazzy new bike, new GPS, a cordless massager, and lots more.

After less than a year, my settling into the Austin scene is far from complete, so that process will be ongoing. I’m looking forward to finding more people, places, and events to enjoy in 2024. Stay tuned to hear how it goes!

In addition to the HUI-VUI, I’ve discovered another thing that happens every six years: I purchase a new GPS bike computer. In this case, we’re talking the Garmin Edge 840 Solar, which I picked up last month after it came out back in April. A new GPS head unit is a really big deal for someone who spends as much time in the saddle as I do.

Before diving into the new unit, let’s look at how far we’ve come. I first used a GPS to log bike rides waay back in 2000, using Garmin’s original yellow eTrex handheld, but the tech back then was so primitive that it didn’t have maps or routes or points of interest; just a blank monochrome 64 x 128 pixel LCD with a breadcrumb trail of where you had gone, and even that initially suffered from “Selective Availability”: an intentional inaccuracy imposed by the government on civilian GPS signals. Six years later I grabbed an eTrex Vista (my review), which had finally added color and some very rudimentary maps. In 2011 Garmin released the cycling-specific Edge 800, then 2017’s Edge 820 (my review), and this year’s Edge 840.

Along the way, I’ve watched these units evolve into incredibly useful and sophisticated navigational and analytical tools. Garmin updates their cycling products about every three years, so I’ve usually skipped a generation (e.g., the Edge 810 and Edge 830). So when I buy a new unit, there are some substantial improvements and compelling new features to check out.

And by that point, my old unit is usually pretty worn out. That was certainly true of my loyal old Edge 820. To begin with, its touch screen – a novelty at the time – was very sluggish, and the processor took forever to calculate routes or pan and zoom the map display. And the Micro USB connector was outdated technology from the start. After a few years the screen faded significantly, leaving a prominent grid of its LCD guts showing through its faint display. And its battery life – originally billed as lasting 15 hours – had shrunk to about 90 minutes. These were the shortcomings that I expected the new Edge 840 to fix.

With that, let’s look at the new beast. As always, I’ll divide this review into four sections: things I’m neutral about; features I don’t know much about because I didn’t test them; features I’m excited about; and the things that already disappoint me. With an executive summary at the end.

The Neutrals

My main display: speed, distance, with power and heart rate charts

One of the most noticeable changes is a revamped UI. It works fine. Its organization of functions isn’t 100% intuitive. And it’s still based on “activity profiles” rather than gear, which has always seemed a bit clunky to me.

The unit also supports phone-based configuration. I really don’t see a ton of value in that over configuring the unit on a computer or the device itself.

Potentially useful features include alerts for upcoming sharp turns and high-speed roads. But the high-speed road alerts arrive way too late to be actionable (e.g. navigating to avoid them). And the last thing you want when speeding around a sharp turn is having to read and dismiss an alert popping up on your head unit. They’re nice ideas, but not practical (at least not with the current implementation).

An unexpected surprise was that when following a route, the GPS can now have your phone verbally announce navigational cues as you approach them. “In fifty meters turn right on Mesa Drive.” Another cool idea, but they’re just not intelligible when your phone is stuffed into a jersey pocket on your back.

The unit can also walk you through a heart rate variability stress test. This isn’t for general health purposes, but for telling you how well or poorly you have recovered from your previous rides. That’s not something I need to wait around for three minutes for a device to tell me.

The Cycling Ability feature can tell you what your general cycling strengths and weaknesses are, as a very gross training aid. Garmin doesn’t add much value by telling me that I’m an endurance specialist.

Same with their measurement of heat acclimation. A simple percentage is way too simplistic to be of any actionable value.

Another hamstrung feature is showing the battery status for all your sensors (e.g. heart rate monitor, electronic shifters, power meter), where you really need more discrete battery levels than “okay” and “dead”.

There’s also a ton of features that I don’t really care much about, but you might. But to be honest I really don’t have any opinion about things like incident detection, structured training plans, mountain biking metrics, hydration alerts, an integrated bike alarm, lost device finder, etc.

The Unknowns

It might surprise you that I didn’t bother testing the unit’s integration with my indoor trainer. But the only useful function that provides would be the ability to simulate the gradients of riding a known real-world course, which isn’t as engaging as riding in the richer worlds on Zwift.

The Power Guide feature gives you a plan for specific power numbers to match when following a particular route. Just not something I’m likely to want.

Same story with the Event Training Plan feature. I hate structured training and already know how to build and taper for a major event. Not something I need, and not something I’d look to a head unit to provide.

There’s also the new and very promising Group Ride feature, which lets groups of riders share their route, in-ride messages, and live map with everyone’s location. This sounds like a really awesome feature if a critical number of rides and riders adopt it, although it’s limited to Garmin’s most recent units. It’s only in my “Unknowns” section because I haven’t had any opportunity to test it out.

The Positives

My customized boot screen

Solar power gain, showing 71 minutes gained over a 9-hour ride

ClimbPro displaying map, elevation profile, current grade and power

Real-Time Stamina, estimating 21% or 17km remaining before bonking

Let’s start with the basics: critical things my Edge 820 did that the 840 still does. I can still download my activity FIT data files to my laptop, as mentioned above. It still communicates with my Di2 electronic shifting and displays what gear combination I’m in. I can still capture screen shots, as you can see at right. I can still set the text that appears on the startup screen. And you can still charge it from a portable USB battery while using it. Good!

Then there’s things that aren’t new, but are features the Edge 840 has improved upon. Starting with the most important improvement: battery duration is now listed at 32 to 60 hours! The touch screen is so much more responsive that it’s actually usable now! Panning and zooming maps is reasonably quick! Calculating and re-calculating routes takes a second or two instead of five to ten minutes! Adding the GNSS GPS system improves GPS accuracy in cities and other challenging areas! And while my old unit would show alerts when calls or text messages came in, the 840 also shows email and all other phone notifications! Very nice!

The passive solar receiver adds around 8 to 10 minutes of extra power per hour in Texas sun, which might not be a huge deal for folks in cloudier locales, and there’s a data page showing the unit’s solar efficiency. Even I debated buying the non-solar model when I learned that the special glass makes the solar screen a little less bright, but it seems fine, and way better than my old, faded Edge 820.

On the topic of charging, we’ve finally made the transition from a MicroUSB to a USB-C charging & data port!

One of the highlights of the new interface is a home screen with “Glances”, little UI widgets that summarize important information and link to the most frequently-used functions. For example, there’s a Weather Glance that shows current conditions and clicks through to a dedicated weather page. And the Navigation Glance will show and give you one-touch access to the route you most recently downloaded onto the unit.

But by far the most massive UI enhancement is the widespread addition of graphical data fields! Heart rate and power are no longer a single number, but also time-series charts that are color-coded for intensity. Solar power, route elevation and gradient, and several other data fields can be shown as color graphs that encapsulate a ton of information in a small screen factor. Very cool!

One special application of charts is the new Climb Pro page. When you begin a climb, a new page pops up to show your current power, how much longer the hill is, its current slope, and a chart that shows where you are on the climb, and color-coded undulations of how steep it gets over its entire duration. It’s a very handy little tool for managing your effort, especially on long or steep ascents.

And if you need to manage your effort over an entire long ride, the Real-Time Stamina page is a great new feature. It uses your history to estimate what percentage of your total endurance you’ve used up – and therefore how much you still have left in the tank – and what that translates to in terms of time or distance until you hit the wall and your performance plummets. This sounds like a gimmicky pseudo-feature, but on my recent 100-mile Livestrong ride, it accurately foretold that I’d run out of juice about 30 km before the finish.

I could have included this in my “enhanced features” above, but it deserves its own paragraph: enhanced text message functionality. On my old Edge 820, when replying to someone’s text message, I could only pick from a pre-set list of 8-10 basic canned responses. Now there’s about three times as many canned responses. And you can customize them in their mobile app. And you can add emoji. And the Holy Grail: you can even compose your own responses on the fly, using the on-device keyboard! Finally Garmin no longer artificially limits me to replying with “Yes”, “No”, or “Almost there”!

The Negatives

The most obvious and glaring negative is that the meager screen resolution (246 x 322 pixels) hasn’t increased. It’s not a huge issue, but a higher resolution display would improve my perception of the unit a great deal.

Garmin advertises a cool feature that will tell you your “fitness age” based on your measured physiology. Why is that a negative? Because you don’t get that piece of data unless you buy both a connected scale and wear a 24-hour fitness watch that’s paired to their central database. Garmin advertising this feature as available on their bike computer is completely misleading.

While I haven’t sussed out exactly which features require it, the bike computer will nag the user to not only install but keep Garmin’s smartphone app open and running in order to take advantage of certain online features (IIRC things like current weather, voice navigation, text messages, and phone notifications).

The only true malfunction I’ve experienced is that a distance alert I set failed to trigger on my recent 100-mile Livestrong ride. Unfortunately, I’ve only done one century ride, so this isn’t something I can test very often!

Finally, the unit often hangs whenever I disconnect it from a cable connection to my laptop. It’s recoverable, and most people probably don’t do this very often, but I download my activity data file after every ride, so it’s a big annoyance for me. Aside from the fact that the unit shouldn’t hang under normal operating conditions to begin with!

The Bottom Line

Six years ago, I was disappointed after buying Garmin’s Edge 820. After defining and owning the GPS bike computer market, they released an underwhelming product that was unimaginative, behind the times, and deeply flawed. As a result, more agile competitors like Wahoo and Hammerhead eagerly and justifiably took major chunks out of Garmin’s once-dominant market share.

Garmin seems to have learned their lesson. The Edge 840 has improved on several old features and introduced a raft of new functions. I’m genuinely excited by the improved UI and graphical data fields, the passive solar charging, ClimbPro, Real-Time Stamina, the enhanced SMS capabilities, and the potential of the Group Ride features. Assuming they figure out the missing distance alert, my only knock on it is the meager screen resolution; but that’s still markedly brighter and more responsive than my old, fading 820’s terrible display.

Am I happy with it? I’m delighted! While it’s not perfect, the Edge 840 is a tremendous improvement over my old 820, with far fewer built-in flaws.

I wouldn’t normally post a ride report for a mere 100k (62-mile) ride, but there are reasons why I’d like to share my experience of my first Fire Ant Tour.

Big sky fulla giant Ornoths!

Riding straight past the first rest stop

Rolling into the second rest stop

... and limping over the finish line

To begin with, I haven’t found many (imperial) century-length rides around Austin, which means very little to talk about. I’m hoping to get one or two under my belt soon, but this is summer in Texas: not the smartest time to undertake my first century in a while. So I might not have any century-length ride reports to post until fall.

On top of that, my last outdoor ride of more than 80 KM (half a century) was back in October, so it’s already been eight months since I posted my last ride report. So the Fire Ant Tour was a test of my physical readiness for a long ride after such a long hiatus.

In the same spirit of testing things, this was a ride full of important firsts. It was a chance to try my first major event on the new bike: Pæthos. It was my first major event in Texas after our move down here in January. It was also my first ride out in the rural Texas countryside, well outside of the proverbial “Austin city limits”. And it was my first long ride facing the extreme heat of summer in Texas, coming just eleven days before the summer solstice.

I didn’t maximize my physical preparation. I was pretty casual about my fitness level in the weeks leading up to the event, and I didn’t bother tapering my riding just beforehand. I wasn’t feeling particularly strong, but I figured I was ready enough for a little 100k.

In short: this ride was going to be a big test of several factors, and I was very interested in learning from how it went.

So with Inna away visiting family back in Pittsburgh, I hopped in the car at 5:30am – after waking up at 2:30am due to a thunderstorm – and drove 90 minutes north toward Waco and rural Gatesville TX. Although there was still lightning when I left Austin, the sky had cleared by the time I checked in and got the bike ready for the 8am start. Over 325 riders set off in very pleasant 24° morning sunshine.

We rolled along, mostly north and east, often topping 40-50 km/h and averaging over 30 km/h, knocking off the first two of the route’s four small 50-meter hills. There were almost no cars on the roads, and the landscape surprisingly reminded me of the very open, flat-to-rolling farmland in Ohio. At this point, it was really delightful.

It was when we turned back west to complete our first, clockwise 20 KM loop that we learned how much of a tailwind we’d enjoyed on the outbound leg: about 18 km/h gusting to 26. Despite putting much more effort into overcoming the headwind, I was going slower, and that variation in power and speed would continue all day, depending on which direction we were going.

After a tedious westward slog, the route continued with a larger 55 KM loop, counter-clockwise, with the wind cutting my average speed to a painful 18 km/h on the westward portion. That loop ended with a 3 KM section of rough gravel that stung my hands, followed by the last of the climbs on the route.

After that challenging segment, I took some extra time at the last rest stop to douse myself with water and rest my legs. It was now the heat of the day, and the former cooling wind had become hot. I wish I could quantify that, but after a forecast high of 36°, on the ground readings ranged from 31° on one feed, to 35° from the National Weather Service’s intermittent rural monitor, to 40° recorded by my GPS. After having increased my sport drink intake, my stomach was bloated and queasy, my feet were hurting, and my power numbers were flagging.

The last segment was short and partially downhill, and I rolled across the finish shortly after 1pm, having taken 5 hours to cover 107 KM, with just 750 meters of climbing. I certainly didn’t finish strong, but picked up my finisher’s medal, doused myself with water, and packed up. I gratefully jumped in the air conditioned car and drove straight home, my stomach wanting no part of post-ride hot dogs, drinks, or ice cream.

Despite the discouraging finish, I really enjoyed the ride. The roads were quiet and reasonably well surfaced – except for that gravel section – and car traffic was minimal. The Texas landscape wasn’t dramatically different from what I’m used to, and less sere than I expected. The tailwind was awesome, the headwind was annoying, and overall the breeze did clear some of the heat off the road surfaces.

That heat wasn’t extreme by Texas standards, but I did gain a healthy respect for it. I’ll have to be more assertive about hydrating early, and accept the limits of my endurance when it gets really hot. Whether I want to push myself for summer century+ rides is still a bit of an open question, knowing that it’ll entail an extra, dangerous level of suffering.

The organizers did a good job, with frequent rest stops amply stocked with ice, and I’m always delighted to receive a finisher’s medal.

As for Pæthos, it did marvelously. I had no issues with mechanicals or fit or unwelcome squeaks and creaks. My only complaint was some pain in my hands, which was aggravated by the short gravel section. I’ll be keeping an eye on that in the future.

So for a first event, the Fire Ant Tour was fun and provided the desired learning experience. With a hot five-hour ride under my belt, I have a better idea what to expect if I choose to undertake my first century in this summer’s extreme Texas heat.

In my previous post, I outlined my plan of using Zwift to mimic real-world rides I had planned but couldn’t ride due to the Coronavirus lockdown. My goal has been to ride the same distance and elevation gain as the actual route.

When my first event came in late April, I somehow had to identify a route on Zwift that would provide me with the same 7,687 feet of climbing over 123.19 miles as the IRL ride. I cobbled together a mash-up of three different routes, but it was a bit off: 8,402 feet of climbing over 125.56 miles! My mileage was good, but I’d done 10 percent more climbing than I needed to!

I knew there was a better way. Someone should write a program that would take stats for all Zwift’s routes and compare that to my target route, then tell me the Zwift route that would allow me to finish with just the right combination of distance and climbing.

Obv, that someone had to be me.

So I went to work and produced the Zenturizer. You give it the distance and climbing in the ride you want to simulate (metric or imperial), and it will list which routes on Zwift are the best match, and how many laps you need to do. Just like this:

Last weekend, I wanted to test the Zenturizer and get another “Zentury” under my belt. While I didn’t have any real-world events in May, I decided to replicate a ride I used to do over Memorial Day weekend back when I lived in Boston: the Tour d’Essex County, a 102-mile century in Boston’s north shore and Merrimack valley that included 3,000 feet of climbing.

Feeding that data into the Zenturizer produced the following options, in order of how closely they match my criteria:

1. Ride about 15.9 laps of Flat Route (Watopia) 94% match
2. Ride about 44.7 laps of Volcano Circuit (Watopia) 88% match
3. Ride about 44.2 laps of Volcano Circuit CCW (Watopia) 88% match
4. Ride about 34.8 laps of Classique (London) 83% match
5. Ride about 16.4 laps of Greater London Flat (London) 83% match
6. Ride about 6.6 laps of Greatest London Flat (London) 75% match

Although I wasn’t very excited at doing the bog-standard Watopia Flat route, it was the best match, and I wasn't about to ride any course 35-45 times, so Watopia Flat it was!

According to the Zenturizer’s calculations, it should have taken exactly 15 laps of Watopia Flat to accumulate 3,000 feet of climbing, and 15.9 laps to go 102 miles; on my Zwift ride, both those estimates were right on the money!

In an ideal world, I would complete both distance and climbing goals at the same time. But because the closest Zwift course wasn’t a perfect match, I finished my climbing goal a full lap before my mileage goal. In riding that extra lap to complete my mileage goal, I wound up doing an extra 213 feet (or 7 percent) of climbing. However, that actually matches the Zenturizer’s estimate that the Zwift route would only be a 94 percent match for the IRL route.

All told, I think the Zenturizer did a fantastic job finding the right Zwift route to simulate the real-world ride I chose. Feel free to try it out yourself!

Okay, that’s enough about the Zenturizer; how did the ride go?

It was hot. I was hoping to ride Friday or Saturday or Sunday, but I spent those days suffering with a migraine. So Monday it was, and temps inside my pain cave sat at 90º throughout. Being my first hot indoor century, I suffered a lot, but also earned a number of lessons:

• Have tons of ice on hand. Two trays of cubes isn’t enough!
• Start early in the day. I got a late start, and it was already hot when I saddled up.
• In addition to a towel over the handlebars, have a second towel nearby to sop up excess sweat. I normally don’t sweat, but given the conditions...
• Nothing feels better than a cold, wet facecloth. Lifesaver!
• Watch out for cardiac drift. As the event wore on, I had to back off markedly because of elevated heart stress. Take it easy; there’s no point in trying to hammer for five hours straight in the heat.

But I knocked it out, thanks to the Zenturizer. And that’s the story of my 5th Zentury of the year!

I wasn’t planning on repeating last year’s Akron Bike Club “Absolutely Beautiful Country” century. It was a really nice ride, but it’s a two-hour drive from Pittsburgh, which makes for a lot of driving on top of a 100-mile bike ride.

Selfies on the River Styx

Level crossing delay

Sunburned hands

However, having spent much of the first half of this year away from home, I was really under-trained and in desperate need of fitness before all the big summer rides. And with Inna still out of town, there was no one to inconvenience.

But the biggest reason to go was the weather. A week-long heat wave broke on Friday, leaving us with a delightfully temperate weekend. Sunny and less humid, with little wind, it was perfect weather for a long ride, so…

I got up at 3:45am Sunday “morning” and was on the road by 4:30, headed back to the city that gave us the Kent State massacre, Devo, and Chrissie Hynde.

During the drive, I noticed that almost all of Ohio’s roads are straight north-south or straight east-west, with very little variance. It made me wonder why they didn’t just name their cities by map coordinates. So if Cincinnati was called “A12” and Columbus was called “F5”, then you’d know that to get from one to the other you’d have to drive 5 units east and 7 units north. Seems like it would be a lot more efficient in a place like Ohio, since—with no diagonals—that’s just the way the roads work anyways.

Kitting up in the Copley High School parking lot, I discovered a packing mistake: the pair of cycling glove’s I’d brought were both right hands. The guy parked next to me offered to loan me a pair, but I demurred. Going bare-handed wouldn’t be any major discomfort, I thought. No big deal… If anything, it might hide or even out some of my characteristic cyclist’s tan lines.

At ten-to-seven I was in the saddle, dropping lots of riders in a desire to work up some body heat to ward off the morning coolth. Eighteen miles later, I stopped to get a selfie in front of the sign for the village of River Styx. It’s probably not an auspicious thing, crossing the River Styx with 82 miles still to ride…

Speaking of stopping, about 35 miles in I caught up with a couple riders who were stopped at a level crossing while a big freight train rolled by. Fortunately, the end (of the train) was near, and I was only delayed about three minutes.

About one-third done, I was already experiencing some physical difficulties. I was obviously undertrained and not ready for the distance, even on a flattish course like this, and by the end of the day my legs were cramping up. My knees were complaining loudly, thanks to inflammation picked up while on my recent meditation retreat. I was also having difficulty swallowing due to an undiagnosed throat irritation. The day eventually heated up, and on the last, 15-mile segment, I was so blown that I had to stop for a brief roadside rest before finishing.

This was countered by the excellent work done by the organizers at the rest stops. Twelve miles in, riders were offered donuts. At the halfway point, small sandwiches piled high with cold cuts and cheese. At Mile 70, the Dalton Dari-ette offered free ice cream! And all the stops had ice, which for me is always key.

I finally rolled back into the high school at 2:15pm. I had enjoyed the Ohio countryside and the beautiful day, but I was glad the suffering was finally over, and happily looking forward to getting into an air conditioned car for the drive back to Pittsburgh.

Pulling the bike out of the car trunk at home, I noticed that the plastic mounting tab for my Di2 electronic shifting junction box had broken. That’s an annoyance, since I’d just purchased and installed a new mounting bracket for it.

But more troublesome—though less costly—were the implications of spending seven hours in the July sun without gloves. The rest of my body has long-since adapted to sun exposure, such that I didn’t suffer any ill effects of going completely without sunblock; however, my hands have always been shielded by gloves, and the sensitive skin on the back of them isn’t seasoned to strong sunlight and got thoroughly sunburned. Lesson learned!

Nonetheless, I’m glad I went, and (mostly) had a good time. There aren’t many century rides to choose from here in Pittsburgh, and I’m happy to participate in and support those few that remain.

But whether I’m ready and willing to undertake another century happening weekend… We’ll see how well I recover!

Last weekend was my second century of the year and first Pittsburgh charity ride: the Bike MS Escape to the Lake, which goes from Moraine State Park an hour north of Pittsburgh to the shore of Lake Erie. Rather than do the whole route and deal with an overnight stay, I preferred to do the first day century route and quit there.

The forecast was unfavorable during the week leading up to the event, so I waited to register. But the calls for extreme humidity and thunderstorms abated at the last minute, convincing me to sign up at the starting line and personally fulfill my fundraising requirement.

Years as a PMC rider served me well in quickly registering, getting my bike ready, dropping my bag at the luggage truck, and lining up near the front of the staging area, directly behind the VIP riders. I chatted briefly with my randonneuse friend Stef before we were punctually sent off. I wore the green and black dazzle jersey that I’d worn with the Buildium team for last year’s Cape Cod Getaway.

The first third of the ride was pleasant and gentle, with temperatures in the 60s and only a couple notable hills. I skipped the first two rest stops (miles 12 & 21), and finally refreshed my bidon at mile 33, then proceeded to the lunch stop at mile 48. Halfway done by 10am, I had averaged 17 mph and over 165 watts for three hours.

After lunch, the ride became more challenging. The temp had cracked 80°, and three big hills came in the 16 miles preceding the rest stop at mile 64. My speed dropped to 14 mph and my power to 140 watts, though I still had enough in the tank to pass a couple Amish buggies… one towing a canoe!

The final third of the century was a horribly brutal slogfest. Seven major hills were packed into the final 32 miles, with a very long 22 miles between the final water stop and the finish. The course turned west, straight into a painful sustained 16 mph headwind gusting to 26. Temps peaked well above 95°, with the rolling Pennsylvania farmland offering zero respite from the relentless sun. Although I was only the second rider to arrive at the last rest stop, I was completely tapped out; my speed subsequently dropped to 10 mph and my power below 100 watts.

It was incredibly difficult to finish that long final segment, and I had to pull off by the roadside four times to recuperate enough to press on. At one stop I watched Stef ride past, too overheated to chase her or even call out. I was just about ready for medical assistance, but I only had seven miles left, and once I got over the final hill, the last couple miles were a long, welcome downhill to the finish.

I finally coasted into Allegheny College in Meadville at 2:30pm. 102 miles in 7 hours 25 minutes. More noteworthy than my time was the climbing; at 5,958 feet, this ride had more ascending than New Hampshire’s Mt. Washington Century, and was only exceeded by the 200k I did two months ago. Strava would confirm this as probably the most difficult ride I’ve done in five years. The next morning my scale would report that I’d lost over three pounds, even after plenty of rehydrating.

At the finish I found lots of ice and cola, bag pickup in a blissfully air conditioned auditorium, and very welcome showers. After those things, there wasn’t a lot of time before the 4pm shuttle bus back to my car at the starting line. Volunteers loaded my bike onto a cargo truck and handed me my finisher’s medal, a detail I always wished the PMC had done.

I slowly recovered on the hour long bus ride. Although the rented school bus lacked air conditioning, we opened all the windows and I let my hair fly loose in the wind. After arriving back at Moraine State Park, I gathered my bike, dumped my bag in the car, and went for a refreshing wade in Lake Arthur.

After all the concern about thunderstorms leading up to the ride, we finally got some on-and-off showers during the hour drive home. The A/C felt absolutely wonderful!

It was a good ride, and I’m glad I did it, notching up my second century of the year, but I was also very glad not to have to saddle up and fight that headwind for the second day’s leg up to Lake Erie!

Prelude

Epic rides deserve epic ride reports, so here’s the tale of the 2012 Mt. Washington Century…

The story begins with last July’s Climb to the Clouds ride. For at least the past three years, my Pan-Mass Challenge training culminated with that century ride up Mt. Wachusett a couple weeks before the PMC. But that ride isn’t well run, and last year my buddies and I reached the breaking point (ride report). As we sat around recovering from a brutal ride, all four of us concluded that we never wanted to do that ride again.

So this year I proposed a different ride that occupies the same spot in the New England cycling calendar: the Mt. Washington Century. It took very little convincing that a different ride would be more fun than yet another disappointing Climb to the Clouds.

The bonus is that this isn’t just another ride; it is an epic 108-mile ride over three named passes in the White Mountains. The route accumulates more than a mile of vertical by traversing the well-known Kancamagus Highway, Bear Notch, Crawford Notch, and Pinkham Notch. Billed as “New England’s most challenging century”, it circumnavigates most of the Presidential Range, including Mt. Adams and, of course, Mt. Washington, which is the highest peak in the northeastern US.

Preparation

In anticipation of the most difficult route I’d ever attempted, I spent a couple weeks doing hill repeats on the biggest hills in the area. On July 3rd I did four ascents of Great Blue Hill… and, of course, four high-speed descents, which I would also need to be ready to tackle. And on July 8th I did six trips up Eastern Ave to Arlington’s water tower… again with six screaming descents down the Route 2 on-ramp. While I wasn’t sure I was ready for 108 miles of mountains—especially after my self-destruction on my attempted Harvard century two weeks earlier (ride report)—I figured I was as ready as I was ever going to be.

I also wanted the Plastic Bullet to be ready, and it needed help. After a recent cleaning, my shifting had started skipping around. It had been more than a year since my last tune-up, so on Tuesday I brought it in and had them true the wheels and replace the chain and cassette. Seemed like a wise idea, right? Let the shop make sure everything was in good order for the big ride.

On Wednesday I biked to work, and the shifting was just as bad, if not worse. It was bad enough that after work I rode directly to the shop and asked them to fix it up properly. But as soon as the tech touched it, the shifter cable snapped at the shift lever: a problem that has happened to me two or three times in the past. When it happens, your shifter locks into the hardest gear and there’s nothing you can do about it. In short, had that happened during the Mt. Washington ride, I would have been absolutely screwed. I had really lucked out.

Getting There

The day before the ride, I left work at 4pm and met my buddy Noah drove me from my place out to Jay’s in Waltham. Rather than try to fight Friday rush hour traffic, we followed the first of several insightful suggestions I offered: get Thai from the restaurant around the corner. Everyone loved that idea… even me, who’d already eaten Thai for lunch for two days in a row. Hey, I figured it was good veggies and carbs! So that was my first good call.

Hanging at Jay’s, the sandbagging began. It was clear that each of us had some level of anxiety about the ride. Paul hadn’t ridden in a while. Noah hadn’t ridden much all year. Jay was surprised to learn that the ride’s site had lied about how much climbing was involved, proclaiming 4800 feet of vertical instead of a more realistic 6000'.

We also took a moment to acknowledge that this would be our last major ride together as a group, with Jay moving to Florida next month. We’ve had a great run together, and I think everyone’s sad to see it pass. On the other hand, doing the White Mountains would be a fitting and memorable way to go out!

The 3-hour ride up was pretty uneventful, and we arrived at the hotel Jay had booked at 10:30pm. That’s when the fun began: the woman at reception couldn’t find our reservation. Jay whipped out his laptop, but all he could come up with was some followup spam that Marriott had sent him. Apparently their central booking agent had added him to their spam list, but never bothered to make our reservation! Thankfully, by the time all was said and done, the local manager gave us a two-bedroom for a ridiculously low price; another crisis averted!

Departure & the Kanc

After grabbing some stuff from the hotel breakfast, we hit the road to the start: the Tin Mountain Conservation Center just outside Conway. We were already running later than Noah or I wanted, since it promised to be a very hot day. We signed in, got all our stuff together, and finally rolled out at 7:30am. The first mile featured a screaming descent which we all knew would be a kick in the teeth on the way back.

Within a mile, we turned left onto the Kancamagus Highway, arguably the most famous road in New Hampshire. It was a bright, beautiful morning. The road was smooth and steady. The mountains towered above us, the evergreens covering the hillsides offered fragrant shade, and the granite boulder-strewn bed of the Swift River ran along the road, keeping us company as we climbed toward its source.

My buddies stopped to stretch for a while, but I was eager to keep moving, so I went on ahead alone. The Kanc climbs gradually but steadily, but I kept a comfortable pace, knowing that I’d need lots of strength in reserve for the peaks that lay ahead. Still, I kept my buddies at bay until shortly after making the left turn onto Bear Notch Road. The Kanc had ascended about 800 feet in 12 miles.

Bear Notch

On the course’s elevation profile, Bear Notch looked like the easiest of the three ascents, with more gradual, easy climbing. And that’s pretty much how it turned out. It never seemed to get steep for any sustained period of time, and I climbed alongside my buddies, who had finally caught me. It was cool that three of us were together when we passed the event photographer, who captured us.

The climbing we’d done on the Kanc (800 feet over 12 miles) had put us more than halfway to the top, so the actual climbing on Bear Notch Road really only amounted to another 600 feet over 4 miles.

Then, without really expecting it, we were over the top and coasting at 35 mph down a winding, wooded road. Thankfully, the road surface was beautiful, and we zoomed down almost without touching our brakes, admiring the mountain and valley vistas that opened up on our left.

After a long descent (over 1000 feet in 5 miles)—but still too soon—we were dumped into a little village called Bartlett, where the first rest stop sat in a public common. We all had big grins on our faces as we recounted our experiences to one another. So far it had been a wonderful day, and the temps were still in the low 70s.

Crawford Notch

We rolled out and turned left onto Route 302, a somewhat busier road. Paul and Noah caught and passed me, but Jay hung with me as we fought an unexpected northwest headwind—the only time that happened all day.

Again, the ascent was long and gradual but very manageable (550 feet over 12 miles). As we got close to Mt. Jackson, we stopped for a photo opp at the Willey House pond, close to the source of one of my favorite rivers (the Saco).

We caught a slower paceline just as the road started kicking up at the summit. Jay and I debated passing them, but that soon sorted itself out, as some of them distanced us while others went backwards. The last two miles or so was a real struggle, gaining another 550 feet, but that made it all the sweeter when Jay and I crested Crawford Notch together, yelling weightlifter Ronnie Coleman quotes at each other (“Yeah buddy!”, “Whoooo!”, “Lightweight baby!”, and the ever-popular and slightly-modified “Everybody wanna be a cyclist; nobody wanna climb these big-ass hills… I’ll do it tho!”). It felt like a victory worthy of celebration, and thus it was nice to share that moment with Jay.

The problem with Crawford was that there wasn’t any real descent afterward. The road leveled out and angled down just a hair, but not enough to really make a big difference. The road was also barren, having emerged from the woods, and the temperatures were into the mid-80s.

Fortunately, the second water stop materialized in a convenience store parking lot. Surprisingly, the organizers had run out of sports drink, and we had to go buy our own from the convenience store. That was the organizers’ one obvious shortfall: we shouldn’t have to pay for Gatorade out of our pocket on a ride we’d paid to do!

Going Round the Mountain

Jay and I left Crawford and continued north on 302. I pulled him for a few miles as we turned east by cutting across Route 115 to Route 2. Here there was a mix of rolling climbs and a few long descents, but nothing like that off Bear Notch. Jay pulled away but Paul caught up and rode with me for a while before he too moved on.

Then, shortly before we reached Gorham, I rounded a corner to find myself facing an immense wall known as Randolph Hill. In the distance, the road looked like it took off like a jetliner, soaring into the sky (in reality it climbed 200 feet in less than a mile). By this point, temps had climbed to 90 degrees, and there was little if any shade along the route. I poured the last of my Gatorade over my head and plodded up the brutally steep climb.

Fortunately, the third water stop was at the top of the hill, where I collapsed in the heat. Thankfully, the organizers had cold drinks on ice in coolers, and I shoveled ice into my water bottle for the next segment. I also had a couple sips of Coke, which certainly went down nicely.

It was at this point that my stomach started doing flip-flops. At the rest stops, I felt bloated and queasy, full of too much liquid, which I’d been pouring down my throat; but on the bike, I felt pretty good for the most part. This would continue for the rest of the day.

Mount Washington and Pinkham Notch

Jay and Paul left the rest stop shortly after Noah showed up. Noah was pretty cooked, but I rested for a few more minutes and we left the stop together. The good news is that the road continued to descend (650 feet in 4 miles) after the rest stop, and Noah and I rode together through Gorham, where we finally turned south onto Route 16 for the climb up to the base of Mt. Washington.

Route 16 was a really long, steady climb, but a bit steeper than the easy slopes we’d taken to approach the other notches. It was grueling, but I found it manageable, so long as I kept pouring water on myself. On the other hand, Noah was still struggling and fell behind quickly, although he stayed within sight of me much of the way up.

Eventually I pulled into the gravel parking lot at the base of the infamous Mt. Washington Auto Road. Again, no shade was to be found, but with the temp peaking at 95 degrees, I loaded up on ice and headed out with Jay and Paul, who quickly gapped me as the climbing continued for another 4 miles to the top of Pinkham Notch. Overall, that climb had ascended 1200 feet over 11 miles.

Then came the final payoff: a 15-mile, 1500-foot descent down from Pinkham Notch, into the woods and down to Jackson. My legs were so beat that I didn’t push the descent, but just rolled with it. Just as I was thinking I could go wade in a mountain stream, Noah caught up with me and left me behind, so I plodded on.

I eventually reached the town of Glen, where 16 rejoins 302 and again becomes a major thoroughfare. As I looked left, I saw a moderately-sized hill that just wasn’t going to happen. So I pulled into a Dairy Queen parking lot and rested for a few minutes before finishing the final two miles to the last rest stop. That was the only unscheduled stop I made during the ride; I hadn’t gotten off on any of the hills, but I needed to gather my strength before attacking that one just before the rest stop.

The Final Countdown

The last rest stop was a grassy lawn—essentially someone’s yard. I laid on my back and just gasped due to the heat. It was only 13 miles to the finish, so I would certainly finish it, but I needed another good rest first. I downed half a can of Coke, filled up with ice, and poured ice water over my head before following my buddies, who had left five minutes earlier in hopes of finishing within eight hours.

Again, once I was back on the bike things settled into place, and I made okay time. I wasn’t strong, but made steady progress. With all the climbing behind me, it was just a question of closing it out, and surviving that final mile.

The final segment—West Side Road—was a long but nice ride, although it felt like I was still climbing a false flat. Finally I came back out onto Route 16, and half a mile later passed the point where we’d turned onto the Kancamagus. I marshaled my strength and made the turn onto Bald Hill Road that led up a punishing ascent up to the finish at Tin Mountain (officially it gains 300 feet in 1 mile). It was as steep and difficult as anything we’d done, but I finally drifted into their driveway and hung gasping over the bars for a minute before signing in and meeting up with the guys.

Final tally: 108 miles in 8:15, with 5800 feet of climbing and an average speed of 16 mph. For the mappy junkies, here’s a link to the GPS log.

The After-Party

I tried to eat a bit as we sat outside the Tin Mountain cabin, but really only managed to down a couple chocolate milks. It was still too hot to let our core body temperatures drop, and we all were feeling the effects. But this is where my second grand pre-planning idea paid off in a huge way.

I knew it was going to be hot. I knew we were going to be near lakes and streams. I knew we were going to be four stinky, grimy, sweaty guys stuck in a car for three hours. So one of my pre-ride emails suggested that everyone bring swim trunks, and they had. We briefly discussed where to go, then went back to the truck and exchanged our sweaty kit for trunks and drove to the nearest possible water: the Swift River we’d ridden by on the Kancamagus at the start of the ride.

We quickly found a swimming hole others were using, pulled off the road, and picked our way down to the torrent. As I said earlier, the whole area was just a pile of granite boulders: the smallest being the side of a dog; the largest being as big as a tractor trailer. The water was absolutely blissful: cold yes, but not blisteringly frigid. We dunked in the deeper parts, then sat in the middle of the rapids and let the cold water flow over us. Jay clambered around and found a way to swim underneath a huge monolith in the middle of the river. Everyone agreed it was the perfect way to relax and cool off.

At this point, I saved the day again. Jay jumped into the water and lost his sunglasses in the torrent, but I was able to spot them, so that was gratifying. Less gratifying was learning that Noah had stolen a towel from the hotel, when we had earnestly promised them we wouldn’t incur any incidentals. That was the one sour note of the trip.

The road home included a stop at a donut shop that featured (for me) more chocolate milk and a blissful rest in a big overstuffed armchair. Then we hit the Wolfetrap, a restaurant in Wolfeboro, Paul’s home town, so that was kinda cool, and my huge burger and cornbread were precisely what the chirurgeon prescribed. That was also where I saved the day yet again, pointing out to Paul that—despite his claiming otherwise—he really was about to leave his credit card behind with the check.

We got that straightened out and hoofed it back to Boston, where I was anxious to begin my next task: recovery! It was still Saturday night, and I had all day Sunday to shower, relax, fuel up, and rehydrate.

Das Ende

I really enjoyed the Mt. Washington Century. I think it lived up to its billing as a very challenging ride, but it was also just an awesome day all around. The scenery—the rivers, the mountains, the woods—was just breathtaking. The climbs were long and steady which made them very manageable but they still packed some challenging sections, and the descents were long and smooth. Sure, with a newer bike I could have pushed the top speed on the descents, but it was just as nice to let gravity do all the work.

The Plastic Bullet once again did its job admirably for an old bike with more than 20,000 miles on it. After the cable was swapped out, I literally didn’t once think about the shifting problems I’d had earlier that week.

This was my third complete century of the year, which puts me about on pace with my previous two years, and it certainly puts me in good shape for the PMC, which is only two weeks away (as of this posting). I’d love to do this ride again, but I’m not sure whether that will happen, with Jay moving away and the group likely to fragment.

Which brings me back to the idea that this was the last major organized ride for Jay, Paul, Noah, and I. From the ride to the post-ride swim in the Swift River, this was a perfect day and a fitting way to honor our friendship and our mutual encouragement. It was epic.

And I’m so glad I was able to convince them to go for Mt. Washington instead of the Climb to the Clouds. After last year’s CttC, we were too exhausted, overheated, and demoralized to even stay for a post-ride swim in nearby Walden Pond. The contrast between that and this year’s relaxing dip in a wild mountain stream just underscores what a truly awesome time we had on the Mt. Washington Century, making memories that we’ll take with us for years and years to come.

Chapeau, boys!

Right now my life consists of work, cycling, fundraising, and occasional sleep, so my periodic updates this time of year tend to cover a lot of ground… like this one, which covers the past month.

July was a memorable month, but not for good reasons. Although I usually spend most of the Fourth of July holiday on the bike, with one of those days comprising a century ride, this year a terrible cold hit me Friday afternoon and kept me housebound the entire holiday weekend. Pure suckage!

The next weekend I had to go up to Maine, and convinced myself that I could get some training in by riding the 70 miles from Portland to Augusta. That ride wound up being really difficult, thanks to my lingering illness, a 25-35 mph headwind that hadn’t been forecast, and a mile-long section of muddy dirt road up and over a big hill in Sabbatus. But at least I managed to get some time in the saddle…

Which I needed, because the weekend after that was the CRW’s Climb to the Clouds, a very hilly century that goes up Mt. Wachusett, and is a traditional warmup for the Pan-Mass Challenge.

So CttC was just brutal. Combine my reduced training this year with oppressively humid 96-degree blazing sun and the CRW’s extremely limited idea of what constitutes a supported ride, and you can begin to imagine how difficult it was. Thankfully, I can say that my age wasn’t a factor, as my three buddies (all 17+ years younger) also concluded that they never wanted to do that ride again.

The ironic thing is that I spent half the day hammering, thinking I was chasing them, when actually I was ahead of them. Although I let them go ahead after the first 10 miles, they stopped at a water stop I skipped. I was surprised to see them ride past me in Princeton, where I stopped but they did not. So I got back on the bike and chased, unknowingly passing them *again* when they stopped at a convenience store. So I beat them over the mountain, and they only caught up with me after I’d spent 20 minutes at the next water stop, 53 miles in.

And as I predicted last year, the summit road was closed to us for the third year in a row, which was disappointing.

Toward the end of the ride, I was nauseous and unsafely overheated, and kept pouring water over my head to cool off. I stopped at the little Chinese grocery in West Concord and picked up their last two bottles of water, only to discover on gulping it down that it was seltzer! I sipped what my stomach could tolerate and poured the rest over my head and limped to the finish, where I pretty much just collapsed. But not before getting shit from the ride organizers for asking if I could have some ice. I was too destroyed to muster any argument when the guys decided to go home early rather than take the traditional postride dip in Walden Pond.

Definitely one of my worst days on the bike. There damned well better be some training benefit, after all that suffering!

And to make matters worse, my brand new $700 bike computer / GPS failed to record the quarter of the ride that included Mt. Wachusett and the following descent (GPS data). I had already left its heart rate monitor at home, because it had been malfunctioning. At least Garmin is replacing the HRM strap; hopefully the new one will last longer than the first one.

And then yesterday Boston tied the second hottest temperature ever recorded in the city’s 140 years of keeping records. Thinking I couldn’t get into much trouble in just one hour, I biked home from work in 103°F / 40°C heat. Against a convection oven-like 25 mph headwind, over three sections of stripped/grooved pavement along one of Boston’s biggest and fastest 6-lane arterials, and then stupidly up and over Dorchester Heights, just for fun.

That kind of heat will raise your heart rate 10 bpm no matter what you’re doing, and by the time I was done my heart was pounding and I was feeling very lightheaded. Kinda scary! Hopefully this stretch of intense heat will break and the weather will be more forgiving for the upcoming PMC ride!

And that brings me around to the tiny list of positive things that happened this month. First, Garmin did replace my problem HRM strap, and the new one seems to be functioning well; tho I probably will use it sparingly until PMC weekend.

Second, a question I’d sent in to the RoadBikeRider online magazine was published this week. The question was about how to fit a cooldown, stretching, shower, and recovery meal all into the half hour after stopping that is the optimal window for those activities. You can see the full question and RBR’s response here.

And, finally, the news that really matters: PMC fundraising. Once I finally started getting fundraising letters out, the money came in quite readily. I’ve surpassed the minimum and made the Heavy Hitter level for the sixth year in a row, and have settled at $7,200 for the moment, which is quite satisfactory, although there’ll be additional donations coming in over the next month or two.

Naturally, if you haven’t made your donation yet, please do so here.

And PMC weekend is only two weeks away. I’d normally be excited, but after the difficulties of the Maine ride and CttC and this brutal heat, I’m a little gun-shy about looking forward to riding. It hasn’t been a great year for any of my cycling buddies; just ask Lynda, who canceled her plans to do the epic 745-mile PBP ride; or Paul, who bought a pricey new bike only to have Jay destroy it by driving his truck over it on the way to the 150-mile Harpoon B2B ride that was supposed to be the highlight of his season.

The bad juju is in full force this year.

So we’ll see. There’s two more weekends before the PMC, and I don’t have anything special planned for them. Hopefully there’ll be a couple Quad rides and some hill repeats in there, and then a relaxing, rewarding PMC ride once the calendar turns to August.

Hopefully…

Lots of things to talk about this week, not all good.

I've started my fundraising, and am presently at $435. That's slightly ahead of where I was last year at this time, but not up to where it ought to be. I've had a lot of people delaying or reducing their donations this year, and I haven't had any luck with the posters I put up. It's a little discouraging, but hopefully things will pick up over time.

Wednesday I had the first ride I ever had to abort. Although I was already sensing that I was weakened from overtraining, I'd planned to ride to Gloucester and back, about 80 miles, but in the 95-degree weather I started suffering heat exhaustion about 30 miles from home. Now, I'm an exceedingly proud person, and calling for help is completely humiliating, but I had to admit that I really needed it. I wound up limping to Jeanie's house, where I took a cold shower, sat in front of her A/C, then was driven home. Still, I enjoyed tooling around Gloucester, and did get 70 miles in...

On a positive note, I've surpassed several mileage "milestones", as it were. I've done more than 100 miles per week for five of the last six weeks, and have biked 1500 miles since October. I am also a day or two shy of passing 500 total hours on my bike (since October 2000), and have ridden over 7000 miles in that same time period. Of course, about a month from now I'll have eclipsed 7500...