September’s been a dud as far as riding goes. It’s been unseasonably cold and rainy, I started the month still suffering from a summer cold, and to be honest even when the weather’s conducive I just haven’t had much desire to lay down the miles. Poop on that!

WPW Fall Rally: Morning on the Yough

WPW Fall Rally: Morning on the Yough

WPW Fall Rally: Soutersville Train

WPW Fall Rally: Soutersville Train

I skipped the Pedal the Lakes century up in Mercer County due to a showery forecast and the organizers’ persistent refusal to provide GPS route data, something which has become de rigueur for everyone else.

I had the opportunity to do a 1am night-start 200k brevet, but just couldn’t motivate myself. It was a cold night, a very hilly route, I haven’t got the form, and it was Inna’s last night at home before a long trip. Having seen the weary finishers—all three of them!—I’m glad I gave it a pass.

That 200k ended at the Western PA Wheelmen’s fall rally, which I did go to (at a more respectable 9am). It was still cold and foggy, but it wasn’t dark, and I only had to pedal 35 miles instead of 135! I still went off course twice, and it was hilly enough to dissuade my lazy ass from undertaking an additional 32-mile route after lunch.

On the other hand, I saw the 200k riders finish, got to socialize with a bunch of folks, picked up the snazzy new argyley WPW jersey I’d ordered, and got a free (surplus) WPW “ride leader” tech tee and wind vest.

This month of poop gets even worse going forward, as I’m leaving to join Inna for a week in Seattle and Victoria. There goes what’s left of my late-season fitness!

Unfortunately, I could really use that fitness, because with the change of seasons comes the transition from endurance riding to obscenely steep and painful hill repeats in preparation for my first infamous Dirty Dozen ride. And if I get enough climbing in, I’m hoping to hit a quarter million feet of ascending by the end of the year. But in order to do any of that, I need to re-find my lost bikey mojo.

The sole bright spot has been new advances with my Edge 820 bike computer. First, I was able to wirelessly connect my new phone to my Di2 electronic shifters, download new firmware patches, and install those patches myself. Previously, you had to pay a bike shop to have their mechanics do all that; and even when Shimano’s hardware and firmware supported it, my old phone didn’t. Now, when Shimano introduces new functionality, I can just download and install it myself. So that’s quite a convenience.

And after posting an idea for a new data field on Garmin’s product forum, I found a guy who wrote a ConnectIQ app called AppBuilder that you can download to your bike computer and program to calculate your own data fields, which is exactly what I did. So now, in addition to the regular fields that Garmin supplies, my bike computer now displays how many feet of ascent I’ve done per mile for the current ride. That’s something I’ve been following since moving from flat Boston to hilly Pittsburgh, and having my cyclocomputer display it for the current ride is pretty darned cool.

But the reckoning is coming… DD minus 10 and a half weeks.

Whenever I talk to people about electronic shifting, someone inevitably freaks out. “OH MY GHAWD WHAT IF YOU FORGET TO CHARGE YOUR BICYCLE AND IT STOPS SHIFTING IN THE MIDDLE OF A RIDE?!?!”

Obviously, electronic shifting isn’t for everyone. Like any system, it has advantages and disadvantages. I wouldn’t condemn anyone for their preference for mechanical shifters, just as I don’t expect to be condemned for generally preferring rim brakes over disc brakes.

Di2 battery

Di2 battery

However, let’s at least base our preferences on facts and reality, rather than “alternate facts” derived from wild conjecture and irrational fears.

In the case of electronic shifting, running out of battery power—whether thru actively depleting it without recharging or through letting the bike sit idle for months—will never be an issue for typical riders.

I started riding electronic in April 2013, more than four years ago, when I bought a bike featuring Shimano’s new Ultegra Di2 10-speed groupset. I’ve put 13,000 miles on that bike, or over 3,000 miles per year. And the data from my Di2 system tells me that on average I shift every 20 seconds while riding.

In all that time, I have never once depleted the battery. Was I a battery-charging maniac? Not at all. I usually charged it just three times per year: something like March, June, and September. And I virtually never had less than 50 percent charge, even if the bike sat idle for six months through the winter.

Until this year, I was getting 1,500 to 2,000 miles of riding on a charge. But in May I added another component to my system: the D-Fly wireless kit, which allows my electronic shifting system to communicate with my bike computer, to add gear shifting data to my ride logs and display what gear I’m in and how much battery I have left.

The D-Fly draws power from the battery to wirelessly transmit ANT+ data to the bike computer, so that noticeably reduced my overall battery life. But even with the D-Fly attached, I’m still getting two months and more than 1,000 miles of riding out of a single charge. Battery life simply hasn’t been an issue.

