Tag Archives: cycling

Training Tuesday: half-marathon now, triathlon soon

Time for a progress check-in on my training plans.

First, CHP. I am still delighted with the coaching I’m getting from Alex and the accomplishments and support of my fellow athletes is very motivating. For example, Dani Overcash, a 123lb woman, just set a new US record for deadlifting 402lbs at the RUM powerlifting meet this weekend. It is really cool to look in the FB group and see how many people are setting PRs, winning competitions (in powerlifting, strongman, Brazilian jiu-jitsu, and triathlon, among other sports), and generally being badasses.

Second, I started the Fleet Feet half-marathon program a few weeks ago. The program is pretty typical of half-marathon training programs: one long, slowish run on weekends, speed work one day a week, and a couple of shorter tempo runs. There are a few people in the program I know from the local running / triathlon community, which is fun. The long runs are Saturday mornings at 6am, which I semi-resent since that would otherwise be one of the few days when I don’t get up early. The program overall has a different vibe from TRI101, too, in part because of the different mix of coaches, and there have been a few hiccups with organization and logistics, but I am enjoying it and it should be good preparation for the Bridge Street half-marathon.

Third, I signed up for my first two triathlons of the season: the New Orleans Sprint on March 29 and the Lake Pflugerville Sprint in late June. There will undoubtedly be others in between (including the Issaquah Sprint, I hope!) Signing up was sort of a forcing function; I have been doing mostly weights and running, with occasional rides on the trainer, but I knew it was about time to switch to a more tri-focused regimen. I told Alex Sunday that I’d signed up and he immediately scheduled me for a brick Monday– and tomorrow I swim. Time to get back to it!

Fourth, I’m still debating which of the two local Olympic-distance training programs to sign up for. Note that I’m not debating whether or not I want a local group program. I do, because I like the energy and social connection of training with others. Fleet Feet is doing their TRI201 program, which I expect to be just like TRI101 with different distances, and local tri legend Rick Greif is doing his own program. Rick’s program is more expensive but includes some extras (including race registration for Renaissance Man), so I am leaning towards that.

I have a bunch more posts that I need to write, including an explanation of the setup I ended up with for bike training and a race report for the most excellent Tick Ridge Trek trail 10K I ran this past weekend, but this’ll do for now. See you on the road (or in the pool, or on the trail, or maybe at the pasta buffet!)

2 Comments

Filed under Fitness

Getting started with indoor bike training

A coworker was asking me about indoor cycling, so I took a few minutes to put together some notes on the configuration I use. He wanted a basic setup that would let him train indoors and minimize time spent away from his family. Here’s what I told him.

First, you should know that you can train in two ways: 

  • Structured workouts that target a particular power level (your functional threshold power, or FTP). An example workout is here. For example, you might ride a warmup for 10min at 60% of your FTP, then do interval sets of 80-115% FTP, then a cooldown.
  • Workouts where you ride for a set distance or duration while keeping your heart rate and/or pedal cadence in a certain range. These are akin to what you might do in a spin class, although a good instructor will provide a much more structured experience with intervals.

Both of these depend on having a way for something to measure how fast the pedals are going (cadence) and, optionally, your heart rate. Structured power-based workouts require you to have some way to either measure or estimate how much power you’re putting on the pedals.

Assuming you want to spend as little as possible, here’s what you need to get started with bike trainer workouts:

  1. A bike trainer. This DC Rainmaker article is the canonical list of recommendations for every price range. I got one of the Performance Bike TravelTrac units for about $100. I had borrowed a Kinetic Road Machine and loved it; it is much smoother than the TravelTrac but also costs 2x as much. 
  2. Speed and cadence sensors for your bike. There are two sensor protocols: ANT+ and Bluetooth Low Energy. You may be able to use BLE sensors with your phone and selected software, and it might work with your laptop, depending on what kind of gear you have. ANT+ is much more widely used for these sensors. I have a Wahoo ANT+ speed/cadence combo sensor but Garmin and several other companies make them. (Ignore the price at that link; sensors cost from $35-75 depending on brand).
  3. If you want structured workouts, TrainerRoad or some other training software. TR is $10/month, has a full money-back guarantee, and is very well worth it. TR will calculate what they call “virtual power” based on your pedal cadence, wheel speed, and the type of trainer you have. You will also need an ANT+ USB stick for your laptop so the TrainerRoad app can see your cadence and heart rate data. I use a $17 one from Amazon.
  4. If you want cadence / HR-based workouts, you need some way to see what your cadence and/or heart rate are. You can use a phone app for iOS or Android such as Strava or Wahoo Fit, the TrainerRoad app if you’ve subscribed, or a bike computer or watch that speaks ANT+. Beware that not every ANT+ device can display all types of sensors. For example, the Garmin Forerunner 15 running watch will display ANT+ heart rate data but ignores cycling sensors because it’s a running-only watch.
  5. If you want to gather heart rate data, you’ll need a heart rate monitor. I use the Scosche RHYTHM+ because a) it’s an arm/wrist strap and not a chest strap and b) it can transmit both BLE and ANT+.

There are lots of other ways to spend money on this stuff: there are computer-controlled trainers that adjust the resistance to give you realistic uphill and downhill rides, power meters that measure your power using strain gauges, bike computers that display your cadence, speed, etc. on a handlebar-mounted unit, and so on. But with the basic stuff above (which I’d estimate will cost less than $200 all in) you can get a terrific training experience without leaving your house.

Leave a comment

Filed under Fitness

Training Tuesday: a new bike and my first long bike ride

Wow, lots has happened since my last Training Tuesday entry. Maybe I should call it “Triathlon Tuesday,” since not every post is about training? But then again, not every post is about triathlon, either, as you’ll soon see.

I’d been wanting a new bike for some time. My previous ride, a Specialized Crosstrail Sport Disc, is a big, heavy beast of a bike. Its gearing is designed for trails; it has 3 chainrings (more on which later) with 9 gears in each. In addition, the frame geometry is such that you sit up straight and tall, which is fine for riding to work (the reason why I bought it) but not so great for riding fast in races or training. After my debacle at Rocketman, and my successful experience at Nation’s Tri with a rented Cannondale road bike, I knew I wanted to try to find a road bike before my last two races: Racin’ the Station and Rocketman Florida.

To save you lots of tedium, I’ll cut my description of the shopping process short. Suffice to say I did a ton of research, hit all the local bike shops, test rode a bunch of bikes, and spent an unhealthy amount of time looking at bikes on SearchTempest and eBay. The keys to finding the perfect bike are that you should pick a bike:

  • that fits you. This is a bit of a problem since I am tall. Bike geometry is complicated, so I quit trying to predict what would fit me in favor of riding bikes to see. how they felt
  • that’s in your price range. You can spend many thousands of dollars on super-fast racing bikes with all kinds of fancy crap, but that wouldn’t do me much good. To get faster, I need more time riding, not an uber-bike. All I wanted was a basic entry-level road bike, so I set a budget limit of $1000.
  • that you like. This was tricky. I saw lots of bikes that I liked that weren’t in my price range, and some that I liked and were in my price range didn’t fit me (including a really sweet all-carbon Douglas).

