Friday, March 7, 2014

Today's SCID Post

Rest & Relaxation

Where I've gone wrong in the past: too many consecutive days of running. Granted, the type of running matters too, and in what context. For example, running 5 times a week when the past 6 months have been sedentary. Bad idea.

I was never a coached runner, but I've read and heard about "workouts" which from what I understand generally refers to the non-junk miles days where you actually focus on a specific pace. Don't do two days of workouts back to back. That's where recovery days come in. Save those rest days or easy pace runs for the day after a workout (in my case this is either intervals, a long run, or a full-effort 5-10K. It's also a good time to do non-running fitness activities such as core, weight training, poodle grooming, and the like.

Gradually increasing mileage and number of days run is also sage advice. I've seen percentages thrown around, but that seems really arbitrary to me. The number of miles probably doesn't matter as much as how they are run. At any rate jumping from 10 mile weeks to 30 mile weeks is asking for trouble.

What happens if you overtrain? From my experience-injuries. I've experienced 3 major injuries that all came down to the "too much too soon" principle. Shin splints-running in Vibram Five Fingers 20 miles a week on pavement. Achilles tendonitis-probably from amping up mileage in zero drop shoes too quickly. Patellofemoral pain-running with weak legs. This one used to really scare me. Since I've strengthened my legs, I have very little knee pain. Leg strength takes time and for me lots of lunges, squats, and using the stairs all day at work.

Sunday, February 16, 2014

SCID Installment #1

Sometimes I get solicitations for running advice, which I feel dumb giving. What seems more appropriate is sharing things that have not worked for me or have simply gone horribly wrong. And thus what will be a recurring segment: SCID (stupid crap I've done).

Meal Timing

There was a time where I ran with reckless abandon. Eat bacon & eggs, run 5 minutes later. Eat a giant "carb load" meal the night before a big race. I don't do those things now because I would prefer to not have to be in constant vigilance that I don't load my drawers mid-run. Let's cover some basic physiology first: it takes your stomach about 2 hours to empty. Running with a full stomach is uncomfortable and for me causes crippling sideaches. I don't know the mechanisms behind this, whether it's from my gall bladder squirting out digestive enzymes or the clash of sympathetic and parasympathetic nervous system responses. Whatever it is, it doesn't jive, y'all. After two hours I'm almost always good from a sideache perspective.

The dookie situation is interesting. I've found there's no predictable formula for "eat at time x, meal transit time through gut=x+y. Drop deuce at time z. Lather, rinse, repeat." BMs seem to be more of a circadian thing for me, irrespective of meal timing for the most part (unless Taco Bell is involved, then formula becomes "eat chalupa at time x, endure stomach cramps at time x+5 minutes, fumigate lavatory at time x+5.2 minutes"). Meal size, however, is an important trigger for laying cable. My new formula, that I have yet to find unsuccessful is: wake up early, eat medium size breakfast, large glass water at time x, await inevitable dook at time x+0.5 hours. This has been a vital tidbit to help avoid "messy" situations on long runs.

Runner's Trots are pretty crappy. Having the urge during a race I think is avoidable by following the morning meal rule. But even if the staging area is clear at race time, what about that "carb load" meal from last night still meandering through 30 feet of entrails? This has come back to haunt me (if ghost are apt to haunt one's bowels) at the end and after runs, where I'm writhing in pain as my body rejects the previous night's meal. (Don't ask how I can be sure it was the previous night's meal). So that age-old advise to eat a bunch of pasta before a race? Bad idea. In general, it's just a bad idea to do anything you wouldn't do during training for a race. That's a recipe for surprises. And in this case "surprises" is a euphemism for diarrhea which may or may not be disposed of in a socially acceptable way.

TMI you say? I learned the hard way so you don't have to. Take heed.

Sunday, February 2, 2014

Tybee Run Fest Half Marathon Race Report

Final time 1:37

Very happy with that. Yesterday everything came together in ideal fashion and the end result is better than I expected.

