Kailee's Run

Sunday morning was Kailee's Run - a 5K fund raiser to benefit Tracy's Kids who have helped Kailee, a member of our church, in a battle with cancer.

It turns out that walking 7 miles around DC sight-seeing yesterday was a pretty good warm up for running in the 5K this morning. I set a new PR at 29:16 - nowhere near the front of the pack, but a darn good time for me.

Segway into related topic... you'll see the connection in a few minutes.

I think maybe I'm just cursed when it comes to electronic gadgets.

You don't have to scroll back very far in my blog to find a couple of common themes - an obsession with high-tech electronic gadgets... and an element of frustration and banging my head against the wall when said high-tech electronic gadgets don't work right.

No, I'm not going to regale you with more stories of my BlackBerry woes. Although I will say that my wife got the same BlackBerry that I did the same day that I did (buy one get one free promo). We use pretty much the same applications on them, too, and she doesn't seem to have the same problems I have with her BlackBerry. Maybe it's just me.

Okay, so yesterday we went to do our sight-seeing trip around DC. I wore my Garmin Forerunner GPS watch to keep track of the mileage we walked. When we got out of the car at the Iwo Jima Memorial, I looked at my watch to see what time it was. The watch said 9:16:50... I said to myself, "Self, I coulda sworn we left the house about 9:15, did we travel back in time?" In the time it took me to ask myself that question, I noted that the seconds didn't budge.

Yep, my super-whamodyne fancy high-tech GPS watch read 9:16:50 the ENTIRE day.

I tried looking for a reset button somewhere but found none. I tried pushing and holding one or both buttons for multiple seconds to see if that did anything. Nope, nada, zip, no response.

When we got home from sight-seeing, I went on the Garmin website and looked up the trouble-shooting guide. In order to do a factory reset, first you have to hold BOTH buttons for 6 seconds then LET GO of the TOP button for 3 seconds. Gosh darnit, why didn't *I* think of that???

That worked.

Then it beeped at me and told me the battery was low.

Nice.

No, it didn't really matter by that point, it just seemed to add insult to injury. No worries, I put it on the charger last night to get it fully charged before the 5K this morning.

Everything started out fine on the 5K, but it was sprinkling rain. Over the course of the run, it grew to a deluge of rain and I was SOPPING wet by the end.

Kailee's Run in the Rain

The Garmin Forerunner uses a cool touch-screen type of display where you touch the corners of the bezel to activate different functions.

Well... it doesn't work so well in the rain.

The water pretty much shorted out all four corners of the bezel. The entire run, the watch was beeping at me as the rain was causing it to go into all sorts of different sub-menus and activating all sorts of obscure work-out programs and options. I had NO control over it. When I actually touched anywhere on the bezel with my finger, it didn't respond at all.

The RAIN was in control.

Normally, my watch tells me how far I've run and what my pace is. This morning, I couldn't get it to go back to the display that told me how far I ran or what pace I was running, so I had no clue for the duration of the race.

So I just ran.

No idea what my pace was. I just ran at what I thought was a comfortable steady pace that I could maintain to the finish line.

It still recorded the data though, and I was able to download it when I got home. When I got home and looked at my pace and my time on the computer screen, my jaw dropped. I routinely jog 3 miles around Ashburn on my own, and I usually finish in about 30-33 minutes or so. Today I hit the 3 mile mark at 28:27 and I finished the 5K at 29:16. That averages out to about a 9 1/2 minute/mile pace, which is pretty darn good for me.

I still think maybe I'm just cursed with (a) an obsession with electronic gadgets and (b) very bad luck with getting them to work right.