Long Overdue for an Update

It’s definitely been a while since I’ve posted any updates, but I’ll try my best to give a nice synopsis of the past two weeks of training. I’m still settling into my training regimen and trying to get accustomed to the new settings here in Charm City. During the past few years in Chicago, I never had to drive my bike anywhere to ride and I had two pools where I could do my swim training at any given time. Here, my options are more limited in some sense, but I’m hoping that it will make for a more successful season. Though I can only swim during Master’s practice times and I often have to drive at least 20min away for good riding, I’m getting more feedback about my swimming technique and hopefully riding up and over all the hills in the area will make me a stronger cyclist. Speaking of training, what does real world Ironman training actually entail? A typical training week for me looks something like this:

Day	Session 1 (am)	Session 2 (pm)
Monday		Master’s Swim
Tuesday	Patterson Park Loop Ride
Wednesday	Run	Master’s Swim
Thursday	Trainer Ride	Run
Friday	Rest
Saturday	Master’s Swim (early am)	Long Ride/Brick (late am)
Sunday	Long Run

In total, each week has 10 scheduled workouts and so far I’m averaging around 8. Since the first 8 weeks of my program are devoted to building a strong aerobic base, the majority of my workouts are done in Zone 2-3 with sets of short sprints or hill climbs for running and cycling respectively. I’ve been able to see some real fitness gains recently as running has become a bit easier and my heart rate isn’t climbing as high as it usually does at a given pace. Swimming is coming along slowly as usual, but that’s probably because I’ve yet to have a week where I’ve completed all 3 scheduled sessions. Even though the training intensity is mostly easy, I’ve noticed that the cycling hill intervals really wear me out. On Tuesday, I did 10 x 1 min climbs in Patterson Park and my legs were feeling really fatigued until Thursday morning. I’ve also noticed that it takes me about 10 seconds to fall asleep at night and I have no problem sleeping for 9 hours straight depending on when I go to bed. Speaking of bed, I guess I’ll wrap up this post and get ready for an early morning swim workout. Gotta stay streets ahead of the game.

Changing Lanes

One of the major differences between Chicago and Baltimore is that in Chicago, I had no worries about starting and finishing my cycling workouts from my front door. Well, at least the front door of my building as I haven't yet learned how to ride down 3 flights of stairs on aerobars. There were basically only two routes one could take when riding in the city: east to the lake and head north or east to the lake and head south. Even though Chicago lacked riding options and the terrain was mostly flat; riding was definitely convenient.

In Baltimore on the other hand, I have to drive to all the places where I would feel comfortable riding on the road. This presents a problem for weekday morning rides because I'm not a huge fan of losing sleep so that I can wake up early, install my bike rack, secure my bike, drive 20 minutes, ride for an hour or two, and do the whole process in reverse. However, the idea of doing all of my mid-week rides on a trainer is not appealing in the least, so today I decided to suck it up and drive to a "safe" spot.

Last week, while driving to a local park, I spent about 15 minutes driving down Pulaski Hwy. Surprisingly, the highway had wide shoulders and was marked as a bike route to some of the towns northeast of Baltimore. Although the road was extremely busy during the afternoon, I figured that it would be relatively quiet at 6:30am on a weekday. It turns out that this assumption proved only partially correct. The problem was that I had to ride far enough to get outside of the beltway (I-695) before the traffic died down and in the meantime, I had to make sure that I stayed as far to the right of the shoulder as possible. As a aside to any city planners who might happen upon this post, if you have a bike route that bypasses one or multiple interstate on-ramps, build a bridge or underpass or specify a detour so that cyclists don't have to play Frogger with cars, trucks, and semis driving along at 50 mph. Anyway, once I made my way outside of the beltway, the ride was great. Nice rolling hills that required use of most of my gears (a nice change from Chicago) and not too much traffic.


View Larger Map

All in all, it was a good experience and I will now suck it up and spend the extra 5-10 minutes to park outside of the beltway before hopping on my bike.

Off the Chain

So my plan for today was simple. Wake up bright and early at 5:00am, eat breakfast, go to swim practice, and then join the group ride leaving from Tri-Speed. If everything went according to plan, I would have enjoyed about 3 hours of training while also earning my post-workout, pancake breakfast. Steps 1 and 2  went smoothly, though I woke up about 7 different times last night, so it was off to swim practice.

Unlike Wednesday's swim, I joined the group at Meadowbrook this morning. They have a nice 6 lane, 50m indoor pool and in the summer, they open a massive 10-lane outdoor pool as well. Today's swim was mostly composed of varying sets of 300's for a total of about 2400 yds. I guess things went well for about half of the workout, but as is typically the case, I was seriously getting dropped near the end. Fortunately, I was able to hold on until our hour was up, so with my swim in the books and a bagel and some Gatorade in my stomach, I went to meet my new-found riding group.

This would be my first real ride since I've been to Baltimore, so I was really looking forward to riding on the quiet country roads in Baltimore county that I've heard so much about. The ride began on time and I quickly realized that a tri-bike is not the best for riding in these parts. Unlike Chicago, where everything is pancake flat, the roads here are more like a rollercoaster. I hear that Louisville has a similar terrain, so I guess this will be the proper place to prepare for the big day in August. I was able to stick with the group for the lesiurely beginning of the ride, but once we hit the first hill, my bike had a surprise in store for me.

I initially tried to stay seated at the bottom of the hill, but as I started to get dropped, I decided to stand and apply some power. Three pedal strokes later, I heard a loud pop and I thought that I had simply dropped my chain. Instead, I looked down to see that my chain had snapped and looked something like the picture below.

Though most of the group was already pulling away before my chain snapped, Mike from Tri-Speed stayed behind to help. Unfortunately, neither of us had a chain tool, so I was stuck about 10 miles from my car with a useless bike. Mike, however, was generous enough to ride the 30 minutes back to the store, and drive back out to pick me up (Thanks Mike!). Since my chain failed near the top of the hill, I was able to coast back nearly a mile so that Mike wouldn't have to drive quite as far to pick me up. After about 45 min, Mike made it back and we were able to install a new chain at the store. Woo hoo!

Moral of the story: Always be prepared.

Oh, and I ate a bowl of cereal when I got home. The 30 minutes of riding wasn't really deserving of a pancake breakfast. Maybe next time.