While at the gym on Tuesday, I contemplated the treadmill. Actually, it wasn't much contemplating as it was wondering. I wondered when I'd get on it again, and if getting on it sooner would be better than later.
Of course, that was before my great workout. Now, I feel comfortable staying on the bike.
But there will come a time when I have to run again, and when I do will I be prepared?
I came across this article on runnersworld.com that talks about getting back into running shape after a prolonged layoff. It doesn't go into detail about how many days constitutes a prolonged layoff, but after having run for so long, 10 days to me seems rather prolonged.
The story suggests to start with some light running to begin with. So a two-minute run followed by a two-minute walk would suffice. Then, add minutes to each run and pretty soon you'll be, well, off and running.
This was actually a bit of my plan. I had planned to run intervals the next time I hit the treadmill. The only problem was my first interval segment was a full 12 minutes of running and asking my body to do that seems like it would be a jolt to the system. I suppose biking hard for a few days or weeks would help alleviate whatever stress may be caused by such a run, but mentally it could still be a struggle.
I plan on resting on Wednesday before hitting the gym again on Thursday and possibly Friday. Both days probably will mirror today, with a bike segment followed by some time on the elliptical. Running will subside, for now.
Actually, until next week. I'll shortly begin a new type of running workout, one that will involve more than a treadmill. What is it? Well, I'll save the topic for another post since I'll need some time and energy to get me through it - the post as well as the endeavor.
Showing posts with label cardio. Show all posts
Showing posts with label cardio. Show all posts
Wednesday, November 19, 2008
Tuesday, November 18, 2008
What a difference .01 makes
On Monday, I returned to the gym and biked for 45 minutes. I did 16.20 miles and it was overall an average workout. Today, I got on the same bike, set the timer for the same 45 minutes and in the end wound up with a distance of 16.21.
But today's workout was infinitesimally better. Night and day. Apples and oranges. Water and oil... well, you get the point.
Not only did I feel exhausted after I was done, I felt like I'd just completed a challenging workout. Yesterday, I felt like I'd spun the wheels on the bike for 45 minutes.
I had a better mindframe, better mentality today. I focused before getting on the bike and was ready to face whatever challenges I had. For the first 10 minutes or so it was about the same but I made it a goal to push my heart rate as high as I possibly could. On the bike, though, I'm limited. My thighs can only handle so much before they start to burn and threaten to tear off my pelvis so I can only really push myself for a few minutes at a time.
But for those few minutes it made a world of difference. I started to challenge myself in two- or three-minute increments. I rose the bike's level from a seven or eight up to a 10, which for me is challenging. Hopefully if I get a bike and start to exercise using a bike I'll be able to handle more and ride longer distances at a higher level.
Anyway, that worked. My heart rate climbed immediately once I put on the higher pressure. It went from the high 130s into the 140s and eventually into the 150s. When my thighs started to shout, I slowed down. I did this multiple times during the bike ride and once my 45 minutes were up, I was exhausted.
Well, a little bit. I was tired of sitting so I jumped on the elliptical for about 15 minutes to round out the workout.
Here are the heart rate stats
(bike) time: 45:00, Avg hr 140, Max hr 164, Cal 532
(elliptical) time: 15:14, Avg hr 150, Max hr 160, Cal 201
I was able to maintain a higher average on the elliptical because of my bike workout. I think I may be able to adjust the times on both the bike and elliptical to have a more well-rounded workout.
More importantly, there's hope. I can start to challenge myself on these machines that I felt were not challenging enough as I take a break from distance running. And that alone makes the extra .01 worth every bit of energy I expelled to attain it.
But today's workout was infinitesimally better. Night and day. Apples and oranges. Water and oil... well, you get the point.
Not only did I feel exhausted after I was done, I felt like I'd just completed a challenging workout. Yesterday, I felt like I'd spun the wheels on the bike for 45 minutes.
I had a better mindframe, better mentality today. I focused before getting on the bike and was ready to face whatever challenges I had. For the first 10 minutes or so it was about the same but I made it a goal to push my heart rate as high as I possibly could. On the bike, though, I'm limited. My thighs can only handle so much before they start to burn and threaten to tear off my pelvis so I can only really push myself for a few minutes at a time.
But for those few minutes it made a world of difference. I started to challenge myself in two- or three-minute increments. I rose the bike's level from a seven or eight up to a 10, which for me is challenging. Hopefully if I get a bike and start to exercise using a bike I'll be able to handle more and ride longer distances at a higher level.
Anyway, that worked. My heart rate climbed immediately once I put on the higher pressure. It went from the high 130s into the 140s and eventually into the 150s. When my thighs started to shout, I slowed down. I did this multiple times during the bike ride and once my 45 minutes were up, I was exhausted.
Well, a little bit. I was tired of sitting so I jumped on the elliptical for about 15 minutes to round out the workout.
Here are the heart rate stats
(bike) time: 45:00, Avg hr 140, Max hr 164, Cal 532
(elliptical) time: 15:14, Avg hr 150, Max hr 160, Cal 201
I was able to maintain a higher average on the elliptical because of my bike workout. I think I may be able to adjust the times on both the bike and elliptical to have a more well-rounded workout.
More importantly, there's hope. I can start to challenge myself on these machines that I felt were not challenging enough as I take a break from distance running. And that alone makes the extra .01 worth every bit of energy I expelled to attain it.
Monday, November 17, 2008
Back to the grind
Properly motivated, well rested and with loads of energy, I made it out to the gym on Monday. And it was a good workout as I rode for 45 minutes and even got in a brief bit of weigh training.
So I was happy with how the day went then, right?
Sort of.
I hadn't intended to run or work out pretty hard. In fact, I'd intended for an easy workout, something that would help get me back into the rhythm of working out, both mentally and physically. It had been a week since I last did any sort of physical activity, when I ran the Mission Inn Run 10K.
Did Monday's workout meet my goals? Yes, but those goals weren't ones that I would normally hold for myself. I suppose then that's why I feel satisfied that I worked out but not exactly feeling great over a killer workout.
Perhaps the problem is in my expectations and not so much the workout itself. Every time I go to the gym, I try and challenge myself and while Monday's workout was a challenge in and of itself, it wasn't of the usual I'm-going-to-push-my-body-to-the-limits kind. I wanted to ride the bike for 45 minutes, I did and that's that.
Here are some stats to prove how merely satisfying my workout was:
Time 45:00; Avg Hr 135; Max Hr 160; Cal 525
Compare that to my Mission Inn Run
Time: 52:30; Avg Hr 182; Max Hr 192; Cal 989
Okay, maybe that comparison is a bit unfair. After all, running a 10K is supposed to be challenging, far more challenging than the typical gym workout. But still, when I run my heart rate is typically more than 160 and sometimes is in the 170 range. So when I work out and I only get as high as 160, it's natural to feel it as a bit of a letdown.
Again, it's all about expectations. I expected myself to have a recovery-type of workout and I did, so I need to feel satisfied. My normal expectations are quite higher so I just have to adjust them sometimes to meet my specific demands.
Because I can't run a 10K every day.
So I was happy with how the day went then, right?
Sort of.
I hadn't intended to run or work out pretty hard. In fact, I'd intended for an easy workout, something that would help get me back into the rhythm of working out, both mentally and physically. It had been a week since I last did any sort of physical activity, when I ran the Mission Inn Run 10K.
Did Monday's workout meet my goals? Yes, but those goals weren't ones that I would normally hold for myself. I suppose then that's why I feel satisfied that I worked out but not exactly feeling great over a killer workout.
Perhaps the problem is in my expectations and not so much the workout itself. Every time I go to the gym, I try and challenge myself and while Monday's workout was a challenge in and of itself, it wasn't of the usual I'm-going-to-push-my-body-to-the-limits kind. I wanted to ride the bike for 45 minutes, I did and that's that.
Here are some stats to prove how merely satisfying my workout was:
Time 45:00; Avg Hr 135; Max Hr 160; Cal 525
Compare that to my Mission Inn Run
Time: 52:30; Avg Hr 182; Max Hr 192; Cal 989
Okay, maybe that comparison is a bit unfair. After all, running a 10K is supposed to be challenging, far more challenging than the typical gym workout. But still, when I run my heart rate is typically more than 160 and sometimes is in the 170 range. So when I work out and I only get as high as 160, it's natural to feel it as a bit of a letdown.
Again, it's all about expectations. I expected myself to have a recovery-type of workout and I did, so I need to feel satisfied. My normal expectations are quite higher so I just have to adjust them sometimes to meet my specific demands.
Because I can't run a 10K every day.
Friday, October 24, 2008
Lucky seven
I didn't intend to run seven miles today. I was meaning to run six miles when I first stepped on the treadmill. Somewhere early in my run, I decided to go 6.2 in order to simulate a 10K. As it turned out, though, I went a long distance. And I felt pretty good.
On Saturday, of course, I ran the Mud Run, all of 10 kilometers. I've got the Mission Inn Run coming up in two weeks now but having trained and prepared for the Mud Run has also made me primed to run this upcoming 10K. If it were this Sunday instead of two weeks from Sunday, I would be confident that I would not only finish the 10K but do so in a good time, in what I consider a good time for myself, anyway.
I think overall though the run wasn't as challenging as it could have been. Yes, running seven miles is a daunting task. However, my heart rate rose fairly steadily throughout the last three miles; actually, to be more precise it was almost stagnant for 20 minutes or so.
I suppose I should take that as a good sign. If and when I run a half marathon or even a 10-mile run, I'm fairly confident now that I will be able to reach the 10-mile mark without maxing out my heart. In other words, I will have quite a bit left in the tank for miles 10, 11, 12 and 13. Running intervals and changing speeds has become ingrained in me so if I run for even a half-mile at one speed I feel like I'm not doing it right.
Somewhere around the 4-mile mark, I decided to keep the speed at 7.0. I started slowly, at a 6.0, and then increased my speed to 6.5 near the mile mark, 6.8 shortly after that and a 7.3 for the third mile. I had intended to go down to a 6.5 for mile 4, up to 7.3-7.7 for mile 5 and finish off with 6.8 for mile 6. Instead, at mile 4 I wanted to stay at a 7.0. I think that's the pace I'm most comfortable at right now.
I realized that I needed to get to 6.2, not just 6.0, so I had it in my mind that I needed to get over six miles. I felt the twinge from inside, the seven-mile itch you can call it, asking me to run that seventh mile. I was debating whether or not to go through with it when I asked myself "Come on, how often are you here?" By here, I meant not the gym but rather the distance. "Here" was in the sixth mile of a six-mile run but, more importantly, I felt good about myself. My heart rate was where it needed to be, my mental makeup was also fine even though my iPod gave out at about the 17-minute mark and I wasn't in a hurry to leave the gym.
I ended up completing seven miles in about 62:42 or so. Incidentally, I crossed 6.2 miles - or the finish line of my 10K - at 54:55.
Distance runs like these are necessary. Even if you don't intend to run them.
On Saturday, of course, I ran the Mud Run, all of 10 kilometers. I've got the Mission Inn Run coming up in two weeks now but having trained and prepared for the Mud Run has also made me primed to run this upcoming 10K. If it were this Sunday instead of two weeks from Sunday, I would be confident that I would not only finish the 10K but do so in a good time, in what I consider a good time for myself, anyway.
I think overall though the run wasn't as challenging as it could have been. Yes, running seven miles is a daunting task. However, my heart rate rose fairly steadily throughout the last three miles; actually, to be more precise it was almost stagnant for 20 minutes or so.
I suppose I should take that as a good sign. If and when I run a half marathon or even a 10-mile run, I'm fairly confident now that I will be able to reach the 10-mile mark without maxing out my heart. In other words, I will have quite a bit left in the tank for miles 10, 11, 12 and 13. Running intervals and changing speeds has become ingrained in me so if I run for even a half-mile at one speed I feel like I'm not doing it right.
Somewhere around the 4-mile mark, I decided to keep the speed at 7.0. I started slowly, at a 6.0, and then increased my speed to 6.5 near the mile mark, 6.8 shortly after that and a 7.3 for the third mile. I had intended to go down to a 6.5 for mile 4, up to 7.3-7.7 for mile 5 and finish off with 6.8 for mile 6. Instead, at mile 4 I wanted to stay at a 7.0. I think that's the pace I'm most comfortable at right now.
I realized that I needed to get to 6.2, not just 6.0, so I had it in my mind that I needed to get over six miles. I felt the twinge from inside, the seven-mile itch you can call it, asking me to run that seventh mile. I was debating whether or not to go through with it when I asked myself "Come on, how often are you here?" By here, I meant not the gym but rather the distance. "Here" was in the sixth mile of a six-mile run but, more importantly, I felt good about myself. My heart rate was where it needed to be, my mental makeup was also fine even though my iPod gave out at about the 17-minute mark and I wasn't in a hurry to leave the gym.
I ended up completing seven miles in about 62:42 or so. Incidentally, I crossed 6.2 miles - or the finish line of my 10K - at 54:55.
Distance runs like these are necessary. Even if you don't intend to run them.
Wednesday, October 22, 2008
Back at it
I ran today. For the first time since the Mud Run. It felt strange yet comforting at the same time. Strange in that I was no longer running to train for the Mud Run, no longer wondering if my workouts would help me prepare adequately for the event and because I have two new goals to pursue. Comforting, well, that's an odd word to use for a run but it was just that. It's like getting into an old familiar habit.
Anyway, one thing I noticed was how quickly my heart rate dropped off during the rest part of my intervals. First, the stats:
Time: 42:00
Avg HR: 145
Max HR: 181
Cal: 527
Now, this includes the five-minute warmup. Without that my average heart rate would have been a little higher. Regardless, after running rounds of 6.0 and 7.5 for 12 minutes - the longest portion of my run - I went from somewhere around the low 160s to the one-teens in just over two minutes. This is a tell-tale sign that the interval run is not challenging enough - at least, that's what I've read and been told.
The formula is somewhat simple. Take your max heart rate (187) and subtract your resting heart rate (50 or thereabouts). 187 minus 50 is 137. Divide that by half (68.5) and add that back to your resting heart rate (118.5). If you get below that heart rate during intervals, then your workouts aren't as challenging as they could and should be.
Of course, this means that I need to amplify my workouts. I can still use this interval run and frankly I'd be upset if I couldn't. But instead of a 6.0 and 7.5, perhaps I can do 6.3 and 7.8. It's a little modification but it will go a long way, I'm certain.
After my next rounds of running, six minutes of 6.0-7.5, my heart rate went down into the low 120s but between four minutes of rounds and a two-minute sprint, it stayed at around 150. I'd expect that since by that point I'm usually exhausted. I sprinted two minutes at 9.0 and then walked five minutes afterward.
Then to round out my cardio, I biked for 20 minutes. I didn't keep track of the heart rate on my watch but since my heart rate monitor and the bike (and mill for that matter) are all made by Polar, it continuously displays it on the bike. I stayed around the mid 130s and got up to the high 150s during my most grueling part, the final four-minute stretch.
Oh, and one more positive from today. My shoes are fine. I used my running shoes during the Mud Run on Saturday and they looked in bad shape afterward, drenched and covered in mud. But I hosed them down, let them dry and put them on. They had some sand in them which I expected and felt during my interval run today. But I don't feel any sort of remnants right now.
Anyway, one thing I noticed was how quickly my heart rate dropped off during the rest part of my intervals. First, the stats:
Time: 42:00
Avg HR: 145
Max HR: 181
Cal: 527
Now, this includes the five-minute warmup. Without that my average heart rate would have been a little higher. Regardless, after running rounds of 6.0 and 7.5 for 12 minutes - the longest portion of my run - I went from somewhere around the low 160s to the one-teens in just over two minutes. This is a tell-tale sign that the interval run is not challenging enough - at least, that's what I've read and been told.
The formula is somewhat simple. Take your max heart rate (187) and subtract your resting heart rate (50 or thereabouts). 187 minus 50 is 137. Divide that by half (68.5) and add that back to your resting heart rate (118.5). If you get below that heart rate during intervals, then your workouts aren't as challenging as they could and should be.
Of course, this means that I need to amplify my workouts. I can still use this interval run and frankly I'd be upset if I couldn't. But instead of a 6.0 and 7.5, perhaps I can do 6.3 and 7.8. It's a little modification but it will go a long way, I'm certain.
After my next rounds of running, six minutes of 6.0-7.5, my heart rate went down into the low 120s but between four minutes of rounds and a two-minute sprint, it stayed at around 150. I'd expect that since by that point I'm usually exhausted. I sprinted two minutes at 9.0 and then walked five minutes afterward.
Then to round out my cardio, I biked for 20 minutes. I didn't keep track of the heart rate on my watch but since my heart rate monitor and the bike (and mill for that matter) are all made by Polar, it continuously displays it on the bike. I stayed around the mid 130s and got up to the high 150s during my most grueling part, the final four-minute stretch.
Oh, and one more positive from today. My shoes are fine. I used my running shoes during the Mud Run on Saturday and they looked in bad shape afterward, drenched and covered in mud. But I hosed them down, let them dry and put them on. They had some sand in them which I expected and felt during my interval run today. But I don't feel any sort of remnants right now.
Tuesday, October 21, 2008
Easy recovery day
My post-Mud Run training sessions officially began today. I went to the gym and was bent on two things: 1) getting on the bike and doing my easy recovery workout, and 2) NOT getting on the treadmill. I know myself. If I would have allowed myself to get on the treadmill, there wouldn't have been anything easy about my easy recovery day.
I walked right past a row of treadmills and though I longed to get on them I made my way towards the bikes. I have not done a workout exclusively on a bike in quite a long time, many pounds ago, but I got on one with the intention of staying on it.
But for how long? I started with 40 minutes, a nice, round number. I monitored my heart rate, of course, and early on it was in the low 80s, climbed up towards 100 and eventually settled in around the one-teens. I tried to pedal harder and faster as the workout got on but my heart rate only went so high before my muscles started to make noise - they weren't screaming but they were certainly clearing their throats.
I reminded myself "easy recovery" and continued on my quest to recover from the Mud Run. See, I had to not only get my muscles some light action, I also had to lay the groundwork for runs I have planned for Wednesday and Friday, runs that won't exactly be easy. I didn't want my muscles to act up or anything so I eased up on the bike.
I got to just over 14 miles after 40 minutes and paused to catch my breath. Almost instantly my heart rate dropped below 100 and was down in the 90s.
That let me know two things: 1) this workout was not strenuous, which was good because that's what I wanted (easy = not strenuous); 2) I can't do only the bike for cardio unless I'm willing to push through screaming muscles and pedal considerably harder than I had been.
I rode another 15 minutes. In a total of 55 minutes, then, I rode just over 20 miles. I don't think the workout was too difficult, so I met my goal. In fact, I feel like running right now, as I type. I suppose that's a good thing, since I'll have to run tomorrow.
But here's more proof of the easiness of the workout: my average heart rate was 118 with a max of 140. I burned 491 calories. Compare that to... well, the only recent figures I have are from the Mud Run, when I burned 1165 calories in an hour seven minutes, with an average heart rate of 171 and max of 182. That's a bit extreme of course but subtract a couple hundred calories, raise the max and that's about my typical 50-minute run.
So if I want to ride the bike, I will stick to what I had been doing and ride for 15-30 minutes after a run. Typically, my heart rate has stayed about the same, around 150, during those bike rides. And it works well to complete my cardio workout.
My plan for Wednesday then is set: run, then bike. Run a 42-minute interval run, the bike for 20-30 minutes.
I walked right past a row of treadmills and though I longed to get on them I made my way towards the bikes. I have not done a workout exclusively on a bike in quite a long time, many pounds ago, but I got on one with the intention of staying on it.
But for how long? I started with 40 minutes, a nice, round number. I monitored my heart rate, of course, and early on it was in the low 80s, climbed up towards 100 and eventually settled in around the one-teens. I tried to pedal harder and faster as the workout got on but my heart rate only went so high before my muscles started to make noise - they weren't screaming but they were certainly clearing their throats.
I reminded myself "easy recovery" and continued on my quest to recover from the Mud Run. See, I had to not only get my muscles some light action, I also had to lay the groundwork for runs I have planned for Wednesday and Friday, runs that won't exactly be easy. I didn't want my muscles to act up or anything so I eased up on the bike.
I got to just over 14 miles after 40 minutes and paused to catch my breath. Almost instantly my heart rate dropped below 100 and was down in the 90s.
That let me know two things: 1) this workout was not strenuous, which was good because that's what I wanted (easy = not strenuous); 2) I can't do only the bike for cardio unless I'm willing to push through screaming muscles and pedal considerably harder than I had been.
I rode another 15 minutes. In a total of 55 minutes, then, I rode just over 20 miles. I don't think the workout was too difficult, so I met my goal. In fact, I feel like running right now, as I type. I suppose that's a good thing, since I'll have to run tomorrow.
But here's more proof of the easiness of the workout: my average heart rate was 118 with a max of 140. I burned 491 calories. Compare that to... well, the only recent figures I have are from the Mud Run, when I burned 1165 calories in an hour seven minutes, with an average heart rate of 171 and max of 182. That's a bit extreme of course but subtract a couple hundred calories, raise the max and that's about my typical 50-minute run.
So if I want to ride the bike, I will stick to what I had been doing and ride for 15-30 minutes after a run. Typically, my heart rate has stayed about the same, around 150, during those bike rides. And it works well to complete my cardio workout.
My plan for Wednesday then is set: run, then bike. Run a 42-minute interval run, the bike for 20-30 minutes.
Today's workout
I will do either one of two things today.
A 42-minute interval run and a subsequent bike ride OR a bike ride with no running before and after.
The first option seems best for me. I like to run and I like running that particular run. But I sort of want to take some time off my feet, in a manner of speaking. I've been running a lot lately. I ran six miles on two different occasions last week and I want to change up my workouts.
But at the same time, I can't recall the last time I did cardio exclusively on the bike. Lately I've added the bike to my cardio routine. It has been a pleasant surprise. It is a great way for me to finish off a run and I think it's been rather effective in helping me build up my stamina and endurance.
Probably I'll end up doing only work on the bike later today. It's just that I always feel a bit tentative before doing something new, something different from what I'm used to. And honestly it feels like it would be a struggle to get my heart rate up on the bike to the levels it gets to while running.
I guess there's only one way to find out.
A 42-minute interval run and a subsequent bike ride OR a bike ride with no running before and after.
The first option seems best for me. I like to run and I like running that particular run. But I sort of want to take some time off my feet, in a manner of speaking. I've been running a lot lately. I ran six miles on two different occasions last week and I want to change up my workouts.
But at the same time, I can't recall the last time I did cardio exclusively on the bike. Lately I've added the bike to my cardio routine. It has been a pleasant surprise. It is a great way for me to finish off a run and I think it's been rather effective in helping me build up my stamina and endurance.
Probably I'll end up doing only work on the bike later today. It's just that I always feel a bit tentative before doing something new, something different from what I'm used to. And honestly it feels like it would be a struggle to get my heart rate up on the bike to the levels it gets to while running.
I guess there's only one way to find out.
Sunday, April 6, 2008
Interval cardio
As part of my posts here on this blog, I want to describe some of my exercises so they may be of benefit to people. This particular cardio session is my favorite one. No matter the circumstances, it always tests me and always makes it feel like an accomplishment when I finish it.
Here's the breakdown of the 42 minutes:
- 5 minute warm up (usually a 3.5 or so)
- 12 minutes of alternating rounds; 1 minute at 5.5, 1 minute at 7.0, 1 minute at 5.5, etc.
- 3 minutes walking (3.8 or so)
- 6 minutes of alternating rounds, same as above
- 3 minutes walking
- 4 minutes of alternating rounds
- 2 minutes walking
- 2 minutes sprint (8.0 at least)
- 5 minute cool down
The intervals are supposed to help drive weight loss but I've also found that it helps me recover better. When I play soccer, which I go about two or three Sundays a month, I am running as strong at the end of the game as I am at the beginning. This will be invaluable at the Mud Run, as I'll need stamina and the ability to recover.
It also helps me mentally because it's easier for me to get to the next minute knowing I will change it up rather than thinking about reaching the next 10 minutes at a steady pace.
For me the next cardio hurdle will be running outside in the elements. I know interval training will help me for when I take that next step.
Here's the breakdown of the 42 minutes:
- 5 minute warm up (usually a 3.5 or so)
- 12 minutes of alternating rounds; 1 minute at 5.5, 1 minute at 7.0, 1 minute at 5.5, etc.
- 3 minutes walking (3.8 or so)
- 6 minutes of alternating rounds, same as above
- 3 minutes walking
- 4 minutes of alternating rounds
- 2 minutes walking
- 2 minutes sprint (8.0 at least)
- 5 minute cool down
The intervals are supposed to help drive weight loss but I've also found that it helps me recover better. When I play soccer, which I go about two or three Sundays a month, I am running as strong at the end of the game as I am at the beginning. This will be invaluable at the Mud Run, as I'll need stamina and the ability to recover.
It also helps me mentally because it's easier for me to get to the next minute knowing I will change it up rather than thinking about reaching the next 10 minutes at a steady pace.
For me the next cardio hurdle will be running outside in the elements. I know interval training will help me for when I take that next step.
Subscribe to:
Posts (Atom)