This is the story of the weekend long run that was supposed to happen but never did.
Before I went to bed Friday night I did what I always do. I gather all of my stuff and put it in piles so I didn't have to hunt around in the dark for that random pair of running tights or my Road ID or figure out why my Garmin wasn't turning on.
Note: If you find yourself with a fully charged Garmin that refuses to turn on, plug it into the computer and press reset and mode for 10 seconds. This "soft reset" should work. It did for me. And yes, I realize everybody probably knew this trick, but I was the one freaking out and scouring the Garmin website at 11:30 p.m. Friday night.
My Friday ritual included setting the alarm for 6:15, which would give me plenty of time to get dressed and head out to Plamann Park to meet up with my running group.
Except there was a problem. My alarm either never went off or I've gotten really good at turning it off in my sleep. Because when I woke up it was light out and the clock was reading 9 a.m.
After posting a status update on Facebook - because everyone really needs to know I slept through my alarm and missed my long run - and answering a few Facebook messages that were worried why I wasn't at the group run that morning, I got up and got ready for the day. I could have done the 5-6 miles I needed to do solo, but I had to head over to a friend's house and help him pack a moving truck. I there until dark and then needed to go to a benefit for a family friend's son who's got some kind of tumor on his brain.
So there were plans to do it today. When I got up I didn't feel like running, so I told myself I'd do it after the Packer game. And, well, as I'm sure you've all heard, the perfect season is no longer. And I really wasn't in the mood to run after watching the Packers play like poo and loose to the Kansas City Chiefs.
So I didn't run. And that, my friends, is the story about this weekend's long run that never happened.