Talk about getting the weekend off on the wrong foot today! My little band of running partners and I have something of a tradition when it comes to celebrating each others’ birthdays. We have a great local bakery that makes the most incredible cakes. Every couple of months when we have a few birthdays close to each other, we meet at the bakery, do our long run, and then come back for birthday cake. Yeah, I know, kind of incongruous, but it’s fun.
So our plan for today was for the majority of us to meet up at 6 a.m., get in three or so miles and swing back by the bakery to pick up the rest of the crew for another 10 miles. I was looking forward to this run all week. My alarm clock, however, had other ideas. Maybe it thought I didn’t need cake, I don’t know. But suffice it to say that I didn’t wake up until 6:25, and not to the sound of my alarm. What the heck!
I jumped out of bed and began scrambling to get my running clothes on. I drove over to the bakery, making it there by 6:50. Started heading off in a random direction because I wasn’t sure exactly what route my pals were running. Luckily, a few minutes into it I ran into two of the girls because they had to finish up early. One drove me to where she guessed the rest of the group might be at that point and I jumped out to join them. I was happy for the company, that’s for sure. But I only ran about seven miles, I’m guessing, which means I now need to move my long run to tomorrow morning. I hate running long on Sundays–not only do I miss out on kicking back a bit tonight when it comes to food/wine, but I need to get up very early so that I can get the run in and make a 9:00 church service.
As much as I’d like to blame my alarm for the mishap, I’m pretty sure it was my human error that caused it. I was talking to my husband last night as I set the alarm, and it looks like I set it for p.m., not a.m. Grrrr.
Anyone else have a bad alarm story? Ever happened on a race day?