A comedy of errors

I ran with Murphy today. He was there from the moment I decided I was really going to venture out into the icy cold rain and howling wind. He made sure I followed his law.

My iPhone GPS was acting up again. I did my best to get it to come to an understanding of where I really was, but if you look at the map on RunKeeper, you’ll see that it got very lost along the way. I’m not really sure how it can get so confused so often. I’m hoping it has something to do with interference from the rain, but I’m not very impressed with it to say the least.

My drawstring broke. My shorts dropped. I fell to the ground. My phone buzzed with text message after text message until I thought someone was desperately trying to get in touch with me. I accidentally paused RunKeeper for a few seconds trying to figure out who was texting me so much. It turned out to be text spam. I hate text spam. I did figure out how to resume RunKeeper, but it wasn’t pretty.

30:13

When I used to complain about the weather in high school, my swim coach would say something like, “It’s sunny somewhere else right now, where your competition is training. You may choose not to train today, but when you meet him, he will beat you.” That’s why I decided to run today, and that’s why I kept deciding to keep running each time I wanted to call it quits today.

No Audio Cues

The weather was really nice Monday evening, so Charmaine and I took our bikes out for a little spin. We did our short route, which takes us up into Alpine, over to the road that goes up to Suncrest, and then back home. It’s only 16 miles with very little climbing, but it’s really fun. I always ride with my phone, so I decided to try RunKeeper on the ride. I don’t listen to music while I ride, and I didn’t want the phone telling me I was on or off pace every five minutes, so I disabled the audio cues. Charmaine has a Garmin 705, but I just have a simple bike computer, so I thought it would be cool to have additional data. It was cool. I’ll definitely do that again.

Today I got all excited, thinking I was somehow way ahead of my pace when I made it all the way to the park at the center of The Cedars without hearing the voice tell me how far ahead or behind I was. Soon it was obvious that I had no idea if I was on pace or not. The further I got from where I normally hear the audio cue, the more I wondered what was wrong. Eventually I remembered that I had disabled the audio cues for biking. I wish I could set it differently for different sports. Knowing that I had no idea if I was ahead or behind was a little discouraging. I remembered thinking how much time I cut off the first time I used RunKeeper with the audio cues. I figured I better just push myself hard and see what happens.

I knew I wanted to improve my pace going up the big hill right after the 2 mile mark, so I focused on that. I think I did alright, but I was still dead by the time I hit the top. I pushed myself through mile 3, but I was obviously off my pace by quite a bit. I finished the activity and wrote some notes on my phone before I had any clue how I had done. I actually thought I had done much better than I had, which you can tell from my notes.

30:25

I guess those audio cues make a bigger difference than I thought. I’m turning them back on right now.

Died on the hill again

I didn’t run last Friday. It was snowing, the wind was howling, and it was really cold outside. Plus, I thought I may wind up going skiing again on Saturday, so it was easy to justify not heading out into the blizzard. I had no convenient excuses today. The sun was out, the snow was gone, the wind was calm, and I didn’t end up skiing, so my legs were fresh. It was the perfect day to be outside.

I started out great. I felt good going up the hill by the church and all the way through The Cedars. I hit the 2 mile mark at 18:42, but then I died on the big hill into the last mile. I need to figure out how to get my butt up that hill a little faster. I spend way too much time there. I also need to figure out how to have some energy left to bring it home after I get up that hill. I did manage to finish the last mile at a respectable pace, but I know I can do better.

29:44

I think I could have done a fourth mile today, but only if it was completely flat, or slightly downhill. Maybe it really is time to start thinking up a longer route.

Spinning my wheels

Last night Charmaine and I rode our trainers for an hour. I took it somewhat easy, knowing that I had to run today. I felt pretty good afterwards and good again this morning. I’m still not sure if that played into my terrible performance today, but I don’t have a lot of other excuses, so that’s what I’m going with.

Wanting to avoid another confusing map in RunKeeper, I decided to make sure my iPhone believed I was starting from the right spot. Nope. It thought I was about a half mile away again. I had to fight with it for about ten minutes to convince it I was here and not there before starting my run. Maybe that played into my difficulty?

