That was me, last weekend. Or perhaps more accurately, that was my body, rebelling against my will. After coming off of a--dare I say--good 18-miler in the previous weekend, I had only to complete a 12-mile long run. I did my normal Friday night prepping and set four alarms for early Saturday morning. When those alarms went off, I heard them, but I chose to ignore them. I can't tell you what I thought in that moment, except that I wanted to sleep more than I wanted to run. But it's never about wanting  to run for me; it's about having the strength and will to do something important for myself. So the fact that I ignored all four alarms that morning was, frankly, alarming to me. But I carried on with my Saturday with a plan to do the run in the evening. I set out at about 7:45pm, when the sun was nearly set, and I began my journey. I was feeling fine until about 1.5 miles in, when the humidity started to get to me, and my legs started hurting. I had experienced this befor...

It's 2:30am. I cannot sleep. I cannot sleep because I decided to do my long run at 8:00pm, which, after all of the several-minute water breaks were factored in, turned into a nearly 3.5-hour run. Two things that I always thought should happen after a long run but still never do: I get hungry, I get tired. I look at the calorie burn on my RunKeeper app, and I see that I've burned 1,709 calories. That's some people's daily intake of calories. This makes me think I should be hungry. Yet, I'm not. My stomach feels so tight and full from water that food is actually repulsive immediately after a long run. But I eat anyway, for recovery purposes. Tonight I had half of Greek yogurt cup (protein), half of a banana (potassium, carbs), and a large bowl of cereal (just because I love cereal, and I thought it might be good; it was, until my stomach hurt afterward). But I'll rectify this matter by making up the deficiency tomorrow. In case you were worried. But what's...