TheHamm
DIS Veteran
- Joined
- Jan 12, 2017
- Messages
- 1,126
04 - TheHamm - Firecracker 5K (34:00 / 36:51)
This is in the running for my worst 5K time ever, but I would do the race again. I picked the goal time because it was slightly faster than I had been doing daily runs in the 3 to 4 mile range. But it was too darned hot and I woke up knowing I was dehydrated before I started.
The good: The track club had pacers even back to a 35 minute finish, which I have yet to see in a 5K. I knew I was not going to hang with the 33 pacer, but I was still holding out hope that 76* (seemed patriotic, right?) and 98% humidity would not be so bad. Also, the company who puts on the race seems to always have popsicles at the end, and this was no exception.
The bad: [1]I had planned to bike to the start, but had a flat tire. And I have not ridden regularly so the spare tube was well beyond needing to be replaced, and was not usable. No problem, 2 mile drive! Except I had to go around both the race route and the parade route, and almost did not get my bib. [2] It was HOT. If there had been water at the start I think it would have been decimated. I was just as sweaty at the end as I was in the beginning. [3] There was a silly ~0.7mile loop at the beginning, which was flat but not really shaded. [4] I was kind of running blind as I only knew the start and end points having never looked at the map. Also, while I usually use both Runkeeper and my fitbit, both have been failing (more later) so I had little feel for where I was other than 'hot, sweaty, thirsty, not done yet.'
Lesson: [1] buy new tire tube, remember to check for dry rot each spring, duh [2] The divergence between devices I had been observing for the last month is not going to get better. For example: Runkeeper 1 mile = 10:02 Mat mile 1 time = 11:07 (probably more than a mile as I ran every corner wide and avoided potholes) Fitbit mile 1 time=12:45. [3] do a better job with the potholes. I hit one, and went down while staring longingly at the water station down the block. even without this, I would not have hit my target time, but it did slow me down quite a bit, and now I have to consider how to keep the sweat from dripping down my arm to my elbow for the next few runs, the scab is not going to be sufficient.
Highlight, weird happening of the week: I was pretty bummed about running - slow, hot, hate the new shoes, generally irritated by work, want to go out and run more- and DH decided to cheer me up (ice cream would have worked) to tell me that when 2019 rooms went on sale he snagged one for marathon weekend in case I decide I am going to try the half. Shocked does not cover my reaction. I think he was looking for jumping up and down cheering with joy, but it was closer to when the doctor said 'twins!' and I sat in stunned silence. Still stunned and mostly silence. But the gears are turning.
This is in the running for my worst 5K time ever, but I would do the race again. I picked the goal time because it was slightly faster than I had been doing daily runs in the 3 to 4 mile range. But it was too darned hot and I woke up knowing I was dehydrated before I started.
The good: The track club had pacers even back to a 35 minute finish, which I have yet to see in a 5K. I knew I was not going to hang with the 33 pacer, but I was still holding out hope that 76* (seemed patriotic, right?) and 98% humidity would not be so bad. Also, the company who puts on the race seems to always have popsicles at the end, and this was no exception.
The bad: [1]I had planned to bike to the start, but had a flat tire. And I have not ridden regularly so the spare tube was well beyond needing to be replaced, and was not usable. No problem, 2 mile drive! Except I had to go around both the race route and the parade route, and almost did not get my bib. [2] It was HOT. If there had been water at the start I think it would have been decimated. I was just as sweaty at the end as I was in the beginning. [3] There was a silly ~0.7mile loop at the beginning, which was flat but not really shaded. [4] I was kind of running blind as I only knew the start and end points having never looked at the map. Also, while I usually use both Runkeeper and my fitbit, both have been failing (more later) so I had little feel for where I was other than 'hot, sweaty, thirsty, not done yet.'
Lesson: [1] buy new tire tube, remember to check for dry rot each spring, duh [2] The divergence between devices I had been observing for the last month is not going to get better. For example: Runkeeper 1 mile = 10:02 Mat mile 1 time = 11:07 (probably more than a mile as I ran every corner wide and avoided potholes) Fitbit mile 1 time=12:45. [3] do a better job with the potholes. I hit one, and went down while staring longingly at the water station down the block. even without this, I would not have hit my target time, but it did slow me down quite a bit, and now I have to consider how to keep the sweat from dripping down my arm to my elbow for the next few runs, the scab is not going to be sufficient.
Highlight, weird happening of the week: I was pretty bummed about running - slow, hot, hate the new shoes, generally irritated by work, want to go out and run more- and DH decided to cheer me up (ice cream would have worked) to tell me that when 2019 rooms went on sale he snagged one for marathon weekend in case I decide I am going to try the half. Shocked does not cover my reaction. I think he was looking for jumping up and down cheering with joy, but it was closer to when the doctor said 'twins!' and I sat in stunned silence. Still stunned and mostly silence. But the gears are turning.