Giving myself a “B” on a “C+” ride

It has arrived: the time of year that I run less and less, because I’m pedaling more and more. It’s bike time! This year, “bike time” was kicked off with New Bike Day, and then got delayed by travel, weather and other obligations. Since completing my first century last fall, my goal was to ride three centuries this season — so as fun as some of the delays were, I’ve been eager to get back on the bike regularly and start putting some miles under my shiny new tires.


My cycling club holds organized group rides every night of the week. We try to drum up enough ride leaders that each site can launch rides at multiple paces, and a few of our weeknight rides have enough riders and ride leaders that they can break down one pace into multiple groups. For me, riding with the group is an essential part of my training plan — I enjoy the social aspect of group rides and I feel like I push myself harder when I’m challenged by other, faster riders. When I ride on my own, I tend to be a little more conservative with my pacing.


Paces are assigned letters, based on average speed for the ride. “A” is our fastest pace group, averaging somewhere around 18-20 miles over longer distances and more challenging terrain; our Monday night club ride hosts paces from “A” to “D”, which is a group that rides at an average of 8-10 mph– geared toward new riders and those riding heavier bikes, like hybrids. To make it a little more complex, we get enough riders at the Monday night ride that some of our regular pace groups are broken down further — for example, we don’t just have one “C” pace group; we have “C+”, “C” and “C-“. The purpose here is just to break the groups up a little — rather than having a large “C” group with 30 or more riders strung out on the roads, we can have three smaller groups, with riders able to more consistently stay together, heading out on different routes. It helps manage group size so that we aren’t contributing to congestion on local roads, at the same time as making sure it’s easier for the groups to stay together at a steady pace.

Last summer, I rode consistently with the C pace group, and had a great time. The ride leader, Denise, and sweep rider, Mike, are both great at leading and supporting riders, and the group that turned out weekly was a nice mix of people — so not only was the ride good, but the people were nice to ride with, and that’s about as good as it gets if you’re a social rider like me.


However, by the end of last season, I was starting to feel like I needed to bump myself up to the “C+” group. The rides were starting to feel easier — and, while there’s nothing wrong with just enjoying a ride, I tend to feel that urge to push myself a little harder when things start getting easier.


This year, both the weather and my own scheduling conflicts have conspired to delay my Monday night rides, and last night was the first time I got out to my favorite group ride. I signed myself up on the C+ sign-in sheet, introduced myself to the other riders gathered there, and convinced myself not to bail on the whole idea when the ride leader rolled up and said, “Hope everyone’s ready for a hilly ride tonight. We’re hitting some big ones!” I started having my doubts about bumping up to a faster-paced group, but there were a couple other people second-guessing their pace choice after that announcement, so I figured it was more likely that there would be a few of us trailing behind the group instead of just me, off the back, all by my lonesome.


It turned out to be another good group of riders and a great night on the bike! We did hit some challenging hills, and I did better than expected. I felt like I was close to getting dropped on some of the early hills, but I also had no problem reeling the group back in after we crested — and, as the ride went on and the miles racked up, the group wasn’t attacking the hills as hard as they did at the beginning — but I was, and I started passing people on climbs. (They almost immediately passed me on the next downhill, but perhaps my timid descending is a topic for another post!)


Before the ride started, I set myself a goal: don’t be the last straggler coming back into the parking lot. At the end, I was right on the ride leader’s wheel; we got passed by a couple people who were giving it all they had on the final, flat stretch of road, but I came into the parking lot with the bulk of the group, rather than behind. Since I rode pretty steadily, stayed with the group and felt good at the end, I give myself a “B” grade (not a “B” pace!) on the C+ ride.


Below is a screencap of my pace and the elevation, as provided by my Garmin.





Race Report: Tyler 10k

My trail running group occasionally runs in Ridley Creek State Park, which butts up against Tyler Arboretum — a few of the trails cross onto the arboretum property, and at least a couple of us have signed up for memberships at the arboretum (I felt bad for trespassing the first time I followed the group through a deer gate into the arboretum property, so I signed up for an annual membership afterward. Plus, it’s a beautiful place with many good programs, so supporting it makes me happy).

Each year, the arboretum hosts a 10k trail race, which is capped at 400 runners and sells out every year. I ran it last year for the first time, and hadn’t done much in the way of trail running (mostly flat, local dirt or gravel trails) prior to the race– that’s a big part of what led me to increasing my time on the trails this past year. I had so much fun at the race that I wanted to come back again and do better.

Race Overview:

The trails in Tyler are really lovely — wide, well-maintained, minimal rocks and roots to worry about (somehow, when I run next door in Ridley Creek State Park, roots and loose rocks seem to magically multiply where-ever I’m about to put a foot down. Does fencing out deer work on rocks, too?) It’s hilly enough to be challenging, but not painfully steep. There are two spots where the trail crosses a stream — and the race course loops back on itself, so you get four total stream crossings. One spot has rocks across the stream, so you can keep your feet dry if you want to balance your way across, or you can just splash through above the rocks. The other stream crossing didn’t have any handy rocks, but it was narrower and pretty shallow — maybe 6″ deep. (I got both feet wet, while my long-legged boyfriend was able to leap it in a single bound.)