The people who cite battery life as a reason to avoid electronic shifting seem to think we’re still living in the 1980s, when NiCad batteries were state of the art. I have news for you: lithium batteries are lighter, smaller, have way higher energy density, don’t spontaneously discharge themselves over time, and don’t lose capacity by developing a “memory” after charging. Welcome to the 1990s; please update your expectations accordingly.

The only instance where battery life might be a limitation would be for ultra-endurance rides of greater than 1,200 miles where you couldn’t stop for an hour to recharge. I don’t know of anyone who rides 1,200 miles without sleep… Still, the obvious answer to that: carry a fully-charged spare.

For any normal rider, running out of juice is simply not going to be a concern.

Of course, I’m not saying electronic shifting is for everyone. I do appreciate the advantages of never breaking a shifter cable, never missing a shift, never worrying about crosschaining, and having gear and shifting data in my ride log. But I also acknowledge its drawbacks: it’s more expensive and can be really finicky to setup.

But running out of battery in the middle of a ride simply doesn’t happen, and anyone who says otherwise is either very misinformed, grossly incompetent, or intentionally lying to you.

Three months ago, I replaced my aging Garmin Edge 800 GPS cycling computer with the new Garmin Edge 820. After 52 rides and 1,400 miles, it’s time for an in-depth review.

I’m a data weenie. I was logging my weekly miles all the way back in 2000, and saving GPS tracks of significant rides using a handheld GPS long before GPS tracking was integrated into bike computers. So I’m sensitive to the features, usability, and reliability of my bike computer.

Edge 820 Di2 gearing & Strava Suffer Score page

I was really happy with the Edge 800, which I bought when they first came out in 2011. Over the years, Garmin introduced the newer Edge 810 and the larger Edge 1000, plus the smaller Edge 500 and 510, but the 800 was so good that I never felt the need to upgrade.

However, after six years, my Edge 800’s battery had begun to flag, and I was tempted by all the improved features and functions of the new units. Last July, when Garmin released a new unit in the 800 series, I read the reviews like a hawk, and finally picked up my unit in February, after I returned from my five-month stay up in Maine.

I’ll divide this review up into four sections: basic features and things I’m neutral about; features I don’t know much about because I didn’t test them; features I like and am excited about; and the things that disappoint me about the unit. Then the executive summary is at the end.

The Neutral

My biggest problem with my aging Edge 800 was battery life. I need a device that will record GPS data and provide navigational cues through at least a 9-hour 200k ride. I recently completed a 7-hour century ride, and had over 40 percent charge left, which means the Edge 820 can be expected to live up to its spec of 12-hour battery life.

I was a little concerned that the 820 has a smaller screen than the 800. On the other hand, it has better resolution. So far, reading the screen has not been a problem at all.

At a minimum, I need to be able to import GPX-formatted route data from the computer to the unit. No problem with the 820.

I also download all my raw GPS data (Garmin .FIT files) to my computer for archival. Thankfully, the 820 still supports this type of access.

Rather than coming with an SD card slot, this device has a fixed memory capacity of 8 GB. So far that hasn’t been an issue, and I can only see it becoming so if you were to load multiple continents’ worth of map data. Activity .FIT files don’t take up very much space at all.

Sometimes, if you were following a course and deviated from the path, my 800 would simply give up trying to navigate for you. The 820 hasn’t been bad, in that it tries to get you back onto the course.

Some folks have complained about the altimeter being off, or drifting during rides. I haven’t noticed a problem, given the understanding that barometric altimeters have limited accuracy by definition.

One new feature on the 820 is real-time weather alerts. This would be a cool feature, except it only receives major alerts like flash floods. Useful, but only rarely. Given that the device has a live Internet connection through a Bluetooth link to your cellphone, I’d rather see live local radar and notices of impending rain. There’s an app for that in Garmin’s ConnectIQ Store, but I haven’t tried it out yet.

Another new feature is the display of “recovery time” at the end of each ride. Basically, it’s a gratuitous, dumb feature. Recovery varies from person to person, and even a novice rider can sense how long they’ll take to recover from any given effort. I’ve turned that feature off.

One undocumented feature on the Edge 800 was the ability to set the boot screen text that displays when the unit powers up. I had set that to an inspirational message—“Always lead, never follow”—plus my phone number in case the unit was lost. I was happy to learn that the feature still works on the 820.

One evening, I learned that the Edge 820 automatically switches to an inverted-color display at night for better visibility. I’d love to say that’s an improvement, but it’s a feature that was also available on the 800; I had merely turned it off at some point!

The Unknowns

The Edge 820 comes with a power saving mode that comes on when the battery reserves start getting low. I haven’t tested it yet.

