T48 - Knowledge is Power - Swim/Bike

Gainesville

Swim: speed day
wu: 400 continuous. last 50 in each 100 is kick
main: 10 x 100 EBEH (each 100 = 25Easy, 25Build, 25Easy, 25 Hard)

2 Lipodrene

It seemed that the Monday illicit activities were not hampering me today as I managed to get up earlier than normal, and was at the pool before noon. That's two days in a row of starting before noon, if you're counting. This workout today was nothing new. But I made it through with good power and felt great the whole time. I mean, I think set 4 or 5 I slowed a little on the "Hard" lengths, but I had to marvel at how these used to kinda kick my ass. Like even during the last cycle, I often used the 3rd length to totally slack and take it easy. Now it's probably a similar speed to the old "Build" lengths. Also, my intervals in between are getting a lot shorter, which has to be a good sign. Like I'm generally ready to go again in 30 seconds, and can generate the same speed and power as I was in the last set. Improvement is always fun.

Bike: 1.5 hour with some climbing or low cadence work if you're on the
trainer. RPE 3-4 on the flats and allow yourself some out of the saddle work
of RPE 7-8 on the hills

2 Lipodrene

I took a solid 5 hours between the swim and bike today. Didn't see much point for a brick with the "Escape to Campus Lodge" tomorrow. More on that tomorrow. Anyway, I decided to go at the suggested RPE on the flats and then balls out on the hills in the Hammock on Hawthorne. But when my computer went out 3 blocks into the ride, I got a little pissed. There's a sensor on the wheel that I guess gets misaligned, and it had been fine since I brought it in in June, but after I washed the bike it has been fucking up again. And I realized on the course in Orlando that not knowing how fast you're going, or how much time you've been out there, makes it hard to push it on the bike. At least for me. So after I stopped for like 5 minutes to try and un-fuck it, I gave up and decided to just use the clock on there as my timer.

On a ride where you're supposed to take it easy, not having a speedometer to make sure you don't go TOO easy makes you slack. Unfortunately, I have no idea how bad I was slacking, but I was definitely taking it easy. My quads were a little sore, presumable from Sunday's run and lack of any viable nutrition since then (that munchie-induced large cheese pizza from Mellow Mushroom was probably not the BEST idea)so I really had no reason to push it. When I got to the hills, though, I floored it, going as hard as I could and ignoring my throbbing quads as I did it. I feel like the first hill went well, although I'd been doing it at 20 or higher the last tow rides. This felt about similar.

My computer decided to start working just after nigbridge, so once again I'm not going to take it in to be fixed. Maybe when I get my rear wheel unfucked next week. At any rate, I decided to keep a solid 18-19.5 the rest of the way, which worked out well with the RPEs for today. I didn't make it that far, though, as even lame 90 minute rides I'd had previously got me further on the trail. But the way back I hit the tough hill in the hammock (the way back is steeper) and stayed at 16-18, which is about 7-9 MPH faster that I do some parts of it on long rides. So that was a bright spot.

Not sure what I'm going to do about this computer. I can't have it go out during the Ironman, but at the same time would getting a new one even fix the problem? Definitely a question for Tommy when I take this think in next week. Tonight I had some Muscle Milk a big pasta dinner as tomorrow morning's workout will be tough.