48 days to go: I ran the Hashtag Run 21K

I ran a 21K in the Hashtag Run event, organized by a team named Runtarantantan. This was a “training run” so finish time is not so important. The original training schedule was a 25-kilometer run, supposedly 7K slow, 10K fast, 8K slow. I changed it to 7K slow, 7K fast, and 7K slow. This was supposed to mimic the fatigue in a marathon where runners struggle in the last few kilometers. Did I struggle in the last 7K? Not really. Yes there was shortness of breath and some fatigue in my legs, but I finished relatively strong and fresh. I felt no cramps. My legs weren’t wobbly. I had no muscle pain.

I arrived at the run venue around 3:45 am (run was scheduled to start at 4 am) and the Runtarantantan organizer was giving a pep talk. For once, I paid attention to the speaker on the stage. I normally zone out waiting for the starting gun. He stressed the following points:

Don’t give any attention to people bragging about their run times. This I wholeheartedly agree on. Running is a personal journey. Your time is your time. That’s why it’s called a personal record. So when you run faster (or longer) than a previous run, then you are, in your own way, a winner. And those who run can understand that feeling of beating a personal record.

– Hence, no cutoff times. This I don’t exactly agree on. There should be cutoff times, not so much for the logistics (i.e., roads have to be opened up at some point), but also because people should avoid tackling a distance if they aren’t prepared. Cutoff times can be generous – 3 hours should be more than enough for a 21K, maybe 2 hours for a 10K – and that should serve as a motivation for people to train before tackling a specific distance.

– And because everyone is a “winner,” everyone deserves a medal. I used to wonder why people give so much emphasis, so much emotion, and so much importance on the medal, but then I realized that I had also cherished my first marathon meddal and that I would also soon treasure my Tokyo Marathon medal since that would be a milestone in my running life. So while local races are no longer that significant to me, it is still a significant milestone to others and I should not belittle that achievement.

– He also answered many criticisms about whether or not the route is accurate in terms of distance. He corrected the misconception that GPS signals were accurate. It bugs me when people refer to their app or their watch to contest a route’s distance. “According to my GPS, the route is wrong,” they would say. “It was actually 21.2 kilometers!” GPS is not an accurate measure of distance! Trees and buildings can block the satellite signal. GPS will also encounter problems in routes that have twists and turns! I wish people would stop contesting the race distance using GPS as their basis.

– He also mentioned why the Roxas Boulevard route is better that the Bonifacio Global City (BGC) route. I also agree that Roxas is better than BGC, the latter having more turns than the former. Moreover, he did mention that Roxas is “fully closed” as in all intersections are closed (not that there are many to begin with) unlike that of BGC where you have to stop at intersections to let the traffic flow.

Yes I do prefer the Roxas Boulevard route than BGC. It’s easier to tune out since all you have to do is run the length of Roxas Boulevard, between Luneta and the end of Cavitex, unlike that of BGC where you have to pay attention to marshalls and wondering if you took a wrong turn and ended up with runners tackling a shorter distance.

But the run was not without it’s problems. I had no problems with how the run was organized – there were plenty of hydration stations and there was no “traffic jam” in those stations. My problem was with how I used my running app. I fumbled with my running app buttons, screwing up the lap times. The full workout was still recorded, but the “middle” lap (the fast 7K portion) registered as the “last lap.” So while I have the full run recorded, I don’t have the averages for the final 7K. No big issue, but it is a lesson learned on how to operate the running app.

The other “lesson learned” was that the app begins recording after I press PAUSE if I begin moving again. The app recorded a time of 2:44 but it included the walk I took from the finish line to the finisher booth. Fortunately, I took this picture shortly after I crossed the finish line. While the time isn’t in the picture, the is time-stamped at 6:41, which means that I finished at around 2:41. I did mention that time isn’t the priority – this was not a “race” and I wasn’t aiming for any time goals nor for any personal records – but it’s also nice to have an idea of how long I took to run the 21K.

The good news was that I was able to maintain an easy “zone 2” heart rate in the first 7K, maintained close to the prescribed pace (6:20/kilometer) for the middle 7K, and was able to bring down my heart rate to below 150 for the last part.

Now I have to figure out why Spotify stops in the middle of the run. I wonder if it has something to do with the intervals. It stopped twice during the run, both close to the beginning of a new interval. My guess is that when I enter a new interval, Spotify waits for the end of the current song and then stops. I should take note of this in my next run.

And my next long run will be a challenge – 32K Resolution Run. I have always struggled at that distance. Now am excited to see how my training has prepared me for that distance.

 

Advertisements