It also introduces an “incident detection” feature, where it’ll alert a contact if it thinks you’ve crashed. So many other users reported false positives that I have never turned the feature on.

Presumably you can load your own maps onto the unit. That’s a feature that existed on the Edge 800, but I’ve never felt any desire to mess with the maps that it came with. Though it might be a handy thing if you traveled or moved to a different continent…

Although Garmin did away with the idea of bike profiles, you can still set odometer values based on the sensors that are on each bike. Seems like a lot of work, and I don’t need total odometer readings while riding. I can just get that from the laptop.

The most exciting and useful feature that I haven’t had the opportunity to test is the Edge 820’s FE-C indoor trainer integration, which should allow the computer to set the trainer’s resistance level. In addition to using the Zwift social training app, theoretically you can follow a real-world course that you rode, and the unit will alter resistance to simulate the terrain. I’m looking forward to that, but that’ll require a very expensive trainer purchase, which I’ve been delaying.

The Positives

Edge 820 map page
Edge 820 Strava Live Segment page
Edge 820 Profile page
Di2stats.com gearing pie chart

Let’s start with the obvious. Coming from a seven year old model, the Edge 820 has updated maps, and lots of software updates, both built-in as well as regular firmware updates going forward. It’s nice to be back on a supported platform!

In addition to GPS satellites, the new unit also has the ability to receive signal from the Russian GLONASS constellation, making GPS locks faster, more accurate, and stable. I suspect this is also the reason why the regular signal stops/dropouts/starts I used to have near heavy infrastructure (e.g. bridges, railways) on the Edge 800 are almost completely gone.

With a Bluetooth connection to my phone, the Edge 820 will display incoming SMS messages, and notifications for incoming calls. It works well, and has been a nice convenience, given how many hours I’m on the bike.

For ultra distance rides, you can plug the Edge 820 into a portable battery pack and it’ll charge itself, while continuing to record ride data. To be honest, I think my Edge 800 could do this, but I never bothered to test it. However, I tested the 820 for this review, and it worked well.

With my Edge 800, after a ride I had to connect the device to my laptop and manually kick off a synchronization job to upload my data to Garmin Connect, then manually upload to Strava, as well. The 820 will use Bluetooth or Wifi to automatically upload ride data to both sites without a wired connection. Very convenient, especially when you’re away from home at a multi-day event.

Garmin has created an open API called ConnectIQ for developers to add their own apps and custom data fields to the unit. A favorite is the Strava Live Suffer Score data field, which displays how hard your ride is. I’ve got a great idea for my own custom data field, but setting up the required Windows dev environment is a huge bother.

The Edge 820 also will store your favorite Strava road segments and display a countdown and timer when you are on them, allowing you to measure your effort against your PR or the KoM holder in real time. It’s a cool feature, except for the discouraging Sad Trombone sound it makes when the record-holding time finishes before you do…

With an extra bit of hardware, the Edge 820 will communicate with your Shimano Di2 electronic shifting groupset. That allows me to display which chainring and cog I’m in (both numerically and graphically), as well as the system’s current battery level. It’ll beep when you’re at your absolute highest and lowest gears, and give you a text alert if the Di2 battery goes below 25 percent charge. On top of all that, all your shifting data gets added to your ride logs, which you can analyze later through sites like di2stats.com.

The Negatives

The touch screen is really poor… nearly unusable. Every interaction with the unit must be very deliberate, and often repeated. My unit is barely tolerable, but many people have simply given up and returned theirs for a refund. It’s terrible.

Scrolling and zooming the map are incredibly slow. Like, almost unusably slow. If there’s one thing a mapping GPS should get right…

Loading and calculating routes is even worse! If I have a stored GPS breadcrumb track, it shouldn’t take upwards of five minutes for the unit to begin offering navigation cues. Why would it take even longer than the Edge 800?

When I first started using the unit, it spontaneously turned itself off several times. Fortunately, after a little while, that stopped happening.

Along with SMS and incoming call notifications, it would be nice if the unit offered incoming email notifications, as well. Missed opportunity.

I had a lot of trouble setting my Max Heart Rate. By default, the unit will override any number you specify with whatever it gets from a heart rate sensor. But since HRM straps are notorious for occasionally giving ludicrously high readings (e.g. above 220 BPM), it kept resetting itself until I shut off the auto setting and entered a fixed HR max.

Presumably, the Edge 820 supports Live Track, where you can send a URL to a friend, and they can visit a site that shows where you are in real time. In my experience, the data connection to the phone is too fragile, and I’ve never gotten Live Track to work… not even once. Both Google Maps’ Location Sharing feature and the Glympse app work far better.