I pretty much struck out at the local bike shops. The model year for bikes changes over in August or September, so there were very few 2014 bikes in my size left, and most manufacturers hadn’t shipped many 2015 bikes in my size and price range. So I narrowed things down to a couple of 2014 models at two local shops– a Trek Madone 2.1 and a Cannondale CADD9–  and was planning on going to pick one out when I got back from Exchange Connections. In the meantime, though, a mechanic who works for one of the local shops told me about a sweet-sounding bike he had: a 2013 Giant Defy 1. It was in my price range, and I liked the idea of getting a slightly used bike for less than retail. We met Wednesday, I test-rode the bike for a few laps around the parking lot, and made the deal. Thus this picture from Wednesday night:

What a sexy beast! And the bike is nice too.

What a sexy beast! And the bike is nice too.

I didn’t get a chance to ride Thursday, but Friday afternoon after work I put on my SPD pedals and speed/cadence sensors and got in about a 2-mile ride. After a few tweaks to the seat position, I packed up the bike and went to bed. Saturday morning, I got up bright and early to meet Wendy (one of my Tri101 coaches), her husband, Teresa (another 101 alum), and her husband to convoy over to the All You Can Eat ride sponsored by the Spring City Cycling Club. I hadn’t really planned on riding this ride, but after I told Wendy that I bought the bike, she encouraged me to give it a shot. I decided to go for it. I only signed up the 34-mile loop, but I figured that would be plenty. The 50-, 67-, and 103-mile groups rolled out at 8am, and I joined them so I could ride with Wendy and Mike. The weather was absolutely perfect: mid-70s, with a nice breeze and plenty of sunshine. The first 6 miles or so were pretty slow, as we were riding in a big mob. However, about mile 7, there was a long downhill (with a sharp left at the bottom, yikes), and that spread the group out a good bit. I hit about 30mph downhill and could easily have gone faster if I weren’t so chicken!

Doesn't look like much from here…

Doesn’t look like much from here…

This ride was much different from what I’m used to. In triathlons, you’re not allowed to bunch up or draft, and everyone rides hell-for-leather. In this kind of ride, you can ride abreast, clump up, ride right of the centerline, and pretty much do what you want as long as you’re not unsafe. It was great to be able to ride along chatting with people, the more so because I actually knew some of the people I was talking to!

Another big difference: in this kind of ride, there are rest stops WITH FOOD. That’s right: we rode about 15 miles, stopped for a snack, rode another 8 miles, snacked again, and then rode about 9 miles to the finish. At the first stop, I had half a PB&J, a banana, a big cup of Gatorade, four or five Fig Newtons, and a brownie. Longer distances thus mean more snacks, giving you a built-in incentive to push your distance. As it was, 34 miles is about double my previous long ride distance, so that was enough pushing for me.

After rest stop 2, the ride went fine until we turned onto Salty Bottom Road (great name, huh?) The turn put us into the teeth of a stiff headwind, which slowed me down, and then I had to stop and walk up about half the hill around mile 32– I was just gassed at that point. I definitely felt the difference in chainrings on this hill; on the Crosstrail I would have just dropped to the lowest ring and blasted up the hill (well, OK, “blasted” probably isn’t the right verb). Having only 2 rings is going to take some getting used to.

The scenery was incredible: a hundred shades of green in the grass and fields, a squadron of planes overhead flying into Moontown for the EAA 190 pancake breakfast, and mountains, or at least what passes for mountains here, in the background. The course was very well marked and the support volunteers did a wonderful job of feeding us, providing a sag wagon, and handling all the pesky logistics.

This graph nicely summarizes the overall ride for me. The white line is elevation; the orange line is speed. The gaps indicate rest stops. You can clearly see the big downhill around mile 7 (look for the steep white cliff), plus a few later hills. My average speed was 14.3mph, which was pulled down by the long stretch of chat-riding  at the start. I was routinely hitting 20+ mph on the flats, something that would have been improbable, if not impossible, on the Crosstrail, so I’m really pleased with the results.

Tale of the tape

Tale of the tape

Now I need to log some more miles before Rocketman Orlando, which features a 32-mile bike course. On Sunday, I rode the Racin’ the Station course with a group, just to get a feel for it; I wasn’t pushing hard at all and averaged around 14.5mph. I need to get a few more rides in this week (along with RtS this Saturday). I’ll definitely be on the lookout for other sub-metric-century rides– I may have accidentally caught the club-ride bug!

Leave a comment

Filed under Fitness

Rocketman 2014: my epic fail

In idle conversation with my friend and fellow TRI101 attendee Alex, we started kicking around the idea of forming a relay team to do the Rocketman Olympic-distance triathlon. The Olympic distance is the next step up from sprints; it combines a 1500m swim, a 40Km bike ride, and a 10Km run. I figured I could do either the bike or run, but not both back-to-back, and I knew I didn’t want to attempt the swim… but Alex is a strong swimmer and he jumped at the chance. We recruited Ryan, another TRI101 member who runs ultradistance races, and we were all set.

In the weeks leading up to the Huntsville Sprint, I’d been thinking about buying a new bike. Instead of splurging I decided to rent one from Madison Cycles and give it a try for this race. I picked it up on Wednesday, but didn’t get to ride it until Friday, at which point it scared me badly! At nearly 10lbs lighter than my normal ride, and with much narrower tires, different geometry, and different gearing, it felt much less stable, and after my first ride my shoulders ached from gripping the handlebars so hard. On Saturday I rode it again and felt a lot better, though. I packed my stuff, attended the race brief with Alex and Ryan, and got to bed at a reasonable time. Sunday morning found me up at 0430 to finish my last-minute prep and drive out to the Arsenal’s recreation area, which abuts the Tennessee River. I’d signed up for a volunteer shift at the packet pickup booth, where I had a grand time visiting with friends and helping triathletes get their packets and swag for the race. The morning was cool and overcast, and as dawn broke I was excited about the race.

I met Alex and Ryan at the transition area, got everything set up, and headed over to the swim area. In a relay race, the swimmer starts with the timing chip and hands it to the cyclist in T1,  then the cyclist hands off to the runner in T2. Rocketman has a separate transition area for teams, which is handy.  Once Alex started the swim, Ryan and I hung out in the transition area until he came out, then I was out the chute and on the bike. By this time it had warmed up a bit, but it wasn’t too bad, and I felt great. Fresh breeze! Beautiful scenery! I’d violated my normal “nothing new on race day” rule and was sporting a Camelbak for hydration; I figured it, along with two water bottles on the bike, would keep me well hydrated.

