«

»

The higher target range

Over the past week or so I’ve been complaining about having a week of really piss poor eating. I think at some point, in my Internet food tracking tool I indicated that I was planning on burning a hell of a lot of calories this week. It’s a fair assessment given how far my running distances are becoming, and how much extra stuff I’m starting to incorporate. With that info, the site tweaked my target ranges to be higher. This is supposed to ensure that I have energy to keep my activity levels going at a good level or performance. With the newfound room, I’ve been eating more–no problem there. The danger is that, in eating more it seems like I’ve been sailing over the target all to easily. I might plan to do A and B, but somehow I’d throw in C and D on top of all that. Doing that once in a while isn’t bad. However, doing it multiple times in a week is throwing up red flags in my head. I’ve been bloated several days this week.

The extra food isn’t entirely deadly, if only because I’ve truly been exercising more. Still, it’s an odd feeling considering that I’m on the right track. I have to be careful when people I know tell me “oh, don’t worry, you’re training for a marathon!” That may be, but that doesn’t give me free licence to eat freely. I need to be a bit more judicious with my choices. Yes, today’s stop be the Korean Grill House was awesome, but did I really need to eat all of that meat?

Anyway, I’ve readjusted the tracker once more, and that brought the calories back to a lower range. Starting on Sunday I’m going to go back to watching and tracking properly. It’s the only way I’m going to feel good. This week is done and over, and I had fun, but it’s time to focus again.



Possibly related posts:

  1. “Chance now to climb higher”

About the author

Jay

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Switch to our mobile site