The running community is full of advice. Nearly all of the advice is based on personal anecdotes from people with a broad range of experience levels. I've never really known what to do with all the running information out there, so I've tried a lot of different things. After much ongoing trial and error, I have developed the following rule of thumb for what advice is worth my attention.

-Listen to people that have more experience than yourself. Conversely, take with a large grain of salt any advice from less experienced runners. Unfortunately, it is the latter who are often the most vocal.

One of the most measured sources of running information I have found is Written by a former college professor turned full-time running blogger, the perspective resonates with my own. The author was not always a runner and approaches running objectively or discloses his personal biases when he doesn't.

Why do I mention this? Yesterday was a big milestone for me. All the advice I've taken and personal experience from the past 10+ years of running are starting to congeal. Some lessons learned that were made manifest yesterday:

1) Race infrequently. I've made the mistake of signing up for races every month before. And I've done poorly and injured myself as a result. Racing is hard on the body. I push myself much harder in a race than when I am training. That kind of effort is not sustainable physically. Now I race less and train more.

2) Eat for runs >5-6 miles. I like gels because they digest very easily. Yesterday I had a gel right before starting and about 40 minutes in. Additionally, it takes about two hours for your stomach to move a meal on to greener pastures, so I eat two hours before race start. Both of these points have made an enormous difference in my running. Bowels move at the right times (pre-race) and sideaches are a rare occurence as long as eating during the race doesn't outpace use of the food. Unfortunately, there is no hard rule I've found for this. Every run I go on I have to gauge how much and when to eat based on how much I'm sweating and whether or not my stomach is sloshing.

3) Pace is key and without form, pace is unsustainable. Running well is a skill. Anyone can move quickly (well almost anyone). Running sustainably takes deliberate adjustments to and awareness of cadence, posture, footstrike, arm movement, breathing, and knowing when to push and when to ease off. Cadence was the name of the game yesterday. Normally, I'm the guy falling apart at the end of a race. This time I was flying past everyone the last 5 miles. I would catch up to someone, they would try to match my pace taking longer strides and making significant effort to run "harder" I would move my legs faster and inevitably drop them when the two techniques were put head-to-head. Posture is a big deal too. As I've done regular core stregthening workouts, I can keep good posture through longer runs.

4) Train to end strong. Negative splits have been a big focus in my training. I used to go out hard and just hope that I could hold on to the pace. This technique works sometimes for shorter races (5K, 10K), but it has come back to bite me on long runs. It's a great way to injure myself and feel discouraged. Long distance running is a matter of sustained pace. Ending strong doesn't mean sprinting the last 100 yards. If you can sprint at the end of a race, you have clearly not allocated your efforts optimally. I finished at about a 6:45 pace for the last mile and literally could not have gone any faster. I spent all my energy to sustain my pace for 13 miles and no more.

5) How and what you eat matters. There is a really ignorant idea floating around that if you exercise enough, you can eat whatever you want. You'll just burn off the calories. This is what I like to call excrement. In America, meals are traditionally three times a day and they are large and carbohydrate rich. This is not compatible with an active lifestyle. I had an epiphany while doing a 50 mile hike on the Appalachian Trail last summer when I was eating small meals every couple hours all day long and then a bigger meal at the end of the day. It seemed very counterintuitive to eat that way as the 3 meals paradigm was well engrained (pun intended). It seemed like I would starve snacking on granola bars all day. Here's the thing: I didn't starve. I had energy all day, no sideaches, and actually felt good. Turns out my idea of a meal was really more of a binge. The "snack" is my new meal and I've lost 15 pounds of superfluous swelling and fat. I eat high protein, high fat "snacks" all day every 2 hours on the hour and I feel awesome. High carb foods I save for running. The American diet is a great way to spike your blood sugar and tell your body to store fat and be tired. Not great for anyone trying to get out and run regularly. I won't be going back after 30 years of that nonsense.

There's my contribution to the vast wells of running opinion out there. It's a work in progress, but I'm glad there has been significant progress for me. I had a lot of fun racing yesterday.