Excuses aside, I felt pretty good starting out, but by the time I hit the first corner I realized that my cadence was too high and my stride was too short. In other words, I was just spinning my wheels and not really going anywhere. I tried to step it up a bit going up the first hill, but my suspicions were confirmed at the 5 minute mark when RunKeeper announced, “You are behind your target pace by 14 seconds.” That wasn’t nearly as motivating as finding out I was ahead of my target pace. I tried to push it after that, and I did get ahead of my target pace for a bit, but that last mile just took me apart. Still, I’m happy to have finished with a decent time.

30:09

Maybe I’m not quite ready to add that 4th mile.

Not an exact science

I was at the Apple store last week and picked up what I thought was the ultimate solution to having my phone bouncing around while I ran: the incase Sports Armband Pro. I was so wrong. The strap is about 4 inches too short to go around my arm. As much as I have joked over the years that my biceps were “21-inch pythons”, they’re really not. I just measured my left arm. It’s only 16 inches around. I am shocked and disappointed that an accessory company would cut corners, making their product only fit the arms of small women and children. I’m not impressed.

As cool as RunKeeper can be, it’s far from being an exact science. Take a look at the map it generated for my run today. It says I started about a half mile from home (where I actually started), then I ran through houses and fenced-in yards before I finally got on track. I guess it’s more the fault of the GPS in my phone than RunKeeper, but it’s still sort of frustrating.

Despite the incorrect GPS data for my run today, I’m still happy enough with the end result. I started off pretty fast, trying to make up some time on the initial hill climb into The Cedars. I think I was faster (no way to know, since the GPS data is all screwed up), but then I was hurting the rest of the run. I still managed to come in under 10 minutes, which is my second best time, so I’m happy. Even though I can’t trust the route or distance data from RunKeeper, I can at least trust the time.

29:34

I’m not quite ready to add that next mile onto my route, but I’m getting closer every day.

RunKeeper

I have seen various different workout tracking applications for mobile devices, for social media, and on stand-alone websites. I haven’t ever been impressed with any of them. I have even had discussions with friends about making one that would be worth using. None of us ever did anything about it, and it looks like we won’t need to. Lately I have been seeing a lot of Facebook news items from friends using RunKeeper.com, so I figured I should check it out. I like it. It’s completely free to use. There seems to be some advanced features that you can subscribe to, but I can’t imagine what they are, because I have everything I want already with their free offering.

They have a website and a mobile app that work together. The iPhone app uses the GPS in your phone to track your location, elevation, and pace as you run. It can even talk to you to tell you if you’re on pace or behind. The only drawback is that you have to run with your phone. I don’t have a great way of keeping my phone with me while I run. I put it in my pocket and ran earbuds out of my pocket. There were two little problems with this setup: 1- I kept pulling my earbuds out of my ears when my arm would accidentally catch the cord as I ran and 2- the weight of the phone in the pocket of my shorts kept pulling my shorts down as I ran. I think I can solve both of those problems.

In the mean-time, I am very happy with RunKeeper. I set my target pace for 10:00 minutes per mile and told it to update me every 5 minutes. As I crossed the 5 minute marker, it told me I was exactly on my pace target. That motivated me to run a little faster. By the 10 minute mark I was ahead of my target pace. I stayed ahead the rest of the run, despite slowing way down on the big hill coming up Ironwood. The best part about RunKeeper is that you can see exactly how I ran today. And if you join my “street team” you can even see the map and trace my route. It’s really slick.

29:30 (click my time to see my activity on RunKeeper)

It seems that little bit of motivation goes a long way. I think this makes 5 best times in a row. Amazing. Now I have a dilemma. I told myself when I started breaking 30 minutes I would add another mile to the run. I guess it’s time to start thinking about a new route.

Catching a break

There was a lot of snow and hail over the weekend, but it looked nice outside this morning. I was happy to not have to run in the snow again. But around 11 the clouds rolled in and it started raining, hailing, and snowing again. The wind was blowing hard. I looked at the radar and it seemed the storm would blow over by about 1. At 1:30 it was finally clearing up, so I headed out. The wind was still strong and cold, but at least it wasn’t wet.

