'So, what's the proper pace for warm-up?' I asked one of the Garmin users last night at the track. He rattled off a pace about 30 seconds off what I try to run on one of my easy days. 'Let me walk you further down this train of thought; is there a single, right pace at which you should warm-up?' I think he got the message after that statement.
'You're breathing heavy tonight. Usually I don't hear you that way for at least another mile when the pace picks up,' said my Garmin-guy. Considering the conditions & the fact I raced two races four days earlier, it was not supposed to be a sprightly-paced run. I mentioned what I thought the pace was, at which he told me, 'no, it's...'
Some days the "fresh" pace is slower than others. I'm trying to keep it simple.
Once we got about three miles into the run I began to feel a little better & the pace dropped; a few seconds here, a few seconds there. It probably didn't hurt to make an unscheduled boxen-stop (potty break!) at the 2.5-mile point. Give my training-mates 20 seconds to get up the road & I'm hell-bent for election to catch them. It's that simple.
Too much technology leads to too much dependence on numbers - useless data - in training. If you don't know what the numbers mean, or you can't figure out what a particular effort (pace) feels like on the day, what's the use? It's little more than mathematical self-abuse.
(I was going to use a more-adult term starting with the letter M, but in order to keep this blog post at a PG rating...)
Scarier, even, is if the technology cr*ps out on you on race day. Or you find your pace/power/HR isn't where it should be. At that point what do you do? Do you panic, bail out of your race, or do you (as Clint Eastwood in Heartbreak Ridge said:) 'adapt....overcome....improvise?' Batteries die. Satellites go down unexpectedly. Connections become disconnected.