The first mile of the course went by smoothly and quickly. I was keeping an eye on my pace because 40Km was about a third farther than my previous longest ride, and about half again as long as my previous longest race, but I was still feeling great as I rounded the turn near mile 2… and then suddenly it seemed like the bike was slowing down. I pedaled faster. This had no effect other than to rock me back and forth in the saddle. “Maybe I need to shift some more,” I thought. So I did, fiddling with the bike’s four shift levers in a fruitless effort to stop decelerating. Finally I had to unclip and pull over, where after some experimentation I found that the freewheel gear inside the rear hub had broken or something. Pedaling turned the crank, which moved the chain, which turned the rear cassette, which did nothing to the back wheel. I fiddled with it for another 10 minutes or so, to no avail; then I reluctantly turned the bike right side up and started the Walk of Shame back to the corral.

Along the way, I am happy to say, probably 4 out of 5 cyclists who passed by me asked me if I was OK. I appreciated their support a great deal, though they were moving too fast for me to do more than shout “THANKS!” at their rapidly receding backs. At one intersection, world-famous race photographer Gregg Gelmis was set up and captured the moment:

Me after my rental bike crapped out during Rocketman 2014

Me after my rental bike crapped out during Rocketman 2014

Thanks to my distinctive jersey (which I love, so shut up, haters), Alex and Ryan could see me before I made it back into the corral and they knew something was wrong. I am very grateful to them for how gracious they were; the mechanical failure of my bike meant that I officially did not finish (DNF’d) and so our team was marked as DNF’ing. Ryan ran the 10Km leg anyway and turned in an excellent time; while he was killing it in the 90-degree sun, Alex and I got to cheer a number of our TRI101 friends and coaches as they crossed the finish line. (Results are here if you want to see how fast everyone was.)

The Madison Cycles folks were very apologetic, and I’m sure they’ll settle up with me when I get back home. Mechanical issues happen. as anyone who’s owned any device more complex than a pencil knows well, so I don’t blame them, but it was still frustrated because I was excited to compete. I still had a great time; I especially enjoy the social aspect of triathlons because, while it’s a very competitive sport, the competitors tend to be very friendly and incredibly supportive. It’s a sport where you can take genuine pleasure in the successes of your friends, which suits me just fine.

The only thing to do: come back next year and DO THE WHOLE RACE. That will show ’em.

3 Comments

Filed under FAIL, Fitness

In which I become a repeat offender

Yesterday marked a milestone: my second triathlon, the Tarpon Tri in Houma, Louisiana. I was fooling around one day on TriFind and noticed that there was a race there, so I signed up– I thought it would be a fun trip to see family and visit my hometown again. But you know what they say: one triathlon and you can explain it away as harmless experimentation, or perhaps a temporary indiscretion… run TWO, though, and you’re a repeat offender, well on your way to “serial triathlete” status.

I’d planned to make the 359nm flight from Decatur to Houma on Friday afternoon, so after a great conference call with a potential new customer (more on that next week, I hope), I loaded up the plane. With the two rear seats removed, it was easy to fit my giant road bike, my tri bag, and backpack in; I parked the car and off I went. I’d like to say a lot of neat stuff about how interesting the flight was, but the fact is that it went flawlessly: no major weather, a smooth ride, and some really interesting scenery, including a beautiful crossing of Lake Ponchartrain right alongside the Causeway. After an easy landing, I headed to my hotel to drop off my stuff, plug in all my gadgets, and make plans to see family.

(Side note: I cannot possibly say enough good things about how well the folks at Butler Aviation took care of me. When I arrived, they had a rental vehicle ready because I’d emailed ahead– no mean feat since the nearest rental agency is 10 mi or so away.  When I got ready to come home, the plane was fueled and ready to go, and everyone there was super friendly. Highly recommended.)

Dinner Friday night was excellent: my Aunt Norma, my cousin Ricky, and his wife Tonya went to Dave’s Cajun Kitchen. The name gives it away, of course: it’s Cajun food, but the kind that people actually eat. Gumbo, fried catfish, white and red beans, jambalaya, and so on. I have never had a meal there that was less than excellent. This one was so good that I ate more than I should have, for which I would pay later.

After a visit back to Ricky’s, I headed to the hotel, got my gear ready for the morning, and went to sleep… then spent all night having reflux-y burps of white beans and catfish. Key learning #1: don’t eat so damn much before the next race.

Saturday morning I got up, hit Walgreen’s for some Tums, and headed to the race site for packet pickup. The place was packed! I should’ve gone to get my packet Friday night; after 20 minutes or so in line, I got my packet and chip, got body marked, and headed to set up in transition. Thanks to all the practice with the TRI101 coaches, I had no trouble getting my gear laid out, so I headed to the pool to get in a quick warmup.

This race had staggered pool starts: the fastest swim time was #1, the second-fastest was #2, and so on. If you didn’t put down a swim time, as I didn’t, you went to the back… so I ended up being #180, meaning that I had about a 35-minute wait to get in the water. Key learning #2: put down the right swim time. I had a very pleasant time visiting with the triathletes in line near me, including a multiple half-Ironman finisher and a guy who was running his first race to celebrate his birthday weekend (he didn’t say what birthday but he was no spring chicken!)

The swim went well– 150 yd in the pool in 3:57. Oddly, Movescount showed me with 125 yds (how? it gets its data from my watch, which showed 150 yds!), and the official time for the swim was 4:36:37. The info packet said:

The timing chips are all pre-set as to when they begin your time according to the seeding chart that we give to the timing guy. Please pay attention & listen to the volunteers who are starting you. They have a list of what time each participant is to start his/her swim.

That makes me wonder if for some reason the swim times were off based on the expected time at which I was supposed to get in the water. In any event, the swim felt good. I got through T1 in a leisurely 3 minutes, partly due to my decision to try my new USMC cycling jersey as racewear. Turns out putting on a clingy bike jersey when wet is really hard– and it reminds me of key learning #3: nothing new on race day. (For reference, the fastest T1 time in my age group was 19.9 seconds!) I also forgot to grab my race belt, which turned out to be OK because we were issued number stickers for our helmet, though at first I had paranoid visions of being DQ’d for not having a visible number.

The bike course was great: flat, hot, and sweaty, just like my first girlfriend. We got a steady light rain for about the first 25 minutes I was on the bike, so the pavement was a little damp but not unmanageable. The course runs right along the bayou, so there was lotsto see: egrets, various other birds, cypress trees, and the whole nine yards. There were plenty of volunteers along the course, great course markings on the pavement, and very little traffic. I averaged 15.6mph on the bike course, for a time of 38:28, which was a little frustrating because I thought I’d be faster. I didn’t take the time to mount my Suunto on the handlebars during transition, though, so I couldn’t easily see my cadence or pace. Next race I think I’ll mount the watch during setup and just go without in the pool.

Coming back in from the bike, I got through T2 in 1:02, then headed out for the run, which was also flat. The sun was powering through the clouds by this time, giving runners the sensation of being tucked snugly in Satan’s armpit. Luckily, the organizers had planned for this: there was a water station at the half-mile mark, then again at the turnaround. I spotted a roadside portatunity (that’s a porta-potty for those of you who don’t speak the lingo) and made an emergency diversion, then got back to it. I spent a few stretch breaks walking– more than I wanted to– but still finished the run in 31:51. During the run I noticed some pain on my chest; afterwards I found about a 1/4″ cut on my nipple! I have no idea how it got there, but I bet it was because of the new jersey and/or not using BodyGlide under my HRM strap. Ouch. Key learning #4: you can never have too much BodyGlide.

Overall, I came in 13th in my age group and 96th overall, with a total time of 1:19:00.2. I would have needed to pick up about 2min to move up to the next place. My goals were to finish and to be in the top half, so I was pretty pleased. Swag-wise, I got a nifty tech shirt, a coffee mug, and a can coozie, all of which I can add to my collection.

After the race, I took Ricky and his son Seth for a sightseeing flight. The ceilings at HUM were only about 3500′ and it was drizzling, but we did a couple laps around the pattern and overflew Gulf Island Fabrication, where Ricky works. This might have been the high point of the trip, because the two of them were so clearly enjoying it. I wanted to beat the weather heading north, so after I dropped them off I immediately took off to the north. There was heavy weather directly over the New Orleans airport, which I would have overflown, so I ended up diverting well to the west to get around it. As I worked my way further north, the ADS-B weather from my Stratus showed that there were storms all along my route from about Tuscaloosa north, so I landed at Demopolis to refuel and take a short break. After that, it was a simple matter to dodge a bit (as you can see below) by flying from Demopolis towards Courtland, then turning east once past the storms. Note that the magenta line shows the GPS track, not where I actually was; I had flown well to the west to clear the tail of the storm (the red blocks near the “6nm” label).

20140802_232620000_iOSKey learning #5: datalink weather is strategic, not tactical. It isn’t updated in real-time, so you can’t use it to thread through closely spaced storm cells. The weather was gorgeous when I got to Decatur, so I landed easily, put the plane away, and headed home– with another triathlon and another 7 or so flight hours under my belt. All in all, a great trip, even if I am on my way to a life of crime triathlons.

Leave a comment

Filed under aviation, Fitness

Training Tuesday: it’s all about finesse

[note: I meant to post this after TRI101 yesterday but got sidetracked with RAGE, for reasons which I’ll explain shortly.]

I’ve been super busy since my last Training Tuesday post with a variety of projects (new job means finishing up the old job’s work!), so I skipped a couple of weeks. I did, however, join Strava, so if you’re on there feel free to follow me.

TRI101 has continued to rock right along. Two weeks ago we did a timed mile (8:08, a new PR for me) plus about 2.5 miles worth of hill work; last week we did two 2-mile runs at Indian Creek, with some core work in between, and tonight we did a brick. I finally got back into the pool and am slowly cranking up my distance. You don’t get a lot of training benefit from just swimming super long distances without stopping; instead, the best advice I’ve seen is that you should swim for whatever the total time you expect in the race is. For example, if you swim 400m in 8 minutes, and you’re getting ready to swim a 1500m race, swim at least 3×400 with short rests and you’re good to go. I’m trying to work up to swimming 1000m in one session, even with rest breaks. That will cover me for any of the sprint-distance events I’m doing this year or next, and will give me a solid base for next season if I move up to Olympic distance races, which feature a 1500m swim.

My friend Rachel loaned me her Garmin heart rate strap, which, when paired with my Ambit 2s, gives me a good idea of how hard I’m working. It turns out that at my normal pace of between 8 and 8:30/mi, I am working pretty dang hard; my heart rate runs in the 140-160bpm zone. For my age, that’s nearly max effort. Interestingly, I don’t work nearly as hard on the bike as I do in the run. I think that means I’ve got a lot of potential speed improvement ahead on the bike if I can get my legs to cooperate; my cardio isn’t the limiting factor there. I think I’ve mastered the trick of getting the Ambit to correctly measure pool swims, too (you need a hard push off the wall when turning), so all my remaining races and training will hopefully be logged correctly.

NewImage

Maximal effort for great justice

Right now I’ve got two more races coming up: one in Houma week after next, then the Huntsville Sprint two weeks later. At this point I don’t feel like I have a lot of new stuff to learn; instead, I am trying to polish what I do know and focus on my technique. For example, my swim technique still needs some fine tuning; that’s still my biggest weak point, although the more I swim, the more confident I feel about it. The only way to get good at swimming is to swim, of course. On runs, I’m working in fartleks for speed. On the bike, I’m still working on not falling over when I unclip.

Although I’ve been trying not to make any more equipment changes, I finally got around to doing something I’d been planning for a while: I put road tires on my bike. Those of you who have seen my giant bike know that it had big knobby hybrid trail/road tires on it. I pulled those and put on a pair of Continental 28s. At yesterday’s workout I was killing it on the bike— my speed on the route (a loop around the Arsenal) was a good 3-4mph higher than normal, with no more effort expended. I felt great, right up until I dismounted and tried to switch my watch into transition without looking… resulting in erasing my workout altogether. I was roughly keeping pace with my pal Alex, so I know it was about 11.2 mi in just over 44 minutes, but I lost all the pace and HR data. By the time I got home, I was so mad that I didn’t feel like finishing this post, thus its appearance on Wednesday.

(The good news about the delay in posting is that I can sum up today’s swim lesson with Lisi: enlightening. Unlike running or riding, where my form is pretty natural and just needs a few tweaks, my swim form is poorly developed. It’s improving, for sure, but there are lots of little tweaks that Lisi has been able to point out. After my last session with her a few weeks ago, I’ve felt more at ease in the pool so I’m looking forward to working on the 3 things she identified for me today: earlier head rotation when breathing on the right, keeping my hips lower in the water, and being sure to get my full extension before I start the pull. She’s also given me some new drills and workouts that I will do twice a week; I think they’ll make a big difference.)

I’ve been trying to rest my left Achilles tendon a bit, so I skipped my regular long run last week and have been icing it at night. I think it’s about back to normal, so this week I’ll hit my long run, at least one long ride, and another swim or two. It didn’t bother me at all yesterday, though it was a bit tender after the bike/run brick last night.

