View attachment 909688
New PR, 50 min off my prior NYC trek. Incredible race, crowd support was insane, and the Queensboro Bridge is still very bad. REALLY thought I was on my way to hitting my target goal and they reminded me that nope, wasn’t going to be that easy. I’m at peace with my performance though, didn’t feel like I prepared well enough for this two years ago, this time I did, so we’re good.
One funny side note: I had been monitoring my Apple Watch pace throughout the race and thought I was where I wanted to be to hit my goal (10 min per mile), thought if I could maintain that for 20 miles I had a really good shot. 8 miles in a pacer with a 10:06 pace starts approaching and I realize that something isn’t quite right. Then I started keeping an eye on mile markers compared to when my watch was showing as hitting them and it was a quarter mile off and increasing. I managed to keep up with the pacer for awhile to maintain that pace but obviously I was very uneasy about what I’d need to do to get 4:30. By mile 23 it became apparent that I wasn’t going to be able to hit the target (my left thigh started twitching at mile 18 so I was being careful about my strides so it wouldn’t blow up) so I focused on the PR goal, then at mile 25 my watch died.

Kinda sucks! I know people here were talking about how this happens but really frustrating when the whole purpose of having this is to track my runs and it can’t last through the big one. It’s two years old and I don’t wear it outside of runs.