Then there’s Group Track, where you and your riding buddies can presumably “Live Track” each other, with the head unit displaying the locations of your other riding buddies in real time. Even if I had other riding buddies with compatible head units (not very likely), the fact that it depends entirely on the utterly non-functional Live Track feature means I can’t use it anyways.

That cool Shimano Di2 integration I talked about above took *way* more time, effort, and money than it should have. First, to get the Di2 to talk to the Garmin, I knew I had to order and add a tiny wireless transmitter and a cable to my Di2 system, plus the special tool to connect the cable. When that didn’t work, I learned that I also had to order and replace my old battery mount. Tiring of the runaround when that didn’t work, I brought it in to the bike shop, where they individually updated the firmware on every piece of my Di2 setup. That didn’t work, either, so I ordered a new front junction box, plus two more new cables. When those came in, we installed them and did two more whole rounds of firmware updates during several phone calls with Shimano support. Then we finally had to pair the Di2 transmitter with the Garmin, and iron out a few minor bugs in the system (not reading battery level, thinking it had 11 sprockets rather than 10). In the end, it took a couple months, three trips to the LBS, a few calls to Shimano support, seven new parts from four separate orders, and an extra $450 in parts and labor to set up, just for my head unit to display what gear I’m in. Had I known that at the beginning, I never would have bothered.

The Bottom Line

Ultimately, the unit mostly works, and is generally okay. It’s a good step up from my aging Edge 800. I like the auto-upload, custom data fields, Di2 integration, phone and text message notifications, and Strava Live Segments. And I’m hoping that the FE-C trainer integration works well. But none of those are must-haves, so I wouldn’t say I’m blown away by the new features.

On the other hand, a lot of people really hate the unit, and I can understand why. The touch interface is terrible, basic functions such as loading routes and map data are ridiculously slow, and key features like Live Track, Group Track, and incident detection simply don’t work.

While Garmin enjoyed a market-leadership position in GPS cycling computers for several years, riders who are frustrated with Garmin’s lack of responsiveness are turning to other vendors, now that quality alternatives are available like the Wahoo Element Bolt.

By all measures, the Edge 820 should have continued Garmin’s domination of the GPS cyclocomputer market. I really hope they have learned the drawbacks of releasing such a flawed product and do a better job next time. In the meantime, hopefully they’ll keep issuing firmware updates that fix the Edge 820’s broken features and provide more compelling functionality.

It’s still a good unit, but it’s definitely not the category-redefining product that I had hoped it would be.

Okay, I’ve put about 800 miles on the new bike, including two centuries and one epictacular 130-mile ride yesterday (more on that shortly); it’s time for the full-blown review.

When I set out on this (bike-buying) journey last fall, I knew it would be difficult to find a bike that would live up to my experience with my old steed, the Plastic Bullet. It served me very well, and I put 22,000 miles on it. So the bar was already set very high for the new bike.

For that reason, and because I wound up buying the exact same model, I won’t say that the R2 is a radical improvement. The geometry is almost identical, and even the curb weight is the nearly same as the old bike (the 2.5-ounce difference being about the weight of $3 in quarters).

That might sound underwhelming, but for me, finding a bike that can live up to the legacy of the Plastic Bullet (PB) is a really awesome thing. And I’m doubly appreciative of that, given the large spectrum of poorly-suited bikes that I test-rode! So despite it not being a quantum improvement, I’m absolutely and unreservedly delighted with the R2.

Although I make it sound like it’s just the same as my old bike, it’s really not. Aside from being sleek, shiny, and new, it’s no less than seven model years newer, with all the improvements and refinements that implies. I really think it rides noticeably better than the PB.

One change is that Specialized has tuned the bike a lot by altering the tube shapes. The beefier chain stays make the drive train stiffer, the thinner seat stays are more flexible to ease road feel, and the head tube (which is disproportionately large in my 61cm size) is less ugly/noticeable than before because the tubes arc and gracefully ease together where they join.

They also flattened the top tube like a squashed cylinder. That might not sound important, but it’s an unexpected convenience when stopped, when I (like many riders) will sit on the top tube. However, the lesser top tube height makes it a more difficult place to affix a name decal!

The handlebars are likewise flattened on top, providing a more ergonomic place for one’s hands. And of course the Roubaix’s classic polymer “Zertz” vibration-dampening inserts improved over the years, as well.

One of the more noticeable differences is that the R2 uses internal cable routing. That gives the bike a cleaner, refined look, but sometimes confuses me, because when I used to work on the PB on a repair stand, I’d stop a rotating rear wheel by reaching up to the top tube and yanking on the exposed brake cable that ran alongside it; no exposed cables on the R2!