What will all this polishing and tweaking lead to? There are a bunch of upcoming races in various places, and at various distances, so I’ll probably continue doing sprints until the end of the season and work in at least one 10K. It’s not too early for me to start thinking of what races I want to run next year, too. I found this article to be super helpful; this year I didn’t really have an A race, but I need to pick one for next year: probably an Olympic. I love poking around on trifind.com and looking at all the races, so this will be a lot of fun.

Fun note: I like to try to work races into my training schedule, so last weekend I flew up to Providence and ran the Craft Brew 5K with Julie and her friend Sigrid. This was a fun race, with a large emphasis on post-race beer drinking as opposed to record-smashing running. Despite that, I turned in a smoking time, at least for me: 2.9mi in 25:22, an 8:42 pace. The race chip time scored me at 25:18 and gave me an 8:08 pace, so I am thinking that the last-minute change to the race course shortened it a bit. The post-race beer tasting was fun, although the quality varied quite a bit. My favorite was Dragon’s Milk Bourbon Barrel Stout, for what that’s worth; I may have to lay in a post-race supply!

Leave a comment

Filed under Fitness

Today I am a (slow) TRIATHLETE: my first triathlon

Phew. What a race!

First, the setup. My sister Julie and her family live in Vermont. I was idly poking around trifind.com (yay for the “sort by date” option) and saw that there was a triathlon over the July 4th weekend in Shelburne, not far from her home in Montpelier. I had originally thought about running Tri for Old Glory in Huntsville, but the mountain biking portion of the course put me off a little bit. A Vermont triathlon sounded like a great excuse for a visit, so I registered and started making plans, which included buying a wetsuit, flying, and so on. The organizer’s pre-race mail described the course as “rolling and challenging – Vermont isn’t flat!” That worried me more than a little, since this particular race had a long bike leg and a 500m swim (longer than I’m used to) and it was my first wetsuit swim and my first open-water swim. Oh, and it was my first triathlon, period. So I was a little disconcerted by that message. Julie was kind enough to drive me over to Shelburne to take a look at the course. We found the swim entrance easily enough, but the race map provided by the course organizer didn’t seem to match what we were seeing on Julie’s in-dash GPS. As it turns out, what we drove was not the course, but I didn’t know that at the time, so I went to bed last night thinking “hey, those hills aren’t too bad.”

Pregame

Last night I ate a normal meal: steak salad (plus some extra steak), some guac, a Fourth of July-themed cupcake, and a Heady Topper. I went to bed at a reasonable time and woke up, for no good reason, at 3am. I managed to get back to sleep until about 330am, but after that it was game over. I finally got up at 445, showered, put on my tri suit, and hopped in the car with Julie. We got to the race staging site half an hour early (who knew there wouldn’t be any traffic?) so we headed back into Shelburne for a Dunkin’ Donuts coffee stop. Registration was quick and easy, and I got a good spot on the rack with plenty of time to set everything up.

WP 20140705 008

My setup in transition; note camera on handlebar mount

WP 20140705 013

Julie, acting as my pit crew (she was super helpful— thank you very much, J!)

The weather was cool and windy, as you could see from the video I shot if my balky computer would upload it. However, the scenery on the beach was gorgeous— mountains in the background, a nice variety of low clouds, and the water itself, complete with whitecaps.

WP 20140705 07 11 10 Panorama

a panorama of the lakeside pre-race

After posing for a few pre-race pictures, I got my wetsuit on and got ready for the warmup swim. Several of my TRI101 peeps had recommended taking a warmup swim before any open-water action, and I’m glad I did. The water wasn’t as cold as I expected, thanks to my wetsuit and earplugs. It was, however, choppy, but the course was set so that the longest leg was parallel to the shoreline, so we were swimming parallel to the waves too. The race marshal herded everyone out of the water and gave us a quick safety brief, during which he described the bike course thusly: “You’ll go under the railroad overpass, then get to the first big hill…”

Uh oh, I thought. We didn’t see a railroad overpass yesterday. Maybe we went on the wrong bike course… But at that point there was nothing I could do about it, so I joined the single-file line for the swim and marched down the boat ramp into Lake Champlain.

The swim

The swim started in a single wave. The water was no more than about 2’ deep where we started, so it was easy to wade out to the starting point. I deliberately hung back because I knew if I got in front, I’d get run over by faster swimmers. Laura, Rachel, and a bunch of my other TRI101 peeps had all advised me to just treat the swim as a fun outing, so I did.This proved to be a good decision. At the starting gun, we all started swimming: 100m out to the first buoy, a sharp right turn followed by a 300m leg parallel to the shore, another turn, and 100m back to the boat ramp. I was surprised at how good I felt during the swim, though I got a couple of snorts of lake water from poorly timed breathing. I didn’t have much of a sighting technique, in large part because I hadn’t practiced; shame on me. (I hope Lisi isn’t reading this!) The only negative to the swim was that the inbound leg got shallow really quickly so I had to wade in because it was too shallow for me to swim. This made my legs get wobbly in transition, but I still felt pretty fresh overall. I exited the water, dropped off my provided swim cap, unzipped my wetsuit on the run, and got into the chute.

DSC 2424

As far as you know, I’m up in the front

T1

Coach Rick was right: it’s hard to put socks on wet feet. It’s also hard to remove a wetsuit without a) looking like a stork or b) falling over. I chose option a). The TRI101 transition training was really helpful here, as I had already neatly laid out shoes, socks, helmet, and sunglasses so I could get everything together. However, my transition time was longer than I wanted. It didn’t help that the camera fell off the mount that Paul and I had attempted to repair the night before, so I had to pick it up, adding a little bit of time. Then I stupidly forgot to push the right button on my watch, so my transition time and bike leg measurements are a bit jacked up.

DSC 2442

Luckily I didn’t fall over

The bike

ACK. The course was indeed “challenging”.

Sure enough, after the initial outbound leg, I went under the railroad overpass and… damn, that’s a long hill. And double damn… there was another one after it. The course also featured a long downhill stretch where I set a new speed record on the bike (29.8 mph), plus a stretch with an epic crosswind, plus beach scenery. The whole thing was rough, mostly because I had been riding exclusively on the flats in Alabama. It didn’t help that I stopped a couple of times: on the outbound leg I noticed that my watch wasn’t giving me speed data, so I stopped to adjust the speed sensor, which had gotten knocked out of position. (The cadence sensor, which Paul helped me fix yesterday, performed flawlessly, so yay.) A few miles later I stopped to move my watch to my Cajun handlebar mount, and then later still a cyclist passing me said “your back wheel looks loose!” as he passed. Or maybe he said “That’s a big heel goose.” He was going faster than me so anything’s possible. To be on the safe side, I stopped and checked it too. For the record, it was not loose and there were no geese evident.

