While plenty of running apps guide you on how to run a marathon, how to achieve your target finish time, the target pace, average speed, and all sundry, the best advice I have received is “Follow your pace and your body, not your Garmin.”
Not from Garmin, but a buddy, with whom I ran my first marathon. After a couple of marathons, I now know more than ever what he meant. For, I have paid the price each time I did not take his words seriously.
Sometimes I have listened too much to the running app instead of my body. Yet running apps lie, lie and lie! Those moments their GPS locator fails! It did not occur to me [stupid as it sounds] that running apps timing is based on GPS availability!
Well, I had never paid serious attention, until that sweet-bitter race! My finish time was totally different from the official marathon finish time, I learned that my running app did not correctly record the time, in plac es it was MIA! It just continued on from where it had stopped recording.
Sometimes, I listen to the paces of fellow runners, and either follow, maintain my pace or slow down. This could either be both a good and bad for achieving my race goal.
A week and a-half ago, I did my second marathon of this year, after Boston in April. For this last marathon, it was a great idea to strike a balance between holding back and following “the crowds”. For most the run, I decided my own pace; oh I take that back, MapMyFitness [and sometimes RunKeeper] decided my pace.
Then and again, I tagged onto a runner or a group of runners. About three miles to finish, I found myself a pacesetter who pulled me along to finish. If she did not come along when she did, I would have slowed down, especially at Mile 25. I did not expect that nasty hill near the finish. Let me just say, from mile 23, it was all uphill. But she was still running as fit as a fiddle, and had done this race before.
So, I just tagged along, and that helped me conquer the steep hills. In fact, she saved me from a would-be shocking terrible finish. I had no idea, my apps were not telling me correct timing! I was holding back, thinking I am running faster than my target pace. All wrong!
I know that going too fast can also be detrimental to a good finish. Boston 2015 comes to mind. I had a great time, running out there with lots of cheers, the weather was not too bad and my legs felt in the best shape ever. I was not listening too much to my running app, but my body.
But for the last six miles, particularly the last three miles, I experienced the most difficulty, staying the course. Plenty of times, I wanted to quit and walk. It was gruesome climb after climb. The course is a pain in the butt, plus the wind velocity of the day. Damn! It beat me so bad. But I am proud because I had great pace/mileage.
For my next marathon, I plan follow my body and legs more than my Garmin. Yes, I am going to invest in a Garmin again! You know, ever since I started running with my phone [which is kind of for security purposes] I put off buying another Garmin after my previous one broke. I thought, running apps work as good as a Garmin.
But there’s no better GPS technology than a Garmin to locate you, while mobile network provider sleeps off. Implying, the “security phone” is actually not secure the entire course. Your mobile network provider might not rescue you, if you run off in the thicket of the forest!
Above all, remember to have fun running a marathon, color your hair, read the placards and give a power touch whenever a spectator asks for one. High 5 the kids, stretching their hand out to cheer you on along the course. Respond with a “Thank You” to the spectators as much as possible. It means a lot to acknowledge those who have foregone their sleep, standing out in the freaking cold, the heat or pollen to fuel you up.
Next up, Chic-Town?
Comments