A major difference that worried me initially was the move from a triple chainring to a compact double, and the consequent loss of top- and bottom-end gears. Of course, I never think about needing either an easier or harder gear during regular daily riding, but I have noticed it on hilly rides, where my old triple gave me both easier gears for steep climbs and higher top-end gears for faster descents. So far that hasn’t been a show-stopper for me, but we’ll just have to see how it goes. I expect mountainous rides will be more challenging than they used to be.

I was also concerned about the shifting reliability of the compact double (they tend to be balky because of the large difference in size between the large and small chainrings), but that has been admirably handled by the electronic brain drivetrain.

Which brings up the biggest, most obvious difference with the new bike: the Di2 electronic shifting, which I’ve pretty thoroughly described in a previous post. I can’t say it has been 100 percent flawless, but it’s definitely close (much closer than old-school mechanical shifters), and in the long run I’ll be very happy that I spent the extra money.

I recently toggled its software flag for multi-shift, which lets me swap two or three gears with one long button click. That makes it a lot easier to navigate urban streets, with all the stopping and starting you have to do in town, and has perfectly addressed the only complaint I had about my bike’s electronic brain. I’m only 60 days in, but Di2 has been a daily delight.

And there’s always the cool factor of the sound of electric servo motors moving the derailleurs into a new position. During my first group ride on the new bike, after one front chainring shift my buddy Joe called up to me from behind, “Dude… Are you a robot???”

Damned right! I’m a macheen!

So while you might not have noticed much enthusiasm in my comments to date, I’m absolutely delighted with the new bike. I went into the process with extremely high requirements, and R2-Di2 has surpassed even those expectations. I was looking for the best bike on the planet, and I’m very happy to say that I think I found it.

Ride on! Right, R2?

(Photo essay still forthcoming…)

Last fall, when I kicked off my search for a new bike, it was clear what I wanted: something just like my old bike, but better. The “Plastic Bullet”—a 2006 Specialized Roubaix Expert—had served me very well over the years, and I had nothing to complain about, save that it was showing the signs of age. Because of that, the new version of the Roubaix was at the top of my list when I started thinking about a new bike.

However, a lot has changed since 2006. There are a lot more bikes out there, and I didn’t want to stick with the Roubaix if there was something better to be had. So I decided to shop around and ride a bunch of bikes, exploring new technologies like disc brakes, electronic shifting, SRAM shifters, and so forth.

I tried everything out and enjoyed the process. I test-rode eight bikes, with a collective price tag of $32,300. I learned that I hate disc brakes, SRAM shifters, FSA components, integrated seatposts, and pretty much all bikes manufactured by Trek. On the other hand, I really liked Shimano’s electronic shifting, the Cervelo R5, and Giant Defy Advanced.

Roubaix

But above all, I learned that the Roubaix still seems to be the best all-around bike for me. It fits me and my style of riding well, does a great job absorbing road vibration, and strikes a good balance between ride-all-day comfort and ride-all-out performance.

To make a final decision, I had my LBS bring in a Roubaix that was nearly identical to the one I was looking at. After test riding it, I went home pretty well convinced that I’d be buying the exact same damned bike I bought back in 2006: a Specialized Roubaix Expert. I’d still have to special-order it though, because dealers simply don’t stock bikes my size.

An hour after that test ride, I received an email from the shop, indicating that the following week Specialized would be offering a manufacturer’s discount on that bike: a 20 percent price cut, or a $1,000 savings! Needless to say, I jumped at that. A long two weeks later, I took delivery.

So how is the new bike different from the Plastic Bullet? Aside from being newer, there are really only two significant ways.

One is the Shimano Di2 electronic shifting. I’m pretty excited about that, but I don’t need to say too much about it here, having already written about it in one of my test ride roundups back in September.

The other is that while both bikes are primarily clear-coat over carbon fiber, the new bike has red and white highlights (ironically, those are my high school colors), rather than blue and silver. So the blue tires are gone, and I’ll have some extra work coordinating accessories to match the new color scheme!

Which brings me to the real question: what to name it! This is also a little two-part story.

First, it’s my second Roubaix. To honor that, let’s call it Roubaix-2, or just “R2”.

Second, its most interesting feature is the electronic shifting: Shimano’s “Digital Integrated Intelligence” or Di2.

Put those together and you get the new bike’s moniker. Allow me to introduce you to R2-Di2! The reference to the iconic Star Wars robot is intentional, and appropriate for a bike with electronic shifting. It even makes cool robot noises as the servos shift the derailleurs to change gears!

Having only received it Tuesday, I haven’t got much to say about its riding characteristics just yet. I’ve still got to get it properly fitted and add a bunch of accessories to it before I share any pictures. So it’ll be a few weeks before I have a lot to share, but be patient; those’ll all come in due time.

Of course, saying hello to R2 means saying goodbye to “R1”: the Plastic Bullet. After seven years and 22,000 miles—including seven Pan-Pass Challenges and dozens of century rides—we’ve unrolled an awful lot of road together. It’ll still see the tarmac from time to time—on rainy days or city errands where I don’t want to break out the new bike.

But as of today, she’s second saddle. It’s time to start making a new history of travel adventures with the R2. Stay tuned!

It’s been a couple weeks, but I figured I should capture some notes from my first weekend of shopping for a new bike and doing test rides. Maybe this will be useful to you, maybe not.

Cervelo R5
Trek Madone 5.9
Trek Domaine 6.2
Giant Defy Advanced 1

On the process:

As the buyer, you’re in the driver’s seat. Take your time and check out everything the marketplace has to offer. Put the new innovations to the test. Ride a lot of bikes from all over the spectrum—even stuff you have no intention of buying—and have fun doing it. There’s a lot of good bikes on the market and it can be hard to choose between them, but in the end, something will speak to you.

The one thing to be careful about on test rides: remember that you’re evaluating the bike, not the fit or the gearing or the saddle or the derailleur adjustment or the wheels, because all those things can (and will) be changed. So what’s left? A little of this and that: road feel, frame fit and finish, handlebars and stem, weight…

On the SRAM gruppo:

SRAM wasn’t a player when I bought my last bike, and everyone crows about how great their gruppo is, so one of my first goals was to put it to the test.

What I found didn’t impress me. Their stuff’s light, but I think it’s poorly designed. My main complaints revolve around how their shift levers work: push halfway and you shift into a harder gear; push further and you shift into an easier gear; push farther still and you shift into a second or even a third easier gear. Great idea, right?

Wrong. First, when I jumped multiple gears I found it hard to calibrate whether I was downshifting two or three cogs. That can be annoying when you’re searching for just the right gear ratio.

Much worse things happen if you are on a steep ascent and go to downshift but only manage half a throw, which actually causes you to upshift into a harder gear! And if you already happen to be in the largest cog (easiest gear) and try to downshiftpast that, SRAM only blocks the far throw of the lever; it’s perfectly happy to accept half a throw, which again causes you to upshift: exactly the opposite of what the user intended. And that’s my definition of “bad design”.

Another thing I’m used to doing with my Shimano setup is shifting both front and rear simultaneously. By upshifting one while downshifting the other, I am able to make a smaller jump between gear ratios than if I just shifted the front chainring. On Shimano it’s easy, because you can throw matching levers; but on SRAM, it’s confusing, because you have to remember throw one lever halfway and the other one all the way.

So even though a lot of people juice over SRAM’s gruppo, I found a lot to dislike about it. Combine that with SRAM brakes’ weaker stopping power, and I’ve pretty much ruled them out right from the start.

On Shimano’s Ultegra electronic gruppo:

Another thing I wanted to try out was Shimano’s brand-new enthusiast-level electronic shifting. I’m not a huge fan of technology for its own sake, especially when you have to pay a big premium for it. On the other hand, a lot of people have been pleasantly surprised by the electronic Dura-Ace components, so I figured I’d ride these for myself, even if I was unlikely to spend money to have battery-powered servos to do my shifting for me.

The bottom line is that it’s just as slick as promised. The shifting was quick, smooth, effortless, and intuitive. It was nice… but I had expected it to be nice.

What I hadn’t expected were some of the implications. Because the electronic shifter cable isn’t under tension like mechanical cables, there’s no risk of a shifter cable ever snapping, which has happened to me two or three times on long rides. And since it’s not under tension, a new shifter cable doesn’t stretch, so there’s no need to go back to the bike shop to have derailleur adjustments done after a tune-up.

Not that you’d ever have to anyways, because the electronic shifters automatically adjust to keep the chain centered on the cogs. That means you’ll never have chainskip or balky shifts or need any adjustment of your drivetrain. Even if you do the most ridiculous crosschaining, the system adjusts the derailleurs and chainline to avoid the loud complaints that a mechanical setup would experience.

In other words, you wind up with a completely reliable, nearly foolproof, and maintenance-free drivetrain that you don’t have to think about at all. That has nearly sold me on Shimano’s Ui-2 gruppo.

The only things holding me back? It’s heavier than a mechanical gruppo. It’s a hell of a lot more expensive. And I have questions about its vulnerability in a crash scenario.

Definitely worth looking into if you’re in the market.

On Trek’s Domaine:

