return void;

So last week didn’t produce anything eventful in the running area. I powered through the runs and found that I get better in second extended interval than the first. I struggled with intense 40 mph winds on Wednesday’s tempo run which sapped the energy from me and caused me to walk a few times. Uphill and into heavy winds like that is no way to start a 3 mile tough run. I also made the mistake of changing the route Wednesday due to the increased distance that I definately paid for thanks to the wind.

The only thing worth noting is I had an excellent run on Saturday. I did not fatigue until the halfway mark, which is about 2 miles further than it took last week.

I’m posting this late in the week because of the troubles I had with SportTracks again. This software is seriously pushing my patience. I accidentally hit the start button on my Garmin when I was changing on Saturday, so there was a few seconds of no movement until I realized I had done so. The trouble came with importing the data. SportTracks has this nagging bug where it does not successfully delete the last track, so my pace chart was horribly skewed because of that accidental split. I kept trying to remove it and did everything I could think of. The solution I stuck with was splitting the track at the time that I thought I finished, then removed the new activity.

These kinds of bugs are trivial to fix, but take an extrodinary amount of time to get resolved in a closed source environment. Every little nitnoid like this is driving me closer and closer to an open source solution, such as PyTrainer. In fact, I am tempted to get started helping with development.

Anyhoo, here’s the charts: