This only barely qualifies as a brick, but I did technically ride a bike and then go for a run, so I’m counting it.
The family and I loaded up the car with all of our bikes, all four of ‘em, and headed to a nearby bike path. Our kids are still learning how to ride, so the flat, protected area was perfect for them.
We saw some amusing sights along the way, including a goat corral where goats were being used to help eliminate some poison ivy. Apparently they love the stuff.
As it turns out, their names are Ruth, Bader and Ginsburg. Not even kidding.
After we got home, I went out for a longer run, even longer than my run earlier in the week. I had already begun to think past my third triathlon to next season. I knew I would have to start extending the time I spent on the roads, both in my shoes and on the wheels. No time like the present to start that process, I figured. I had a couple of weeks until triathlon #3 so I wasn’t too worried that I would affect that performance.
A frustrating thing was that my Fitbit Ionic crashed on me during this run, so I wasn’t able to record the GPS data or heart rate, and had to manually calculate my pace after the fact based on the times that I left and returned, and by knowing the distance of the route using Strava.
- 5.20 mi Distance
- 51:00 Duration
- 9:48/mi Pace
That was really a bummer because the stats help motivate me, and this was the longest run I’d done so far in this training program. I wanted the numbers and the route, as a milestone entry in my log. But I had to settle for a manual entry.