Monday, January 20, 2014


The past few weeks I had some type of disease. I think it was the flu. It decimated me for a good 48 hours. Recovery and feeling well enough to run took longer. And thus, training runs fell apart. I've run when physically able. With 12 days left for the Tybee Half, I needed to fit in my final long run before the race. I got off of work and started running, planning 13.1 miles at race pace. I felt pretty peppy to begin, but was unable to hold the pace like I could a few weeks ago. My 7:30 miles started pushing up to 7:45 range. This is not as bad as I feared after such poor past few weeks. The end of the run I was able to speed things up and come up with close to an even split. I'm not upset with the time, which is the fastest I have ever run, 1:41:13. My goal for the race is under 1:40, which I think is doable with some adjustments. I seem to run better in the AM, not after work and fortunately the race is early. Pit stops were a little weird since I had to stop at home, I can mitigate the time loss better with a real race. My stomach did well. I ate two gels, the first right before I started and the second about 35 minutes in. I did drink a tad too much water and had some transient sideaches. It is a trick figuring out how much to hydrate when it's not hot as blazes. During the summer, I drink pretty much as much as I want with no problems. Now to fit in some intervals and easier runs, then race time.

Saturday, December 21, 2013

Still progressing

8 miles today at 7:30 pace, negative splits. Still trudging on toward a sub 1:40 half marathon Feb 1st. Stomach was about 80% with a gel 2 miles in and minimal sips of Gatorade from handheld bottle. Started out a little sluggish and things picked up late, a good sign in my mind. Warm day. Don't know what to expect come race day with bipolar weather all winter.

Monday, December 16, 2013


I stretched out the length of my intervals tonight. Before I'd been doing basically very short sprints down the block. This frightened neighbors to see a ghost-pale walking stick sprinting down the street after dark. Around these parts you either run because you stole something or because you are trying to escape a pack of pitbulls. (I've done one of those on numerous occasions.) So tonight I dropped the pace down to 6 minute/mile pace, albeit not actually running a full mile. I pulled off a whopping two 1/3 mile intervals at this pace before I reached the brink of death. While this was not a particularly fun exercise, I did enjoy exploring a limit. Now I can use this information to hopefully come up with a more manageable interval scheme.

Saturday, November 23, 2013

Speed Kills

The handful of runs I've done since the marathon have been short and fast. I was surprised at how zippy my legs felt. In fact it was hard to hold back the pace. Maybe its knowing that I'm not going to be running for 2-3 hours that provides the incentive to push harder.

I'm also tracking my pace and stats with a GPS watch now, the Garmin Forerunner 10. I had been using my phone, but it was impractical for certain runs. After reading some reviews on what they can do coupled with the unexpected bestowal of a gift card and a 20% off storewide sale at Fleet Feet, I took the plunge. What is normally a $130 watch ended up costing me less than half that. So far I love it. I can tell my pace at any point during the run, total distance run, time each mile, all without a giant smartphone clumsily lashed to my arm. And I can upload all this information and get even more detail, including elevation change and automatic compilation of weekly totals.

After these initial runs, the 1:30 goal for this upcoming half marathon is probably a little too lofty. Realistically, I'm going to shoot for under 1:40, roughly 7:30 miles. This is pushing it, but doable in the limited amount of time I have before the race. Depending on how the intervals and strength training go, I hope to whittle that goal down some.

I did 5.5 miles today at a 7:33 pace. I plan to go up to 6 miles next week, then increase a mile a week until 2 weeks before the race. Weekly intervals, increasing distance, weekly strength work-lunges, squats, using the stairs at work, running the Talmadge Bridge. Also 1-2 maintenance runs during the week, usually 2-4.5 miles.

Sticking with the diet of fat and protein, crack carbs almost exclusively while running. I've bottomed out my weight it seems at 145 lbs. My body fat% is still coming down some, currently 11%. Hopefully this means I am building some muscle mass, because my total weight hasn't changed for well over a month.