Increasing fitness by not running

Building fitness can be relaxing

I believe it's okay to take an ad hoc rest day every once in a while. I did it today and I feel no guilt whatsoever. While I will probably never get up and say, "Hey, I feel great, I think I'll skip my run", I didn't rest this morning because I was feeling weak or ill. What I felt was under-rested and I concluded that I'd be better off taking it easy, rather pushing hard and inviting a problem.

When you think about it, a day of rest is often better for you than a single day's run, because recovery periods are when your body actually builds fitness. That's holds true for a day or even two, but then it starts to go the other way. I've been doing workouts six days a week for the past few years. That generally works for me. My average run  (accounting for shorter distances on weekdays and longer ones on weekends) is 3.3 miles. This seems like the right amount of exercise to keep me fit and (knock wood) to prevent me from sustaining injuries.

The reason I don't feel any guilt for skipping my today's run is that I know I'll be back at it tomorrow. However, my decision puts me three miles behind in terms of reaching my weekly target of 20, but I can probably make up some mileage on Saturday or Sunday. In the meantime, I'm happy knowing that taking a rest was the right thing to do this morning.

Trust your waiter at your own peril

Yeah, sure you are...

Today's run (treadmill): 25 minutes

There are certain things we know we shouldn't do, but we do them anyway. These things are often situational. For me, it's the decision to order coffee after a business lunch. There's nothing wrong with coffee, but I am extremely sensitive to the amount of caffeine I can keep in my system. A little goes a long way for me and I find it a legitimate performance supplement for running.  But having caffeine too late in the day generally disrupts my night's sleep.

While caffeinated coffee affects me, decaf doesn't. At home I can confidently brew a pot of decaf when entertaining friends at night and drop off to sleep without a problem. The problem happens when I order decaf in a restaurant and get regular coffee. I've had enough experience to know that, even after stressing the word decaf and then verifying that the cup placed in front of me contains it, there's a percentage chance that I've been given the fully caffeinated brew.

Caffeine version please

That's exactly what happened to me yesterday at lunch. I thought about the risk, but ordered it anyway. It wasn't until I was tossing and turning in bed last night that I realized what I'd done. If I was a chemist, I'd look for a way of sampling coffee to instantly determine the presence or percentage of caffeine in the cup. It could be like the color-changing chemical that police use to determine if a suspected substance contains cocaine.

I think I could make a lot of money marketing that to caffeine-sensitive people. It would also allow me to take waiters to task for botching my order. That would be much better than cursing them at midnight as I wait to fall asleep.

Garmin FR210 behaving badly

Get back to work!

Today's run (treadmill): 25 minutes

After two years of stellar service, my Garmin FR210 has started to exhibit some bad behavior. I bought this watch because it provided basic GPS metrics, elevation data and wireless syncing with my heart rate monitor. Like all GPS systems, the distance accuracy wasn't 100%, but after a while I understood the margin of error and mentally corrected for it. There are things I still don't like about the watch, such as the weird way it connects to a PC for data uploads, but overall it has been a great resource and a good value.

The bad behavior started on January 1st, with my first run of the year. I was a couple of miles into the Hangover Fun Run at Eisenhower Park, when I looked at the watch only to see that it wasn't recording time or distance. I decided to let it go and just use the event clock to record my time. I figured that I must have neglected to fully push the start button and was paying the price for that inattention.

Since then, I've run five more times. On three of those runs I've noticed that the timer stopped recording after I'd initially started it. It doesn't happen every time, but it forces me to pay careful attention to the watch on every run. I don't know why this would suddenly happen. I checked the FR210 forum on Garmin Connect but haven't seen anyone else with the same complaint.

It would be a shame to have to replace this watch because I've come to rely on it to capture all my metrics, including a map of where I'd run. I still have my FR60 that works fine, but it lacks GPS so I'd need to return to using the foot pad. If I did that, I'd lose the mapping but would gain cadence, something I miss since switching from the 60 to the 210. I could always use an app on my smartphone to do the mapping since I carry the phone on every run. It's worth thinking about. But I'd rather have the FR210 working as it should.

The problem of running too fast

I have two friends who tell me they simply cannot run slowly. When running alone, they claim to always push their pace to a level of discomfort. They have a difficult time easing up when their coaches tell them to slow down during training sessions. If these guys weren't two of the nicest, most secure people I know, I'd chock it up to macho posturing. After thinking about it, I'm beginning to understand their perspective.

Unlike my friends, I can run slow anytime that I'm asked. But ask me to walk slowly and you'll get a different response. I often find it maddening to walk the streets of NYC, especially in midtown where I work, where my path is constantly obstructed with dawdlers of every type. I've always been a fast and impatient walker. This trait that makes for efficient travel across the city, but it can really annoy others who aren't in a rush.

I envy my fast running friends because I really do enjoy the experience of moving swiftly on a run. I just have trouble sustaining an urgent pace unless I'm in a race. I'd always assumed that a person who can walk fast for miles would also be able to run fast for long periods. Sadly, that's not the case. I know I've become competitively complacent since October's Town Of Oyster Bay 5K. Perhaps now is the time for me to start picking up the pace.

The soul of weekend runs and the Sole of weekday workouts

Sole F63 - my frequent morning companion

Today's run (street): 4.2 miles

It's more than halfway through the weekend that followed my short week back to work. The real test comes next week with five straight days of waking up at 3:45 AM. Four of those mornings will involve a run that starts before 4:00. It's harder in the winter, especially on those days where the temperature falls below freezing.

A year ago I would bundle up and get outside every morning unless it was raining. These days I usually choose the treadmill because it saves me time. Instead of dealing with layers of clothes, headlamp, etc., I can be running in minutes. Is it the same experience? Far from it. It always feels like I work harder on the treadmill but the benefits are lower. The machine might be a Sole, but the workouts are somewhat soul-less.

The weekend provides far more opportunity for interesting running. Adding to that is the flexibility to start my run later and to run longer. Yesterday I enjoyed a trail run after a leisurely morning having coffee and spending time with my family. I wasn't that excited about doing another neighborhood run today, but it was better than staying inside.

I probably overdressed this morning in response to the 34°temperatures reported on the news. The skies were dark and gray when I stepped outside so I left my sunglasses behind. About a mile into my run the sun came out and I began to regret that decision. The sun also started to warm things up and I hoped I wouldn't end up completely saturated in sweat before I finished my workout.

Somehow I managed to stay comfortable throughout the run and I even picked up the pace a few times. I wanted to run at least four miles today to hit my weekly distance target and I ended up totaling 21 miles. It's been a while since I've run at Bethpage so I'm thinking of heading there next weekend. In the meantime, the next four runs will probably happen on the Sole F63.