Enough about Kate, who wants everyone to know she also was weighed down by her Garmin watch. It’s time to steer the conversation back to my favorite subject: me.
After my third consecutive night of fitful sleep, I’ve had an internal debate the past hour over whether to run, row, ride or at least make my Saturday morning yoga class. I have a small window before the day starts to accelerate with activities, and I've decided to forgo structured exercise for the second day in a row. I hurt my heel/ankle walking too long in the wrong work shoes. I’ve been icing and resting it since Thursday—to some relief.
I could take the foot for a quick spin, but that test could also set me back, and for what? This, I think, is one of the biggest differences between those who train for speed and those who train for distance. If I were training for a half or full or ultra marathon, I’d feel compelled to get more mileage in, even if the run was slow and painful, just to avoid too many goose eggs. But when your main goal involves shorter courses done at greater speed, you can afford to be more conservative. There are no “maintenance miles” on the schedule; every workout has a specific focus, whether it’s intervals, tempo runs, hills or longer, slower runs to build up endurance. This is both burdensome and liberating.
I admit I most look forward to Sunday long runs because they are the only times I am not at war with my watch. But I’m also starting to feel like a real runner again, despite minor setbacks from weak wardrobe choices. And that’s because my runs have purpose again, with local races to gauge personal progress.
That doesn’t mean I won’t be having the same debate tomorrow morning. I’m going to be on my feet 2:30 to 10:30 tonight helping host a major fundraising event. I’m wearing brand new sandals, which could aggravate that foot ache. If I do end up limping, at least I won’t also have to kick myself for overdoing it earlier.