I went back later (in the car, of course) and took a video of the course that I hoped would illustrate the hills, but it doesn’t; it looks like driving in the car, so you can’t really see the badness. The route is on MapMyRide, if you use it. Here’s an elevation map that helps tell the tale. That big knuckle around the 3.16mi mark is the first big hill, and the one before the 9.47mi mark is the second one. I had to walk up the first hill on the second course loop, as my legs were just gassed. As I found out when the official results were posted, I finished last on the bike— a little embarrassing, but I finished the ride and that’s what counts. (Plus, since this race didn’t have any professional photographers there is no record of my facial expression on the hills, for which I am grateful!)

NewImage

T2

T2 was slick as maple syrup: I got in, parked the bike, put on my running shoes, strapped on my belt, and took off. It could have gone faster; I think my time was around 1:50, but I didn’t drop anything, fall over, swear audibly, or drop dead, so I consider it a success.

The run

The run was a simple out-and-back, with a little bit of elevation on the first leg (the same road as the first 1/2 mile of the bike course, in fact). I took an easy pace, with several walking breaks, but still managed to turn in a respectable time: just under 30 min for 3.0 miles. I drained both of the bottles in my race belt, though, because I had very little water on the bike. I froze my water bottle overnight because I figured that way I’d have plenty of cold water to drink. Sadly, the 3 hours between taking the bottle out of the freezer and trying to get my first drink was not enough to melt the ice, so I got periodic trickles of melted water on the bike but that was it.

Results: “Who you gonna believe, me or your lyin’ eyes?”

78th overall (out of 80). My goals for the race were a) finish and b) not be last.  These might not seem super ambitious, but I expected both the bike and swim to be harder than anything I had done to date. And I was right, so yay me! I ran the race at close to my normal training pace, which I thought was pretty good after the abusive bike ride, and I’m pleased with my performance in the swim.

Event Official result Paul’s watch
Openwater swim 14m20s 292yd, 10m53s
T1  — 3m49s
Cycling 1h13m 13.83mi, 1h11m
T2 1m50s
Run 32m49s 3.0mi, 29m49s

My struggle with the Ambit 2S continues. The results it gives me don’t always agree with what I expect, particularly in pool swims, but today represented a new low. I was careful to make sure that I had “triathlon” loaded as one of the two multisport activities, and I gave it plenty of time to get a GPS lock before the race. The race organizers claimed the swim distance was 500 yards, and the watch credited me with 292. It’s possible that the course buoys were, accidentally or on purpose, sited to make the course shorter, but it’s also possible that the watch just gets confused by swim distances. Once I can plug it in (I didn’t bring the sync cable, oops), I can look at the track it recorded and figure out where things went amiss.

Interestingly, they didn’t time transition separately. The swim was a gun start, and we didn’t have individual chips, but the bike had a chip tag and so did my run bib, so it seems like they should’ve been able to calculate the T2 time at least.

Important things I learned during and after the race

  1. Before you register for a triathlon, look carefully at the course map. This is the most important tip I can possibly give you.
  2. If you freeze your bike water bottle the night before, it might not thaw before the race starts and you will have nothing to drink on the bike.
  3. If you leave your glasses on your transition mat, the very nice lady next to you might stomp on them; if you are very lucky, your brother-in-law will fix them for you.
  4. The salted-caramel flavor of Gu is pretty decent, at least as energy gels go.
  5. The water in Lake Champlain tastes way better than the water in the Madison Wellness Center pool. It’s probably because of all the zebra mussels.

Executive summary

I am a triathlete. Suck it, Blerch!

DSC 2539

3 Comments

Filed under Fitness

Training Tuesday: and so it begins

Well, “begins” isn’t quite the right word; I’m 9 weeks into my 16-week training plan, but this week has a special milestone: my first triathlon is this coming Saturday. I am about equal parts nervous and excited. It’s my first-ever triathlon, my first open-water swim, and my first wetsuit swim. I have really low expectations, though: my goal is to finish, and, as long as I’m not last, the rest is gravy. I know I can do the swim distance, and the wetsuit should make it a little easier thanks to the added buoyancy. The bike distance isn’t a problem but the course is hilly. (Here’s the bike route, though you may not be able to see it if you’re not a MapMyRide member).

I have all the supplies and gear I’ll need, including a spiffy triathlon bag, although I want to get road tires today or tomorrow. Then it’s a matter of packing, for which I’ll carefully follow the checklist I made. I have TRI101 class tonight, and I’d like to get my long Thursday run in before I leave for Vermont, but I’ll wait and see how I feel; I definitely don’t want to overdo it. Perhaps a swim tomorrow would be nice, too. Tom is letting me borrow his Contour sports camera, so I hope to have some fun video from the trip (and, most importantly, the bike!)

Workouts this week:

  • Tuesday was transition training, which I already wrote about— lots of fun.
  • Wednesday I didn’t do anything.
  • Thursday I ran my first 5-miler! (well, 4.98 miles, but who’s counting?) Took me just over 51 minutes. If you look at the route map, you can see where we ran the HudsonAlpha helix— just look for the squiggly lines.
  • Friday I didn’t do anything.
  • Saturday we had our last group swim of the training season, featuring a drill known as “the washing machine”— you swim laps in two adjacent lanes, in a big swirl. Think of seeing people running laps around a track and you get the idea. Over 45 min or so I swam just over 900m, which is a new record for me. Some of that time was spent taking short breaks, though.
  • Sunday I didn’t do anything except eat.
  • Monday I rode with the Athens-Limestone posse— 26km in 1:11. That’s right, I voluntarily rode a bike in 91° heat for more than an hour. What the hell was I thinking?

Expect a Flying Friday post about the trip up to Vermont; that should be a fun adventure in and of itself. Now, I have to go put my USTA sticker on my car…

Leave a comment

Filed under Fitness

Training Tuesday: Transition Trouble edition

So tonight’s TRI101 class deserves its own post. Coach Rick had us practicing transitions; the coaching staff brought out the bike racks and we set up our bikes, shoes, etc. as we would in a race. When called, we were to run, barefoot, to our rack to simulate exiting the water for T1, put on shoes (and socks, if desired) and helmet, then move the bike to the mount line and ride 2 laps around a ~1mi loop. Then we were supposed to bring the bike back into transition, switch to our run gear (hello, T2!), and run the loop again. The goal was to do 3 complete circuits within 45 minutes. I didn’t quite make it— I got 3 bike laps and 2 runs before time expired. I did, however, learn several things I didn’t know, presented here for the edification of all:

  1. No one will stop you from exiting T2 for the run with your helmet on. You might want to remove it before running, though.
  2. Despite their cleats, bike shoes have little traction. If you get a good head of steam going downhill to the mount line, you may have difficulty stopping without falling on your butt.
  3. There’s only one way to hang your bike on the rack so that it doesn’t fall over.
  4. You (or at least I) can’t just jam your feet into your bike shoes because the heel area isn’t stiff; it’ll just mash down.

Despite these errors, I felt like I got the transition mechanics down OK, and both the ride and run felt pretty good (I averaged ~14mph on the bike and 6.5mph on the run). Oh, and my Cajun-rigged cadence sensor fix failed again, darn it. Onwards!

Leave a comment

Filed under Fitness

Training Tuesday: halfway through TRI101

So last week marked the halfway point in the Fleet Feet TRI101 program. I can definitely see a big difference in my overall fitness level, although (as I learned on Sunday in the gym) I am not nearly as strong as I was when I was lifting regularly. This is in part due to the garbage diet I’ve been following; too many carbs, not enough protein, and probably too much fat to boot. That’s one of the things I want to focus on in the upcoming weeks as I start reintegrating lifting into my workouts. The bricks we’ve been doing at TRI101 class have been really helpful, too, along with the many small tips and tricks that the more experienced athletes and coaches have been sharing.

I continue to be tempted by signing up for more races, but at the same time I’m growing more nervous: my first real tri is in less than two weeks, and it’s hard to judge whether I’m ready for it or not. On the other hand, my friend Dana just ran her first sprint tri and finished 2nd in her age group— so it proves that even your first race can go well. My goals for the Shelburne tri are to not burn up all my energy in the swim. The bike ride is a longer distance than any I’ve done so far, so I’d like to finish that at my same ~15mph pace, and then get the run done in under 35 minutes. We’ll see how that goes.

The past week’s workouts:

  • Tuesday we bricked as part of our weekly class: 34:46 for 8.45mi on the bike plus a weak, slow 15:01 to run 1.41mi. As a bonus, I split my forehead open in transition and had to go get stitches, so I couldn’t swim for a little while.
    WP 20140617 003Like my old man always said: it’s not a project until blood has been shed
  • Wednesday I met up with a group of triathletes for a brick south of the airport. Damn, it was hot. 55:01 for 12 miles on the bike plus a super short 8:15 run of 0.8 miles. For some reason I didn’t get any cadence data from this ride. The reason turned out to be simple: the magnet that the cadence sensor senses fell off somewhere. I replaced it with several Buckyballs, which I stuffed into the pedal hole on the crank; a piece of electrical tape holds them securely in place and now I get cadence data again.
  • Thursday I skipped my normal morning run— after a race last Saturday, a long ride Monday, and bricks Tuesday and Wednesday I was ready for a break. I took Friday off too.
  • Saturday I volunteered at the Monster Tri. It was great fun; I saw a bunch of my tri friends and got a close-up look at how transition is supposed to work. I also took a bunch of pictures, some of which were better than others.
  • Sunday I dragged myself to the pool and swam ~ 500yd. I still don’t think my watch is counting swim laps right. Then I carried my tired self over to the weight room and got a lift in for the first time in about two months. I felt weak but good when done, and the DOMS I had yesterday and today is a small price to pay (especially since my glutes and hams were already sore before I even got there.)
  • Monday I geared up and went to downtown Athens for the 15-mile beginner ride that a group of local cyclists holds… but the weather wasn’t cooperating.WP 20140623 002

    Not acceptable weather for instrument flight or VFR bicycling

    Rather than get hit by lightning, I elected to go home. I didn’t even get to test the sweet handlebar mount I made for my watch so I can see cadence and speed data on the go: a trip to Home Depot yielded a piece of pipe insulation that was just right for holding it. However, I am confident that it will work.

     WP 20140624 004Nothing like a little Cajun engineering

     

Right now I’m hoping that the weather will clear so I can go on to TRI101, where we have a workout cleverly named “Rick’s Special” after our lead coach– it’s a 2 mi bike + 1 mi run brick, repeated as many times as possible. Should be fun!

Leave a comment

Filed under Fitness

Training Tuesday: gearing up

It’s amazing how much crap you can buy for triathlon training. I already had running shoes and a bike; since then I’ve bought a watch, a cadence sensor, a wetsuit, goggles, a race hydration belt, and an assortment of other odds and ends. Yesterday I finally broke down and bought swim fins, a kick board, and a swim pacing timer— not because I need those for the race but because I need them for the drills my swim coach is giving me, and if I actually spend money on the gear I will feel obligated to do the drills. Commitment device FTW! In the same vein, since it was about 25% more expensive to buy a wetsuit than rent one, I bought one for my upcoming triathlon in Vermont… but now, having bought one, I feel like I need at least one more open-water tri to justify it. Candidates include the Lone Star Sprint in Galveston (which seems to have a permanently broken web site), the Frantic Frog in Scottsboro, the Tri-Rock in Austin, the Tawas Festival of Races, or maybe one of these.

I think I am done buying stuff for this tri season, unless I break or lose something— certainly not out of the question. I think I’d like a heart rate monitor but that’s just because I like looking at pretty graphs, not because I think it would help my training. At this point I need to stick to the plan, be a little more careful about what I eat, and start getting some actual races under my belt. More experienced cyclists have suggested changing the big semi-knobby hybrid tires on my bike for thinner road tires, and I might do that, but we’ll see how my first race or two goes. I figure I can always buy more crap later, but having more stuff isn’t going to make me go any faster or train any harder.

This week’s workouts:

  • Tuesday and Wednesday I was out of town and didn’t do anything.
  • Thursday I went back to Bridge Street for another group run. I felt really slow starting off, but in the end I ran 4.67 miles in about 47:25— a new distance record for me. (In fact it was a bit longer because my watch didn’t start timing when I thought it did). This was a real confidence boost, because if I can run that distance well that puts me in good position to complete a 10K. I’ll do better this week, too; at once point I stopped to walk because the group in front of me had run out of sight and I didn’t know where the planned route was, so I waited for the group behind me to catch up.
  • Friday I swam. Maybe 475m, maybe 500m, maybe 600m. It depends on which set of data from my watch you believe, as I wasn’t manually counting laps.
  • Saturday I ran the Alabama A&M Cross-Country 5K. I ran it in 31:59, which is certainly not great. The course features a good-sized hill, though, so that’s my excuse. I saw a ton of folks from my TRI101 class, which was cool, and it was a good workout. Plus each finisher got a hand-painted souvenir rock instead of Yet Another T-Shirt, so that was cool.
  • Sunday, I celebrated Fathers’ Day by not doing anything exercise-related. I did eat a steak, though, and I think that should count.
  • Monday I joined the local Kreme Delite group (so called because that’s where we ride from) and did 12.51 mi in 55:29. I got to the ride site a few minutes late, and the group had already left, so I blundered around trying to find the correct street for the route, then encountered another late rider along the way— so he and I rode the route, only to find a big group at the finish line. Note to self: be on time for next time.

