Analyitics

Showing posts with label Cross-Training. Show all posts
Showing posts with label Cross-Training. Show all posts

Monday, August 20, 2012

How Many Steps Do You Take?

My company is participating in the Global Corporate Challenge, a contest in which teams of seven are tracking the steps that they walk every day for a few months. Given that I develop corporate education for a large technology company, I am sitting at my computer or in meetings all day. The benefit of the program has been to open my eyes to how few steps I typically take on a day where I don't go for a run.

The surgeon general recommends that people walk 10,000 steps per day in order to stay healthy. This Livestrong article states that:
People who take fewer than 5,000 steps are considered to be sedentary or inactive. Those who take 5,000 to 7,499 steps daily have a low active lifestyle. Somewhat active people usually take 7,500 to 9,999 steps per day. People considered to be active take 10,000 or more steps per day.
I consider myself an active person, but on days I don't run, I might only walk 4,000 steps at most. If I take the dog for a walk, we're still only looking at 7-8 K. I honestly thought that I would be taking more steps than that! The eye-opening point - and i'm sure why corporations are supporting the program - is that walking the recommended amount of steps per day is difficult to do.

Now combine a running plan into it and things get much easier. It's hard to say how accurate the relatively inexpensive GCC pedometers are, but I've found that a good 4-5 mile run would be around 8,000 steps. On days with longer runs, I find myself racking up a good 30K steps by the time I ease into bed. Unfortunately, the GCC coinsided with my break from running while I healed up my knee from the Burlington Marathon, but once I started running regularly again I've been able to up my daily step average to just under 11,000 a day.

Does walking count as cross-training for running? I'm not sure that it would for a serious runner, but I've found it to be both helpful and relaxing. In addition, during my layoff I found walking to be low-impact enough to stay healthy but active and close enough to running that it helped me figure out how my knee was doing. I plan on continuing to walk as much as I can during the day, but also as and end in and of itself on days when i'm not running.  

Tuesday, October 18, 2011

the importance of cross-training

for specialized, well-trained athletes, cross-training may be counter-productive.  but for those of us who sit in a chair on a daily basis and grind out an honest day's work before we hit the less beaten path, or at least for ME, cross-training is as important as it is time consuming.

i say time consuming because other people may ONLY want to run (for example).  for them, anything that gets in the way of running, which is done in the precious commodity called "free time", is a bad thing.  i happen to really love cycling.  i've been cycling longer than i've been running.  the thing i think i like most about cycling is that i can do it for hours on end without feeling like i'm going to crumble into pieces.  i cannot do that on the run yet.  i'm training to be able to do that, but i'm not there.  but i think it's important, when training to do that on the run, to teach your body how to suffer for hours on end.

i've learned through unfortunate experience that you cannot simply go from someone who runs 5ks to someone who runs marathons.  instead of "you", i should say "i"...  maybe some people can do it, i cannot.  i think modern conventional wisdom indicates a 10% increase is about right per week for mileage, nothing more.  after a good first half of the year of training, i tried to ramp my mileage up more quickly than that.  now i sit and type more than i run due to injury.

reason number 1 why cross training is important to me:

when i cross-train, i get injured less.  during the years i was racing triathlons, i don't remember ever being injured.  i remember a lot of pain, a lot of soreness and lot of weeks when i decided to take it easy due to a feeling of being burnt out or physically wasted, but i didn't get injured to the point where i needed to stop for any significant amount of time.

the first half of this year, i cycled nearly as much as i ran.  i kept a pretty consistent running plan and cycled on the off days, sometimes cycling on days i ran (a "brick").  it wasn't until todd brought up the idea of doing a marathon that i started to focus on only running, ramping up the miles and staying away from the bike.  obviously, it's a combination of ramping miles and forgoing the cross training that led to injury (plus, i've been complaining about the calf for quite some time, so the seeds of this were already there).  but i do think if i kept more consistent about the cycling, i could have ramped the miles a bit faster (but still not as fast) and kept myself uninjured.

which leads me to the number 2 reason why cross training is important to me:

building a cardio-vascular base, a tolerance for pain and teaching your body how to burn fuel over the long "run".  i guess that's more like 3 reasons, but they all lead to the same thing...  preparing the body for going longer.  i've found that swimming is a very intense cardio-vascular workout and over the past few weeks of swimming, i feel like i've certainly maintained, if not improved my cardio by doing increasingly longer pool workouts.  i'm not a "pool runner", which seems a bit ridiculous to me, but a lap ticker... lap after lap of mind numbing crawl swimming.  the most significant jumps i made in increasing my pace (back in the day) came after i started adding serious swimming workouts to my routine.

out on the bike you go through periods of high-heart rate, lactic acid-injecting climbing followed by mellow downhills, with the grinding flats in between.  Massachusetts doesn't offer high mountains, but there are plenty of rolling hills to be found, plenty of climbing to be done.  it's a lot of little climbs, with a cumulative effect of crushing your legs and forcing them to recover quickly.  i think it's good to teach the legs to endure, produce, recover and then to do it all over again.

on a long ride, you also start to learn about the importance of nutrition and hydration.  this weekend, for example, i went out for a nice long ride where the bulk of my climbing was in the first half of the journey.  i felt great through all the climbs, good enough to push the pace a bit in the flats in between.  but when i got to flatter roads, i started to tank...  my body had burned up whatever fuel was left in the tank and needed more...  and it was very hard to take on calories.  my stomach didn't feel all that great, i had no appetite, but i managed to force down some food a bottle of water.  not long after that, i felt good again.  i think it's very good for the long run to teach your body that cycle.

maybe i'm just trying to find some way to be happy about my current non-running state of being...  but the more i bike and swim, the more i'm learning to trumpet these activities as crucial to my well being and preparation for running longer distances.  most importantly, i'm able to get out there and exercise...  and THAT is certainly something!!