Another thing I wanted to try was the Trek Domaine. Trek is known for making Lance Armstrong’s bikes, but this brand new model is their first foray into the endurance bike market, which expects a fast bike with a longer wheelbase and more upright riding position.

Now, I’m biased against Trek. I’m usually not a fan of the favorite, whether it’s Lance Armstrong or Trek as the 300-pound gorilla in the mass-production bike market. But I wanted to give them the benefit of the doubt and ride this bike, since it ought to be a worthy entry into a fairly specific market.

It was also hard to get over Trek’s strident enforcement of how the name should be pronounced: doh-MAH-knee. As a designer, if you have to browbeat the user on something as basic as what your product is called, you’re probably doing it wrong.

I actually rode two Trek bikes—the other a Madone—and on both of them the chainstays flared out so wide that I found my heel kicking them on every pedal revolution. Both bikes were surprisingly heavy, too. The Doh-MAH-knee, despite being a comfort bike, did nothing to smooth the ride over rough pavement; it transmitted every shock, bump, and vibration from the road straight into the rider’s body.

I rode the Doh-mah-knee in the hopes that this new model would show me something that would overcome my natural aversion to Trek as a household name. While their bikes were okay, there was nothing outstanding about them that would lead me to choose them over more established and better performing endurance bikes.

The only thing that almost impressed me was Trek’s “Project One”, which basically allows you to choose what components your bike comes with. That’s a huge benefit over most bike companies, whose models only come in one or two configurations. But even Project One only lets you select from a very tiny spectrum of approved alternatives, so their vaunted configurability is actually not much more than a nominal advantage.

So don’t expect to see me riding up on a Doh-MAH-knee any time soon.

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

Ornoth climbing 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!

Ramping up!

Jul. 7th, 2010 10:14 am

The Fourth of July weekend is usually a big milestone on the way to August’s Pan-Mass Challenge, and this year was no different. I led into the weekend with a 50-mile solo ride on Thursday and a 12-mile kayak trip up the Charles River on Friday; both perfect, gorgeous days just before a massive heat wave hit Boston.

Saturday saw me joining a group of six other Quaddies for an extended ride out to Littleton, Harvard, and Sudbury. We did a nearly-identical ride last year, which was my second century of 2009, while this would be my third century of 2010.

Last year’s Fourth of July ride is also particularly memorable as the ride where the Plastic Bullet first developed the ticking noises that would doom it to ridiculous a three-month stay in the bike shop, as documented here.

Ironically, I was 70 miles into this year’s edition when my bike suddenly shifted into its hardest gear and wouldn’t shift out again. I’d broken the rear derailleur cable, which I knew in an instant because I’d broken the exact same cable last May.

I nursed the bike back to Quad Cycles, where I hoped I could get it fixed. Given that it was a sunny Saturday on Fourth of July weekend, I expected the shop to be too busy to help, but the store was completely empty except for two service guys watching television. However, when I told them what the problem was, they told me it was a very involved repair requiring them to disassemble the whole shift lever, and they couldn’t fit such a lengthy job in at the moment. When I asked whether I should wait for them to fit me in, they told me they had to fix two bikes that were ahead of me, and that would take them more than the two hours and eight minutes before the shop closed. It was obvious they had no intention of helping me, so I thanked them and left. Yes, I verbally thanked them; I didn’t “storm out” as they later told another friend who came into the shop later.

I was eager to get the bike repaired because I had major rides planned for both Sunday and Monday, so on the way home I tried my local bike shop, Back Bay Bikes. They’re usually way too busy to accommodate walk-ins, but this time they surprised me by putting the bike right up on the repair stand, despite being considerably more busy than Quad Cycles had been. After I took fifteen minutes to rest, drink a Coke, and eat a Klondike bar, that “really involved” repair was complete, the derailleur was shifting as good as new, and my whole holiday weekend was salvaged. Back Bay Bikes: 1, Quad Cycles: 0.

Sunday Jay, Paul, and I went out to Sterling to do a very hilly ride around Mount Wachusett. Since the park’s access road was closed, we couldn’t get to the mountaintop. Although the ride was only 35 miles, I did convince the guys to do the ludicrous Mile Hill approach road, which was particularly debilitating after doing a century the day before. We rounded out a fine day by getting ice cream at Meola’s, canoeing and swimming at Comet Pond, then fulfilling my Fourth of July tradition of Indian food with an amazing meal at Surya in Worcester, which is right near the always infamous Liscomb Street.

Then on Monday Jay, Kelly, and I did a very easy, short 32-mile ride around Cape Ann, which included wading at Wingaersheek Beach and swimming at Singing Beach in Manchester, followed by steak tips and ice cream. Another great day, closing a really superlative Fourth of July weekend.

