When is a Straight Line Not the Fastest Route from Point A to Point B?

4.05 mi.@ 7:44
Mizuno Wave Rider 12

When you're a distance runner a straight line isn't the fastest route between two points. Now don't get me wrong. I'm not talking about running all the tangents on a marathon course to save yourself strides at the end. The "straight line" approach doesn't work so well when each foot is on that "line" stride after stride after stride. My way of thinking of it is that you're effectively walking a tight rope. That can become tedious on a 26.2 mile (or even 10 kilometer) trek. It also causes a number of serious deficiencies and inefficiencies in your running biomechanics. According to the doctor I'm working with, my calf strain (a type of repetitive muscle strain) is being caused by my feet landing "on the same line" stride after stride. Based on the wear pattern on my shoes and observation, there's really no disputing this. He believes that "opening up my stride" will remedy my calf problems and avert the knee problems that were most likely next in line.

So I'm learning to walk again. And it's very hard!

A straight line isn't the fastest route from point to point when it causes an injury which puts you on the sidelines!

I Ran Today!

3.12 mi.@ 8:05

Mizuno Wave Rider 12


Good news. I ran today! A couple quick facts:

I'm injured.
I won't be going to Boston.
I'm very disappointed.
I'm getting treatment.
The symptoms - painfully tight calves - are being treated and seem to be responding well.
The cause - a biomechanical flaw in my gait - is going to take time to correct.
I entered the St. George marathon lottery and hope to get pulled. If not, I'll look for another fall marathon. Any suggestions?

I'll fill in more of the details in future blog entries.