Tuesday Training, Trainers, and Trimming

It’s been a busy summer with travel of all kinds.  I haven’t spent a full week home since late May – so the next two weeks are my only opportunity to get in two solid – complete – and well structured training in.

And there’s no better way to do that than my typical Tuesday bike/run brick.

Now, I actually rather enjoy this Tuesday brick.  The schedule that Coach Alan puts together generally makes Tuesday-Thursday my hardest days of the week.  Sure, the long ride on Sunday takes hours longer, but the intensity isn’t to the same level as the back to back workouts mid-week.  This same concept is employed by other coaches as well.

Tonight’s workout included a relatively short – though intense – 34 minute bike, followed by a much longer 1-hour interval-ish run at higher intensities.

IMG_9462

The bike had the normal warm-up, and then a bit of a high cadence pyramid, before getting into sets of spin-ups to focus on even higher cadence.  Now, the goal of high cadence isn’t necessarily to race at higher cadence – but rather to instead reduce the HR impacts of higher cadence.  Meaning, by doing some (and not a ton) of training work, I can ensure that should I need to, I can easily spin much higher without taking a huge hit on my heart rate.  There’s ample evidence on both camps however with regards to time-trial style racing (which is what triathlon is) and exactly what an ideal cadence is.  So I won’t get into that debacle today.

But, I can say that I can spin-up like nobody’s business.  These repeating sets had me maintaining 170+RPM – yellow line is cadence.  Wootage!

image

After the high cadence stuff I transitioned back to a more normal 95RPM and then built up the wattage to bring my HR into a Z4B range over the course of the next 10-12 minutes.  This would end up being about 330w.

Right about the time that got uncomfortable, I spun easy for two minutes and headed out to run.

My run would start with an initial build to about a 10K race pace, before going into a number of 5-minute sets at 10K-ish race pace.  I was actually pacing on a heart rate, but the pace ended up in the slightly sub-6 range.  In between each set I’d have a lowered – but still moving along – heart rate to hit.  Oh, and speaking of HR – again, two flawless workouts with respect to no HR spike/dropouts using the combo Garmin/Polar solution I wrote about yesterday.  You can see the nice even/steady HR with no major jumpiness (except those sprints at the end which are just as painful as below indicates…):

image

Last but not least was some 200m sprints to finish off the day before going into a full cool-down.  All in the running portion lasted about an hour before I found my way back home.  I tend to do these on a looped course about a mile from my house, around a park.  This allows me to repeat each set with exactly the same course and be able to show re-producible sets of data.  Said more simply: I can see if I get slower or faster based on how far I get around the loop each time.

image[6]

I also bring along with me a water bottle and a gel bottle.  After running to the looped area, I toss it by some bushes and then hit it up every few loops.  Here’s me upon finishing the run.

IMG_9464

Once back home I noticed that my constant travelling this summer has meant that my front yard’s bushes had grown a bit…well, actually, a bit overgrown.  Kinda gone crazy really.

IMG_9470

Fearing that the Homeowners Association would soon be sending me nasty-grams I walked to my neighbor and asked to borrow a pair of clips (mine are mysteriously MIA).  He in turn gave me this amazing electric hedge trimmer.  Combined with some cycling gloves, I was in business! Within about 15 minutes my bush was looking quite pretty.

IMG_9474

And then…I was able to relax for the rest of the evening!

6 Comments

  1. I completely understand overgrown bushes. My entire yard is overgrown this year because of all my training and activities!

    Great job on the brick!

    Reply
  2. I noticed that there are gaps in the data on your first picture from the bike. I have this issue also with my Garmin 705. I heard this is a known Garmin issue, but do you have any insight to why this happens and if this will ever be addressed or if this happens with the 310xt and 500 also?

    Reply
  3. 170RPM - goodness, your pedaling is smooth!

    Reply
  4. After reading your first sentence, I thought you said "It's been a busy summer travelling with kids". Then again, I guess it's only a matter time. I'll be looking forward to how you figure out doing THAT already!

    Reply
  5. 170rpm... insane. I would be bouncing all over the bike.

    I love reading an engineer's blog. All about the numbers, charts, and reproducible numbers. That is the key. Nice job.

    Reply
  6. I just discovered Ben Brenman park today! I found it for the tot lot, but I can't wait to run it! Better yet that it is super close to my house!!

    Reply

Post a Comment

Your email address will not be published. Required fields are marked.
If you would like a profile picture, simply register at Gravatar, which works here on DCR and across the web.

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>