Despite my aspirations, Saturday’s century took an awful lot out of me, and I wound up only doing 170 miles over those three days, when I’ll need to be able to do about 285 miles in three days for my Pan-Mass Challenge ride four weeks from now…

On the fundraising side, I think I’m doing well. I’m on the verge of having 50 donations, with a large number of donations still outstanding from people who said that they would help. That still won’t get me all the way to my goal of 100 sponsors, but it’ll put me in the neighborhood, from which I can make a last-minute push toward the target. Please visit ornoth.PMCrider.com to donate.

Next big event is the Climb to the Clouds century up Mount Wachusett, a traditional warm-up for the Pan-Mass Challenge. I am skeptical that they will open the access road, because the road resurfacing project is supposed to last until next summer! So this may be the second year in a row where the Climb to the Clouds doesn’t actually go to the summit, with maybe a third year happening in 2011! Very disappointing!

However, that can’t change how much I enjoyed the rides we took on this year’s baking-hot Fourth of July weekend.

I’ve wanted a heart rate monitor (HRM) for many, many years. They’ve been the gold standard for cyclist training tools for a long time, notwithstanding the recent trend toward power meters.

However, they’re somewhat expensive, and I never felt justified in spending the money. Plus I feared it would be like the cadence sensor: useful only for a short period of time, enough to calibrate one’s own internal sense, and extreaneous thereafter.

However, prices have come down, and an HRM would have been handy indeed for my wintertime indoor trainer workouts. So I finally picked up a cheap Sigma Sport PC14 on sale at the Noshbar.

Cheap is the word. Any electrical field will cause the unit to either register a pulse of zero or over 200: a near impossibility for someone my age. So I can’t really trust it to record the max heart rate I hit during any given workout. Unfortunately, your max is what all the training heart rate zones are based off, so I’m fiddling with it to find my true max.

Here’s my initial observations. They’re based on only two days’ worth of use, so they’re highly provisional.

heart rate monitor

Resting heart rate, taken before getting out of bed in the morning, is a good indicator of general fitness. A sedentary person might have an RHR in the range of 60-80 beats per minute, while a trained cyclist would be closer to 45-55, so lower is usually better. I’ve seen a low of 51 bpm, and a sustained reading of 53, so that’s in line with my expectations. I remember taking my pulse in high school when I was bored and getting resting rates below 48.

Max heart rate is largely a function of age, and the standard formula for estimating it is to subtract your age from 220, but that will then vary based on your fitness level, with higher numbers being better. A 45 year-old’s expected values range from 164 to 186 bpm, and although I predicted I’d max out at 165, I’ve seen readings as high as 171. That’s in line with the base formula, although again that’s preliminary and more testing is required.

Using that as a base, I derived several additional numbers. My aerobic limit is around 120 bpm (70% MHR), and recovery rides should stay below 140 bpm (80% MHR). My lactate threshold should be somewhere between 140 and 155 (80-90% MHR).

The most interesting thing I’ve learned so far is that you can do easy aerobic training or you can do hard, painful interval training, but you derive very little training benefit in the middle ground between them. Below 70% MHR you’re burning mostly fat and can go all day; above 85% MHR you’re burning glycogen and building up lactic acid and need to rest and recover every few minutes; but in that grey area between 80-85% MHR, you’re working way too hard to burn any fat, but not hard enough to exercise your VO2 and ability to buffer and clear lactic acid. So that’s a dead zone you should avoid training in; for me, that area is from about 137-145 bpm. In short: go easy or go hard, but don’t go halfway.

For anyone trying to lose weight, that information is incredibly important. You’re always drilled with the value of exercise— particularly aerobic exercise—in losing weight, but there’s a huge mental trap there. Although aerobic exercise raises your heart rate, it doesn’t raise it enough for it to feel hard. Since most people think “harder is better”, they’ll often push themselves and work out in this middle ground, where they’re working hard, but not all-out. Unfortunately, at that level you’re only burning glycogen, not fat, and you’ll just crave sugar to replenish your blood and liver glucose levels. To lose weight, you have to do gentle exercise for very long periods of time, and it shouldn’t feel very difficult at all.

It’s similar to one of the problems I observe in novice cyclists. They get on a bike and mash down on the pedals at a knee-shattering 60 rpm. They think you have to work hard to make the bike go, or that you’re not exercising unless it’s hard work. It’s counterintuitive to a new rider, but selecting a very light gear that you can turn over easily is not only less effort and better aerobic exercise, but it’s also more efficient, and will save your knees, which harder efforts will damage.

So that’s the report on this year’s new toy. I’ll be curious to get more data from it over time, and particularly to see whether it provides me with useful information that will help me marshal my physical resources during longer rides.

Frequent topics