On to the next!

1 Comment

Filed under Fitness

The difference between Suunto cadence and bike pods

I spent way too much time trying to figure this out today, so I’m blogging it in hopes that the intertubez will make it easy for future generations to find the answer to this question: what’s the difference between a cadence pod and a bike pod according to Suunto?

See, the Suunto Ambit series of watches can pair with a wide range of sensors that use the ANT+ standard. You can mix and match ANT+ devices from different manufacturers, so a Garmin sensor will work with a Suunto watch, or a Wahoo heart-rate belt will work with a Specialized bike computer. I wanted to get a speed and cadence sensor for my bike. These sensors measure two parameters: how fast you’re going and how rapidly you’re pedaling. (This is a great explanation of what these sensors really measure and how they work.) Ideally you want a nice, steady cadence of 75-90 rpm. I knew I had a variable cadence, and I wanted to measure it to get a sense for where I was at.

I ordered a Wahoo combined cadence/speed sensor from Amazon and installed it on the bike, which was pretty straightforward. Then I paired it with the watch using the “bike POD” option. (Suunto, for some reason, calls sensors “PODs”). That seemed to work fine, except that I wasn’t getting any cadence or speed data. But I knew the sensor was working because the watch paired with it. I tried changing the sensor battery, moving the sensor and its magnets around, and creating a new tracking activity that didn’t use GPS to see if I got speed data from the sensor. Then I thought “maybe it’s because I didn’t pair a cadence pod”, so I tried that, but no matter what I did, the watch refused to see the Wahoo sensor as a cadence sensor.

Here’s why: to Suunto, a “bike POD” is a combined speed/cadence sensor. A “cadence pod” is for cadence only. Like Bluetooth devices, each ANT+ device emits a profile that tells the host device what it is. That’s why the watch wouldn’t see the sensor, which reported itself as a combined cadence/speed unit, when I tried to pair a cadence pod. After I figured that out, I quit trying to pair the cadence pod… but I still didn’t get speed or cadence data.

The solution turned out to be simple. For some reason, in the cycling sport activity, the “Bike POD” sensor was unchecked, so the watch wasn’t reading its data stream during the activity. I don’t remember unchecking the box, but maybe I did. In any event, once I checked the “Bike POD” box and updated the watch, I immediately started getting cadence and speed data, so I set out for a ride.

NewImage

Hint: if you uncheck any of these boxes the watch will never, ever pay attention to that sensor

I thought it was a pretty good ride from a speed perspective, even though I took a new route that had a number of hills– I had some trouble with that. But look at my cadence… you can see that it definitely needs work. Sigh. One of the nifty things about Suunto’s web site is that it shows vertical speed when you point at cadence data, so I could see where I was struggling to get up hills (meaning I needed to change gears) or loafing when going downhill. Just one more thing to put on my to-fix list…

NewImage

36 Comments

Filed under Fitness, General Tech Stuff, HOWTO

Training Tuesday: slow progress is still progress

One of my fellow TRI101 participants shared this excellent article about building on your strengths in one event to bolster your weaknesses in another. I don’t really feel like I have any special strengths in running or cycling, other than “can complete required sprint distance.” But on reflection… that counts too. I definitely feel like my swimming is improving, though, and cycling the 10-15Km routes we use for training has been getting easier: an excellent sign that I need to go either farther or faster. The TRI101 program is scaled for participants who start at a low fitness level, but we are now at the beginning of week 6. If I stopped right now, I’m confident that I could finish a sprint triathlon, which is great news— now I just need to work on doing it faster.

The week’s training:

  • Thursday: 250m swim + swim drills. Slow, but better than nothing. I just wasn’t feeling it that day. As Karen, one of our coaches, pointed out, some days are better than others, and sometimes the best thing to do on a bad swim day is cut the distance short.
  • Friday: I swam 100m without stopping— a big deal for me, since I hadn’t been able to do that before— then 5 x 50m intervals, then another 100m. The intervals are 25m slow and 25m as fast as possible. It was a good workout, and I felt much better than I did after Thursday’s swim.
  • Saturday I did a short run/bike brick with a couple of classmates: 8.5 mi on the bike in 44:26 and 1.1mi running in 11:34. On the bike I spent a while riding slow circles waiting for all our party to catch up, so I didn’t take that time too out of sorts. I also went to the pre-race brief for the Mountain Deux aquathalon, which is this coming Saturday: a ~5Km trail run, followed by a 200m swim. Should be fun, except for the “trail run” part.
  • Sunday I swam with two TRI101 peeps: 100m warmup without stopping, 400m with minimal rest, then another 100m (which I did as 2×50, with the same 25m slow/25m fast). This was the first workout I logged with my new Suunto Ambit 2s triathlon watch.
  • Monday I had a bike fitting. That’s a topic for a post all on its own; look for it next week.

So, the watch. Anyone who knows me knows what a gadget nerd I am. I saw a mention on Facebook of a big watch sale mentioned at the DC Rainmaker blog, so I started poking around and was fascinated by the idea of a GPS-powered watch that could track my workouts for me— something I’d been using my phone for, with varying degrees of success. After reading his über-review, I decided to get an Ambit 2S. As much fun as it would be to have the barometric altimeter in the Ambit 2, it wasn’t worth the extra money. It arrived Saturday, and first thing Sunday morning I strapped it on and headed to the pool. Here was my reward: a more-or-less accurate record of my swim activity. I say “more or less” because I think it miscounted laps a couple of times, and the “total distance” column in the laps table doesn’t match the “distance” field at the top. I will be using it for cycling and running in the next couple of days and can get a better idea of how it works but I am most interested in the “multisport” mode for triathlons. I’ll be using that at Mountain Deux next week. The watch can pair with heart rate monitors, cycle sensors, and all sorts of other goodies that I will eventually add.

First swim

The upcoming week’s training should be good stuff— running tonight and Thursday, swimming Friday, and a bike/run brick Saturday. There’s a group that meets Thursday mornings to run a 4.5mi road course; I might join them to get a little distance in on the theory that if I can run 4.5 miles, it’s not that much of a stretch to run 6 miles, which means that I’d be in striking distance of running a 10K once triathlon season calms down some. On the down side, I also have a root canal Thursday (after running), so that may slow me down a bit. Hopefully I’ll bounce back in time for Mountain Deux on Saturday!

 

Leave a comment

Filed under Fitness, General Stuff