Speedy Speedy

Day 52
2 miles at 9:57/mile

Why is it that 2 miles seems so much harder than, say, 10 miles?

Christina met me at my house and since I didn't have my watch juiced up, we had to run a 2 mile route around the neighborhood that I'm familiar with. The goal was to run and make sure we hit the finish before 19:54.

The first mile, we had to run up Stansbury Parkway, which seemed a lot easier today than on Saturday during the triathlon. Granted, it wasn't raining, I wasn't wearing wet socks and shoes, and I hadn't just biked 12 miles. But it was bordering on pleasant. For me anyways. Christina mentioned that she was struggling.

We crossed a mile at about 9:25, well below pace. We turned around at the top of the neighborhood on Stansbury Parkway and ran back down and around the neighborhood to the top of Harvest Drive. It's exactly two miles (I measured on Google Earth when I got home). I'm good, aren't I? :) We finished in 17:54, which means we AVERAGED 8:57/mile. Woot! But since I know we did the first mile in 9:25, we did the second mile in 8:29. Hello? I couldn't even run my fastest mile two months ago that fast. And I just did it as the SECOND mile in a two mile run? How awesome is that? The best part was that I felt like I could've run another mile.

In other news, KSL is reporting that Hobble Creek is currently on fire. I don't know where the fire's at or if it's going to impact our run, but pray that we'll be able to still do it. Because I freaking trained all summer for this. And I'm not going to be very happy if some stupid fire cancels it.

Oh, and I'm now up to five pounds lost. 5 measley pounds from working out six days a week for an hour or more. The injustice.