I think everyone who knows me knows that I am a little obsessed with Mexico. Maybe it started when I lived in San Diego and made the association between Mexico and legal underage drinking, or maybe it was because Mexico is a big part of the desert Southwest that I love (or, to be more accurate, the desert Southwest that I love used to be a part of Mexico), or maybe it's because Mexico has a gritty authenticity about it that is appealing when compared to the U.S. and Europe. For whatever reason, everything to do with Mexico is very interesting to me. So I always knew that I would do the Mexico City marathon some day. My original plan was to combine the marathon with a week of Spanish immersion school, but when I made that plan I didn't know I was going to change jobs and lose much of my vacation time. I decided that Mexico City for a weekend was better than possibly Mexico City never. It's not really that far away, and it's not very expensive to fly there, so I made up my mind and signed up.
I speak enough Spanish to communicate, although my vocabulary is limited and my ability to conjugate verbs is questionable, so I knew I could get by on my own if I had to. Luckily I didn't have to. I have a friend in Mexico City, Gerardo, who was my interpreter in last September's international class at Leader. He is one of the coolest people I know, and he pretty much gave up his whole weekend to help me get around and show me the city. It's a good thing he did, because the only thing I really did to prepare for this trip was find an Airbnb in a safe tourist area that was walking distance from the marathon start line. Things I didn't do that I would do next time include talking to Verizon and finding a way to use my phone in Mexico, and learning something about Mexican money. As it was, I could use my phone only occasionally, sometimes when I got a wifi connection and sometimes randomly when I shouldn't have had any service at all. And when I arrived in Mexico and went to take cash out of an ATM, I had no idea how pesos compared to dollars. In my head, 1800 pesos could have been $20 or $1800 or $5000. I just randomly chose 1800 pesos to withdraw because it was the middle selection in a row of choices on the ATM screen, like where $100 would be on a U.S. ATM. (And as it turned out, that was almost exactly what it was -- $94.)
Gerardo picked me up at the airport and drove me to the Expo, which wasn't that far but took us forever to get to because of traffic. Let me say here that I love how people drive in Mexico City. A lot of roads don't have lane lines, so there might be two lanes, or three, or four, it just depends on how much room there is and how many cars are on the road. Drivers sort of make their own lanes. Rolling through stop signs seems to be totally okay, as I saw it happen at almost every stop sign even when there were cops around. Every driver seems to be a distracted driver, with sudden veers, unsignaled turns, and jamming on the brakes for no obvious reason all being very common. Pedestrians cross through moving traffic whenever they want, and cars and people just somehow avoid each other. Drivers honk their horns even though surely they know it has no effect whatsoever on whatever has made the cars in front of them stop. It's not uncivilized exactly, just casually sloppy, exactly how I would like to drive if it weren't for traffic laws and cops in the U.S.
The expo was huge. It might have even been the biggest expo I've ever been to. It felt like we walked a mile between the entrance to the sports venue where it was held and the place where I finally picked up my number. It was packed, too -- shoulder-to-shoulder people the whole way. I ate a couple of snacks including the driest protein bar I have ever tasted. It tasted like a piece of cardboard and was the same consistency. Other than the size of the expo, this was exactly like an expo at any large marathon I've ever done.
We spent the rest of the day driving, walking around, and eating. We ate at a vegan restaurant that would not have been out of place in any trendy, urban neighborhood in the U.S., and I had black bean tacos and a giant bowl of oats, chia seeds, and fruit. All of the food was excellent. It started raining after that and we drove around looking at monuments. There are a lot of grand, impressive monuments in Mexico City, a lot of them right in the middle of giant traffic circles. I was glad I was with someone who knew the stories behind them and could tell me what they were.
I slept badly because I wasn't sure exactly where the start line was. I knew I had to leave my building and turn right, then walk until the road ended at the Zócalo, but since I hadn't actually seen the start line the night before, I was paranoid about screwing something up, so I left earlier than I needed to. The temperature was perfect for a marathon, 58 degrees with a predicted high of 67. Skies were overcast, but it wasn't raining anymore. It felt strange but undeniably pleasant to breathe air that wasn't humid. The elevation of Mexico City is 7300' (I thought it was 5000' when I signed up for this marathon, and only found out a few days ago that I was off by over 2000'), so it definitely didn't feel like Florida. I wasn't overly worried about the elevation. Throughout my running life, I have found that there is generally a positive correlation between difficulty with elevation and amount of time spent worrying about difficulty with elevation. Personally, I prefer to not think about it.
I didn't need to worry at all about not finding the start line. With over 30,000 runners registered, there was a steady flow of runners from the moment I stepped out of my building. I walked around like a tourist, staring at all the old, grand buildings. This has to be one of the most fabulous marathon start lines in the world.
I did run into a couple of small complications, and the first one was that there was a corral system. I shouldn't have been surprised -- with the size of this race, how could there not be? -- but I was. I had not read anything about the corrals on the website, but then I'm not really in the habit of reading race websites. Most U.S. marathons that I sign up for flood my inbox with emails containing race information, so I have gotten used to sitting back and letting race information come to me, not seeking it out. I realized for the first time that there was a blue square on my bib, and that each corral had a color. I kept walking and walking further and further back from the start line and saw that the blue corral was way in the back. I must have predicted a really slow finish time when I registered, even though I couldn't remember predicting a finish time at all. As I listened to the race announcer, I thought I heard him say that the blue corral was starting at 7:45. I hoped I just misunderstood since the official race start was at 6:45, and when I told Gerardo when to meet me at the finish, I picked the time based on a 6:45 start. Since I couldn't use my phone, I had no way of telling him my start time was an hour later than I thought it was. Oh well. In situations where you can't do anything, it's better to just accept it and move on.
The other complication was that when I went to get into my corral, the guard said "Brazeleta?" I just stared at him blankly. He pointed at his wrist and then at the other runners entering the corral. Every one of them had a blue bracelet. I was mystified. The guy that gave me my number hadn't said anything about a bracelet. And I know it wasn't in the envelope my bib was in because I had upended that one and dumped out all the safety pins, then looked in it again to make sure it was empty. I have never had to have a bracelet in any other marathon unless I was using race transportation or there was a beer tent at the finish. I told him I didn't have it. He waved me on into the corral. I still do not know what the purpose of the bracelet was, but apparently it wasn't critical because I did get an official finish time.
I stood in the corral for over an hour while the wheelchair racers started, then the elites, then, one by one, the faster corrals. Finally the runners in my corral were allowed to start walking towards the start line. I was cold by now, and glad I had, for once, brought a throwaway long-sleeved shirt. (So long, Pocatello Marathon shirt.) The race announcer counted down, the gun went off, and we were released!
This is a very, very beautiful course. It is one of the best courses I have ever been on. Here is the video, in case anyone familiar with Mexico City is curious. The course is mostly flat except for a couple of bridges (thank goodness, with the elevation), and, almost without exception, is nearly all on beautiful streets that really show off the city to its best advantage. Two things I noticed right away. 1) The course was extremely congested with runners. I expect to have to do a lot of weaving around other runners the first couple miles, but this one never let up all through the race, even in the last few miles. I'm sure I could have finished at least 15 minutes faster if not for the amount of time I spent looking for a way around other runners and turning sideways to squeeze through very small spaces. If I ever do this race again, I will definitely predict a faster finish time so I can be in an earlier corral. 2) The crowd support is unbelievable. It's like Boston or NYC -- wall-to-wall spectators almost everywhere, yelling, "Sí se puede!" and "Venga!" the whole way. I had the thought several times that if I were going to throw up, it would be hard to find a place to do it without hitting a spectator.
I felt generally good for most of the race. I didn't have any injuries, I wasn't too hot, I was enjoying the scenery, and the huge amount of food I ate the night before didn't seem to be having any adverse effect on my stomach. There were plenty of aid stations, and they alternated between Gatorade and water. The Gatorade was served in cups and the water was served in little sealed plastic bags. The bags were the ideal size for stuffing into my sports bra in case I wanted one later, and were also ideal for spraying myself down if I got hot: just open the bag and squeeze it, and voila, my own personal fountain. Also, I discovered that I prefer kilometers to miles. Yes, there are more of them, but they go by so quickly. Practically as soon as I passed one marker, I could start looking for the next one in the distance. And it's much easier for me to think of eight 5k's (plus a little extra) than to think of a full marathon.
The last few miles were a straight shot up Insurgentes. Spectators were everywhere, screaming encouragement and offering food and drinks. I ate some of just about everything I could get my hands on -- mango, watermelon, beer, a handful of little curly brown fried things that looked like chicharrones but curlier, a little baggie (think poop bag) of candy-flavored orange liquid tied in a knot. I figured it was too late in the race for what I ate to affect my stomach, and spectators got really excited when runners took what they were offering. The finish line was in Estadio Olímpico Universitario, where the 1968 Summer Olympics was held. It was an epic finish. We ran down into a tunnel and then out of the tunnel onto a track, and then around the track to the finish line. Even on the home stretch, the track was crowded. I finished with a time of 4:26, about typical for my last several marathons. I simultaneously would love to be under 4 hours again, and don't really care if I ever am or not. The only food at the finish line was bananas. Someone also gave me a bottle of the nastiest Gatorade I have ever tasted -- strawberry. I took a few swallows of it, thinking I needed to get my electrolytes replenished since my skin was powdered with salt like it used to be in Arizona, and that tiny bit of Gatorade almost made me throw up everything else I had just eaten. I threw away the bottle and decided my electrolytes would just have to replenish themselves.
I spent my last few hours in Mexico visiting the Blue House -- I may be bored by art, but Frida Kahlo was such an interesting person that even her art is interesting -- eating, and walking around an indigenous market and eating more. I ate vegan nachos, vegan lasagna, some kind of fermented corn drink that tasted like yogurt, and greasy street tacos with beans and potatoes. I changed into clean clothes but didn't make it into the shower until after 10 p.m. I was not going to waste my precious few remaining hours in Mexico by taking a shower!
My flight out Sunday morning wasn't till noon, so I got to sleep in till 7, a total luxury. My trip to the airport was mostly uneventful other than that my Uber didn't work -- it insisted my payment method was invalid, and wouldn't let me add another one -- so I had to take an expensive hotel taxi from the Hilton. (Even an expensive taxi was only about $15 -- try getting to any U.S. airport via taxi for that price!) The driver spoke about as much English as I speak Spanish, so we talked the whole time, in both languages. I asked him if he drove a lot of American tourists. He said no, and that he thought Americans think Mexico City is dangerous. I agree, based on the reactions I got when I told people I was going. Here's what I think: Mexico City is NOT dangerous in the parts I was in, or at least no more dangerous than any other big city. There are police everywhere. I didn't visit any bad neighborhoods, but I wouldn't visit those neighborhoods in an American city either. The parts of Mexico City I saw, which were admittedly only tiny parts of the city, and only the nicest parts, looked completely modern. Even if I didn't speak any Spanish, I still would have felt safe there. I hope no one lets fear keep them away from a place as incredible and impressive and interesting as Mexico City! I'm glad I got to go, and feel like I made the most of my very short trip there. Am I still planning on going there for a week of language school? Um, yes. Duh. As soon as I bank a little more vacation time, I will be back there the first chance I get.
In the meantime, I may or may not have typed this question into Google: "How many Mexican states have marathons?"
Tuesday, August 28, 2018
Sunday, August 5, 2018
Ironman Training Journal, First Month
This was the scene a week ago. Tampa, 11:30 a.m., hot and steamy like the jungle. I was sitting in my car in the shady parking lot where the Upper Tampa Bay Trail -- 7-something miles of paved bike path -- starts. I had a minimum-3-hour bike ride looming, followed by a 2-mile run. I DID NOT WANT TO DO THIS, not at all. I had just come from the airport, a quick work trip to Kentucky. Before I left for the airport, I did something my pre-Ironman training self would not have done, and put my bike in my car so that just in case I felt like getting my long ride out of the way on Friday instead of doing it on the weekend, I would be ready. I changed into bike clothes in the airport and filled my water bottles with water from the airport faucets. Then I drove to this parking lot where I sat thinking about the temperature -- 89 -- and the humidity -- high -- and what both of those things would be like in three hours when I was ready to start my run -- worse. I have bailed on plenty of workouts in my life. Sometimes even when I left my house in Michigan at 3:30 am, I drove right past the gym to the donut shop and then slept on the couch at Leader until work started because I couldn't face the thought of getting into that cold pool. I sat in my car and thought about my 11-hour work day the day before, my 3:30 alarm to get to the airport earlier that day, my cool house and comfortable bed. Then I got on the bike and headed out. I told myself I could have a crappy slow ride or I could decide to enjoy it, but either way I would be on the bike for 3 hours and then I would run after that. And somehow my crankiness mostly evaporated and it turned into a pretty good ride and a pretty decent run, and that is what's happened for every single workout I've done so far.
I've registered for, and bailed on, two half-Ironman distance races in the last 10 years. One was the Soma 70.3 in Arizona, which I quit because I didn't want to work on my swim, and the other was the Steelhead 70.3 in Benton Harbor, Michigan, which I quit because I started to dread the training schedule so much that the dread took over my life. Plus, I didn't like the thought of swimming anywhere in Michigan. The Lifetime pool was always too cold, lakes are gross and also too cold (except for maybe a few minutes in July) to swim in without a wetsuit, and wetsuits are expensive. There was nowhere to ride my road bike except Stoney Creek and Kensington Metroparks, nothing pretty to look at, and for more than half the year I was freezing anywhere except the gym. I thought some of those things would be fixed by moving to Florida, but in all honesty I wasn't sure I wouldn't grow to hate the schedule just as much as I did in Michigan. Even if I did, though, I was pretty sure that the OVER $900 REGISTRATION FEE would keep me from bailing on the training.
I have now finished 7 weeks of the 20-week schedule. Although there is still a lot of time left for things to go south, I am happy to say that I haven't missed a single workout so far, and am thriving on the schedule. I'm not always dying to start every workout -- see above -- but it's never THAT hard to just do it. I've learned a few things along the way too.
*I can swim in the ocean! I have played in the ocean before, but swimming in it was a completely new experience. I really didn't know what to expect. A lot of bad swimmers are terrified of the open water swim (OWS), and some people even get nauseous in the waves. From the moment I started swimming in the ocean, I loved it. It is like a giant, bath-temperature swimming pool where you never have to worry about getting a lane and the lanes stretch out to infinite lengths. Some oceans might be cold and rough and intimidating, but MY ocean is warm, calm, and beautiful. (Okay, not so beautiful today with the algae toxins causing my lips and tongue to burn during and for a couple hours after my mile swim, but I'm sure -- I hope -- that will go away soon.)
*I MUST get swim lessons. Even though the thought of paying for one more expensive thing related to triathlon is one that I dread, it simply has to be done, and soon. The swim is my biggest weakness. Honestly, it has always been the possibility of not making the swim cutoff that has kept me from signing up for any triathlon other than a pool sprint. I am a slow swimmer, even though I can swim for a very long time without getting tired. I am pretty sure that a good coach would be able to help me speed up my swim just enough that I don't have to sweat making the swim cutoff in the race. The swim is 2.4 miles and the cutoff is 2 hours and 20 minutes, which is 3 minutes and 19 seconds per 100 yards. My swim pace right now is between 2:45/100 (ocean) and 2:55/100 (pool, probably because I'm so inefficient at turning at the wall that any momentum I gain from pushing off the wall is erased by the time it takes me to reverse direction and push off). While on paper it looks like I should make the swim cutoff, that does not allow for anything to go wrong, like choppy water or swimming extra yardage due to poor sighting in the water. If I could get it down to 2:20 or even 2:30, I would be happier. But just spending more time in the pool doesn't improve technique any. It just locks in poor technique. I will have to get a coach, and I sincerely hope that in my next Training Journal I will be able to report that I have one and am improving.
*I still hate everything to do with bike mechanics and maintenance. I still don't know how to change a tire, I still couldn't tell you how gear shifting works if someone offered me a million dollars to do so, I still freak out if I get a speck of grease on my hands, and I still have absolutely zero interest in getting better. BUT WHAT IF I GET A FLAT TIRE IN THE IRONMAN?!?! Well, then my race is over. I would rather lose $900+ than spend time learning to do something I hate when there is not even close to enough time in any day. Or, to put it another way, it is worth $900+ to me to give myself a pass on learning about bike maintenance.
*I really need a professional bike fit. My bike does not fit me. My position on the seat feels wrong, the pedals feel too high, the seat itself sucks, and I should be going 1-2 mph faster than I am. I am going to pay for that too rather than continuing to suffer through very long bike rides in discomfort.
*Getting comfortable riding on the road with traffic is a hardening process. I used to ride everywhere in Tucson. I was hit by a car once and almost hit a handful of other times, but I was still very confident riding in traffic. When I started road riding here after a break of several years, I was terrified for the first week or so. Terrified as in my heart was up in my throat when I heard a car coming from behind, even when I was on a wide road with plenty of shoulder. I am happy to report that that has almost completely gone away. People here think that I am nuts for riding my bike on the road because the bike lane in a lot of places is really, really narrow. In some places it's nonexistent, and I have to share the lane with cars. (However, I don't ride roads like that unless they are A) very lightly trafficked and B) have great visibility so cars can see me from far off and pass me.) A thousand or so road bike miles have convinced me that riding on the road is, for the most part, safe. I have never felt like an accident almost happened because a driver didn't see me. I have had drivers be rude jerks, and ride up on my ass and honk at me because they had to wait two seconds to pass due to another oncoming car, but if they honk at me, they aren't going to hit me. Too much paperwork. Let 'em honk. Sure I could be hit by a drunk or inattentive driver at any time, but ANYONE COULD. That's part of the risk of going out on the road. True, the consequences would be worse for me on a bike, but that is the kind of risk I'm willing to take in exchange for being outside and getting legs of steel and feeling the wind in my face. Helmet, lights, smart choices about where to ride, and yielding to drivers if I have any doubt as to whether they see me or not make me as safe as I can possibly be on the bike.
*A bike ride immediately followed by a run is called a BRICK. I don't know why. Some people say it's because bike+run=ick, some say that it's because you're stacking workouts together like you're building something out of bricks. I don't know the real reason. Bricks notoriously suck. Somehow my bricks have always gone really well. Despite the initial shock to the legs as they switch from one grind to another, I have never had a bad (as in slow) brick run. On Friday I rode 60 miles and then got off the bike and ran three miles. OF COURSE it sucked a little bit -- how could it not? -- but on the other hand, I knew those three miles were the only thing standing between me and an evening of rest and snacks, so I was highly motivated to get them done.
*Training for an Ironman has a huge impact on your significant other. This is my schedule for this week:
Monday: 2-hour swim
Tuesday: 1.5 hour bike ride, 1 hour 15 minute-run
Wednesday: 1-hour swim (my easy day!)
Thursday: 2-hour ride, 1 hour run
Friday: long bike ride -- 4-5 hours, followed by 3-mile run
Saturday: 2-hour run, 1 hour ocean swim
Sunday: 2.5-hour ride (and I will probably add another swim, just because I suck so bad at it)
That is over 20 hours of training per week, like taking on a half-time job. And it's not like that is all the time it takes. I also have to drive to all these things, assemble gear for the bike and swim, and clean gear afterwards. Naturally I have to start all my weekend workouts very early before it gets hot. (Not that anything could make the long ride not-hot -- unless I did it at midnight.) So the answer to "What are we doing this weekend?" is always, "working out then sleeping." Ironman training is profoundly selfish. I am very, very lucky to have Will. When he's home, he helps me as much as possible. He will drop me off or pick me up somewhere so I don't have to ride a boring loop. He packs his Yeti cooler with fuel for me. He never complains about the fact that we never get to watch a sunrise together or have a lazy Sunday morning sleeping in. I'm always too tired to do anything fun when I'm not working, and I never have extra money because all of it goes into this insanely expensive and stupid hobby that I wish had never ended up on my bucket list. I feel very sorry for anyone whose partner decides to do an Ironman. In fact, if I were dating, someone training for an Ironman would probably be disqualified just for that reason! I really appreciate Will, is what I'm saying.
I'm eager to see how the next month of training goes. Hopefully I will open my next training journal with "I got a swim coach and I got a bike fit!"
I've registered for, and bailed on, two half-Ironman distance races in the last 10 years. One was the Soma 70.3 in Arizona, which I quit because I didn't want to work on my swim, and the other was the Steelhead 70.3 in Benton Harbor, Michigan, which I quit because I started to dread the training schedule so much that the dread took over my life. Plus, I didn't like the thought of swimming anywhere in Michigan. The Lifetime pool was always too cold, lakes are gross and also too cold (except for maybe a few minutes in July) to swim in without a wetsuit, and wetsuits are expensive. There was nowhere to ride my road bike except Stoney Creek and Kensington Metroparks, nothing pretty to look at, and for more than half the year I was freezing anywhere except the gym. I thought some of those things would be fixed by moving to Florida, but in all honesty I wasn't sure I wouldn't grow to hate the schedule just as much as I did in Michigan. Even if I did, though, I was pretty sure that the OVER $900 REGISTRATION FEE would keep me from bailing on the training.
I have now finished 7 weeks of the 20-week schedule. Although there is still a lot of time left for things to go south, I am happy to say that I haven't missed a single workout so far, and am thriving on the schedule. I'm not always dying to start every workout -- see above -- but it's never THAT hard to just do it. I've learned a few things along the way too.
*I can swim in the ocean! I have played in the ocean before, but swimming in it was a completely new experience. I really didn't know what to expect. A lot of bad swimmers are terrified of the open water swim (OWS), and some people even get nauseous in the waves. From the moment I started swimming in the ocean, I loved it. It is like a giant, bath-temperature swimming pool where you never have to worry about getting a lane and the lanes stretch out to infinite lengths. Some oceans might be cold and rough and intimidating, but MY ocean is warm, calm, and beautiful. (Okay, not so beautiful today with the algae toxins causing my lips and tongue to burn during and for a couple hours after my mile swim, but I'm sure -- I hope -- that will go away soon.)
*I MUST get swim lessons. Even though the thought of paying for one more expensive thing related to triathlon is one that I dread, it simply has to be done, and soon. The swim is my biggest weakness. Honestly, it has always been the possibility of not making the swim cutoff that has kept me from signing up for any triathlon other than a pool sprint. I am a slow swimmer, even though I can swim for a very long time without getting tired. I am pretty sure that a good coach would be able to help me speed up my swim just enough that I don't have to sweat making the swim cutoff in the race. The swim is 2.4 miles and the cutoff is 2 hours and 20 minutes, which is 3 minutes and 19 seconds per 100 yards. My swim pace right now is between 2:45/100 (ocean) and 2:55/100 (pool, probably because I'm so inefficient at turning at the wall that any momentum I gain from pushing off the wall is erased by the time it takes me to reverse direction and push off). While on paper it looks like I should make the swim cutoff, that does not allow for anything to go wrong, like choppy water or swimming extra yardage due to poor sighting in the water. If I could get it down to 2:20 or even 2:30, I would be happier. But just spending more time in the pool doesn't improve technique any. It just locks in poor technique. I will have to get a coach, and I sincerely hope that in my next Training Journal I will be able to report that I have one and am improving.
*I still hate everything to do with bike mechanics and maintenance. I still don't know how to change a tire, I still couldn't tell you how gear shifting works if someone offered me a million dollars to do so, I still freak out if I get a speck of grease on my hands, and I still have absolutely zero interest in getting better. BUT WHAT IF I GET A FLAT TIRE IN THE IRONMAN?!?! Well, then my race is over. I would rather lose $900+ than spend time learning to do something I hate when there is not even close to enough time in any day. Or, to put it another way, it is worth $900+ to me to give myself a pass on learning about bike maintenance.
*I really need a professional bike fit. My bike does not fit me. My position on the seat feels wrong, the pedals feel too high, the seat itself sucks, and I should be going 1-2 mph faster than I am. I am going to pay for that too rather than continuing to suffer through very long bike rides in discomfort.
*Getting comfortable riding on the road with traffic is a hardening process. I used to ride everywhere in Tucson. I was hit by a car once and almost hit a handful of other times, but I was still very confident riding in traffic. When I started road riding here after a break of several years, I was terrified for the first week or so. Terrified as in my heart was up in my throat when I heard a car coming from behind, even when I was on a wide road with plenty of shoulder. I am happy to report that that has almost completely gone away. People here think that I am nuts for riding my bike on the road because the bike lane in a lot of places is really, really narrow. In some places it's nonexistent, and I have to share the lane with cars. (However, I don't ride roads like that unless they are A) very lightly trafficked and B) have great visibility so cars can see me from far off and pass me.) A thousand or so road bike miles have convinced me that riding on the road is, for the most part, safe. I have never felt like an accident almost happened because a driver didn't see me. I have had drivers be rude jerks, and ride up on my ass and honk at me because they had to wait two seconds to pass due to another oncoming car, but if they honk at me, they aren't going to hit me. Too much paperwork. Let 'em honk. Sure I could be hit by a drunk or inattentive driver at any time, but ANYONE COULD. That's part of the risk of going out on the road. True, the consequences would be worse for me on a bike, but that is the kind of risk I'm willing to take in exchange for being outside and getting legs of steel and feeling the wind in my face. Helmet, lights, smart choices about where to ride, and yielding to drivers if I have any doubt as to whether they see me or not make me as safe as I can possibly be on the bike.
*A bike ride immediately followed by a run is called a BRICK. I don't know why. Some people say it's because bike+run=ick, some say that it's because you're stacking workouts together like you're building something out of bricks. I don't know the real reason. Bricks notoriously suck. Somehow my bricks have always gone really well. Despite the initial shock to the legs as they switch from one grind to another, I have never had a bad (as in slow) brick run. On Friday I rode 60 miles and then got off the bike and ran three miles. OF COURSE it sucked a little bit -- how could it not? -- but on the other hand, I knew those three miles were the only thing standing between me and an evening of rest and snacks, so I was highly motivated to get them done.
*Training for an Ironman has a huge impact on your significant other. This is my schedule for this week:
Monday: 2-hour swim
Tuesday: 1.5 hour bike ride, 1 hour 15 minute-run
Wednesday: 1-hour swim (my easy day!)
Thursday: 2-hour ride, 1 hour run
Friday: long bike ride -- 4-5 hours, followed by 3-mile run
Saturday: 2-hour run, 1 hour ocean swim
Sunday: 2.5-hour ride (and I will probably add another swim, just because I suck so bad at it)
That is over 20 hours of training per week, like taking on a half-time job. And it's not like that is all the time it takes. I also have to drive to all these things, assemble gear for the bike and swim, and clean gear afterwards. Naturally I have to start all my weekend workouts very early before it gets hot. (Not that anything could make the long ride not-hot -- unless I did it at midnight.) So the answer to "What are we doing this weekend?" is always, "working out then sleeping." Ironman training is profoundly selfish. I am very, very lucky to have Will. When he's home, he helps me as much as possible. He will drop me off or pick me up somewhere so I don't have to ride a boring loop. He packs his Yeti cooler with fuel for me. He never complains about the fact that we never get to watch a sunrise together or have a lazy Sunday morning sleeping in. I'm always too tired to do anything fun when I'm not working, and I never have extra money because all of it goes into this insanely expensive and stupid hobby that I wish had never ended up on my bucket list. I feel very sorry for anyone whose partner decides to do an Ironman. In fact, if I were dating, someone training for an Ironman would probably be disqualified just for that reason! I really appreciate Will, is what I'm saying.
I'm eager to see how the next month of training goes. Hopefully I will open my next training journal with "I got a swim coach and I got a bike fit!"
Subscribe to:
Posts (Atom)