Even with the rain leading up to the race this year, there were very few muddy spots on the trail. The trail surface was nice and firm in most areas, with just a couple low spots that actually had good ol’ squelchy, slippery mud.

Of all the hills on the course, the meanest one is at the finish. Not because it’s the steepest, but because you have to bypass the nice, flat area where the start line was set up, then run down a slight hill, cross a bridge over the stream and then run up a wide, grassy slope to finish next to the barn. Last year, this hill was a surprise — I hadn’t been looking around enough to notice that the finish line was not in the same place as the start line, and I sped up too early. This year, I was ready for it.

The general atmosphere of the race is really nice — from the volunteers at check-in to the folks directing you out on course, everyone is positive and encouraging. The folks at the water stations were great, as were the volunteers directing people at intersections and encouraging runners at each of the water crossings (I even saw one guy lending a balancing hand to a runner carefully picking her way across). Since the course does loop back on itself, you eventually reach a point where you’re seeing the head of the pack coming back, and all the runners cheer for each other, too. I got a “Good job, runner!” comment from someone who was somewhere in the top 10 runners, which was cool. (The overall winner finished the course in just over 36 minutes. My mind was BLOWN when I heard that. I can’t even imagine what it must be like to be that fast!)


My personal race experience:

The forecast for the day included sun and a high temperature of 60 degrees. The morning temperature was expected to be around 48 degrees, climbing pretty quickly to the mid-50’s. I planned my outfit accordingly: lightweight running capris (I kind of hate shorts, and never wear them), and a light-weight, long-sleeve shirt. When I woke up that morning, I was freezing — I just felt really cold from the moment I woke up, and it felt colder than mid-40’s to me when I first stepped outside. My boyfriend also reminded me that, when we got to the park last year for this race, we discovered it was quite a bit colder there. Another running friend confirmed it was “usually” 10 degrees cooler in the park. I second-guessed my clothing choices, and swapped in my Brooks insulated running tights, and a long-sleeve base layer with a light t-shirt over it. I also threw on a lightweight pair of gloves and a headband to cover my ears. Mistake #1 complete! I was relatively comfortable walking around before the race started, and that should have been a blinking neon warning sign that I was wearing the wrong clothing. In hindsight, while it was too late to change pants before the race started, I could have gone back to my car and gotten rid of the long-sleeve base layer — that would have helped. As it was, I kept all that clothing on and ended up over-heating and not feeling well for most of the race. (I did end up taking off the gloves and headband about a mile into the race, and rolled up the sleeves of my base layer, but I stopped short of stripping off clothing so that I could remove the base layer and just have the t-shirt on.)

I was pretty frustrated over that newbie-style mistake — how many seasons do I have to make the same clothing mistakes before I learn to trust the temperature/weather guidelines instead of my instincts — but that wasn’t the only newbie mistake I made on Saturday. The other one? Not retying my shoes.

No, I’m not joking. At one point, just after the race started, I thought that my left shoe was a tiny bit loose, and maybe I should re-tie the laces. But we were in the thick of the crowd, and I didn’t want to end up all the way at the back of the crowd before we hit the natural bottleneck of the first stream crossing, so I kept going. Were there better places along the way, after the crowd was more spread out on the trail, where I could have stepped off to the side to redo those laces? Yes, there were. Did I do that? No, I did not. By the time the crowd thinned, I was moving along at a good, comfortable pace, focused on running the trail, and completely forgot about my shoe. I twisted my left ankle three or four different times in the first four miles, and I remember glancing at my Garmin to check the distance, seeing 4.19 miles and thinking, “I am going to be walking the last 2.01 miles. THIS SUCKS.” At this point, my boyfriend had dropped back to run with me, and I had to turn my face away from him — I was struggling not to cry. My ankle hurt every time I put my foot down, I was feeling a little nauseous from being overheated, and I was angry with myself for not doing better.

And that’s when I remembered that I had thought, early on, about retying my shoe. I stepped off the trail right then and did it, figuring at least the bit of extra support might help mitigate the pain of my ankle, even if I still had to walk the rest of the way. I was surprised at just what a big difference it made, and was able to pick up the pace again and continue run/walk intervals the remainder of the distance. (To the rhythm of, “IF ONLY YOU HAD DONE THAT TO BEGIN WITH, YOU IDIOT” in the back of my mind.)

With my ankle feeling a little better, and my boyfriend running with me, my spirits picked up considerably. I crossed the finish line to the cheers of a friend who had finished ahead of me, then stayed there to cheer for two other friends (and everyone else who came up the hill to the finish line). Finishing a race at a run instead of a walk is pretty much all it takes to put me back into a good mood, no matter how rough the race itself was, and I can look at any difficulty I had or mistakes I made from a better mindset and move on to the next challenge.

Now that I’ve run the race twice, next year might be my turn to volunteer. Not because I don’t want to run it again, but because I know how hard it can be to find volunteers for an event — and it doesn’t matter how many people register if you can’t wrangle enough volunteers to support them!