Recently I entered myself into a mass-start ride that would be well over 60 miles long (70+ in fact) with over 5000 feet of climbing. While this may not seem like much to some of the ultra-cyclists out there, when you realize that the climbs are nearly all at a steep gradient (New Jersey is just a bunch of ridgelines) and that I have been working on my time trial position, something was going to break - and it did. My left knee started giving me problems at around mile 40 and I just rode through the pain.
My mother (a physical therapist) did a few simple checks and decided that my quad muscles were lopsided and one side of the leg was pulling the kneecap off center. Ok - not good but also not bad! After a fairly easy week though the pain had subsided off the bike because of the exercises I had been doing to strengthen the inner side, but on the bike the knee still hurt. I decided it was time for a cyclist’s opinion. Speaking with the person that has done my fit twice and is a good rider himself the conclusion was that there is something wrong with the way I was pedaling and/or sitting on the bike.
The problem could be one of many things…
- I had adjusted my saddle position to be farther forward and this was crunching the knee too much on the top of the pedal stroke due to the lower position. Fixes? Raise the saddle or sit back farther.
- I was pounding too hard on the pedals and not lifting enough on the upward portion of the stroke. Fixes include spinning lighter and spinning faster.
- Unlikely possibility but my left leg could be a different length. Fixes would include a refit with some shims or something.
I can hear the programmers wondering what the hell this post has to do with debugging code. If you are a learned programmer you should understand the benefit of the scientific method and having controlled changes. By limiting the number of things you change between builds a programmer can see how A affects B directly or indirectly without worrying about how C fits in. I take a similar approach to my health: when sick, eliminate something until the problem changes or is fixed and then work backwards adding things back on. Unfortunately I didn’t do that this time around!
What ended up happening is I bought new bibs (shorts with suspenders built in) that have a thicker padding than the ones I was wearing when the problem started. I also lightened my pedal stroke and sat farther back on the saddle. I just committed debugging suicide by changing three things about my fit and while it may not seem like a big difference remember that a 1mm change in saddle height can be the difference between excruciating pain and pure bliss for some riders. The effective changes include higher sitting height from the bibs and the saddle position, a different KOPS measurement due to changing the saddle position and spinning lighter meant that my quads would not be working against each other so much.
Where do I go from here? While the changes have eliminated the pain, I need to actually work backwards no until I get some sign of the pain reoccuring. This means sitting forward on my saddle with the new bibs as well as sitting at the back of the saddle with the old bibs. I have to mix it up completely until I can figure out specifically what triggered the pain. The problem is that it is time wasted towards a goal I don’t want to sustain (knee pain) and with a race in five weeks, my fit should be the last thing I am worried about.