I started off fairly strong and seemed to keep it up through the first two miles. I even went fairly quickly up the big hill on Ironwood and Sycamore. When I rounded the corner at the top of Sycamore onto Sandalwood it all started to fall apart. I fell into a 1/3 breathing rhythm, which felt very wrong. It wasn’t long until I had a side ache. I tried to get my breathing back in line, but it was hard. I finally found a 2/2 rhythm as I headed down the last hill, and snapped back into a 2/3 going up the other side.

As I headed around Mesquite, I figured I was still on track to set a new personal best. I was right.

30:37

That’s going to be tough to beat. Up to this point, there have been obvious areas for improvement, but there are less and less of those. It’s definitely going to be interesting to see what happens next.

Battling the blizzard

It’s cold outside. It’s been snowing the past two days. When lunchtime came today, I looked out the window. I saw a blizzard. I couldn’t even make out the outline of the mountain we live next to. The snow was heavy and wet. I didn’t want to go outside, but I didn’t have a good alternative plan. So I got dressed in my shorts and t-shirt and realized that wasn’t going to cut it. I added a sweatshirt and a hat. That seemed just about right.

I knew the sweatshirt was much heavier than the light-weight sports shirt I normally wear running, so I figured I would wind up a little more tired at the end than usual, but nothing too extreme. As I ran, the snow piled up on the sweatshirt and hat. I was nice and warm inside. Unfortunately, that made most the snow on the sweatshirt melt, which made the sweatshirt even heavier. My shoes were also sopping wet and a little heavier than normal. I think the worst part was the snow. It was blowing around and seemed to fly into my eyes no matter which direction I headed.

I told myself I would find a way to just plow through it. I would be slow, but I would make it. This would be three days in a row with no walking. That would mean something. When I got to the big hill on Ironwood, I wasn’t sure I would make it. My breathing switched from 2/3 to 2/2. I found a way to get to the top, but I didn’t seem to be catching my breath. I was on the flat, but I was still stuck breathing a 2/2 rhythm. I was hurting. I slowly worked my way back to a 2/3 by the time I was heading down the last hill. I stayed at 2/3 back up the other side and onto Mesquite. I finally started feeling good as I rounded Mesquite and headed home.

31:02

Something magical must be happening. There’s no reason I should have been that fast today. It was a battle almost the whole way. I guess I’m glad I fought that battle. That’s three best times in a row. And that’s the first time that has happened. I just hope the weather clears up and I’m able to run without the extra gear.

Going through the motions

My legs were sore yesterday. I started talking about possibly taking a few days off from running to let my legs recover. I thought I was serious, but somehow I found myself running again today. I didn’t particularly want to run today, and I especially didn’t want to push myself too hard. It is absolutely beautiful outside today, and I wanted to spend some time outside enjoying it. I thought about taking a ride on my scooter instead of doing my daily run. I thought about just walking the route to enjoy the great weather. But in the end I decided to run.

I started off slowly and never really picked up the pace. I kept telling myself that I didn’t have to run too hard, because I was going to run the whole loop again today, and that would make up for not going fast. I knew that wasn’t the ideal situation, but I figured it was fine, since I was at least out there running. I kept thinking the loop will get easier each time I do it. I don’t think I realized how much truth there was in that thought until I finished and looked at my time.

31:15

How did that happen? I didn’t run hard. I didn’t push myself. I barely even picked up the pace for the home stretch. So how did I get my best time yet? I’m still a bit confused about it. Maybe I should just go through the motions more often?

Full-combo finish

When I opened the door to see how warm it was today, I got blown back inside the house. The wind was really strong. So I looked up the weather forecast for today… heavy wind, rain, and snow… continuing for most the week. I had been toying with the idea of signing up for the “Ice-breaker” triathlon this weekend, but there’s no way I’m biking and running in rain and snow at 25 degrees while I’m soaking wet after the swim portion. At the same time, I realized my chances for running this week may be diminished, so I better hurry up and get out there.

I knew I had to run the whole loop today. I knew it as soon as I wrote it last Friday. I thought about that a few times this weekend. I was worried that it would be extremely difficult to pull off. It wasn’t. Running up the last bit of the hill on Sycamore wasn’t any more difficult than walking had been. Continuing to run along Sandalwood was a little tougher, but I was able to regain my rhythm after a house or two and then it was just a fun run to the finish line.

31:19

My tradition of setting a new record each Monday continues.