Since spring I’ve been using some workout plans put together by Anthony Arvanitakis. For eight weeks from late May to early July I did his Superhero Bodyweight Workout, and since then I’ve been following along with bodyweight workouts he’s been sharing for the summer.

One limitation that I’ve had all this time is that I haven’t been able to do the hill or stair sprint workouts that he suggests, due to a lingering foot injury. After repeatedly resting my sore foot until it was nearly all better, and then trying to get back into running, only to have my foot start hurting again, I finally took a full month off. That was enough for my foot to finally feel entirely better, so last week I went for a 3-mile run as a test. My foot didn’t hurt during the run, but was sore again that evening and the next day.

I took another week off from running, and then today decided to try a different tack: Those hill-sprint workouts.

Three things about this make it make sense to me:

  1. Hill sprints are lower impact than running on flat ground (because the ground is higher for each next step, so your foot doesn’t fall as far).
  2. The total mileage is much less (today’s workout was just 0.5 miles).
  3. My running gait is better when I’m sprinting.

Putting those things together makes me think that maybe hill sprints will let me run at least a little without aggravating my foot injury.

Another thing I’m doing is extending my warmup quite a bit. I did my full dynamic stretching routine before heading to the workout location. Once I got there I scrupulously followed the prescribed warmup routine, jogging up the hill at 50%, 60%, 70% and 80% intensity (I actually did 5 preliminary jogs up the hill, at gradually increasing intensity). After each of the last two warmup jogs I did a set of 12 straight-elbow push ups (what I call rhomboid pushups) as preparation for the pushup part of the workout.

The main workout then was 4 sets of sprinting up the hill at 90% intensity, walking down, and then doing as many pushups as I could do with perfect form (I did 10, 10, 8 and 8 pushups).

I also did something I’ve always resisted in the past: I drove to my hill. (This being central Illinois, hills are few and far between. My hill is at Colbert Park.) Usually I don’t like to drive somewhere to get exercise—why not walk or run and thereby get more exercise? But with my sore foot, that much extra running would definitely aggravate the injury. Even walking that far might be an issue.

One thing I need to be careful of is to be sure to get in my full wrist warmup. I’m pretty good about that ahead of a rings workout, but perhaps wasn’t as scrupulous as I should have been this time. But the pushups put enough stress on the wrists that it’s good to get them fully warmed up even before the rhomboid pushups.

I’m pretty pleased with my workout. My foot (really my ankle) is a bit tender this evening. We’ll see how it feels tomorrow. On the schedule I’m (tentatively) following, I’ll be doing hill sprints again Monday. If my foot is completely pain-free at least several days ahead of that, I’ll proceed with that plan.

Jackie was fixing blue-corn pancakes with maple syrup for breakfast, and eating that many carbs first thing in the morning can be a problem for me. However, I have come up with a strategy for dealing with it: Getting in a pre-breakfast fasted workout. My theory is that by doing this I deplete my muscle glycogen, so that my muscles are primed to soak up all the carbs I eat, minimizing the degree to which the glucose spikes my blood sugar.

I have no data to show that this works, but anecdotally I can report that it seems to help.

I’ve been wanting to go for a run. I had planned to go for a run yesterday, but it ended up being rainy enough that I decided to postpone the run for a day. So I might have gone for a run for my pre-breakfast workout, but Jackie was hungry early, and I didn’t want to delay breakfast by an extra hour.

So, I did what’s becoming my standard HIIT workout: I warm up with 3×25 Hindu squats, and then I do 3×25 kettlebell swings with my 53 lb kettlebell. It’s a quick workout—it’s all done in 20 minutes, including some amount of pre-warmup warmup—and it’s of high enough intensity to burn off plenty of glucose.

After breakfast (and a bit of digesting) I went ahead and got out for my planned run. After the persistently sore foot I’ve been dealing with for months now simply refused to get better, I had taken a full month off from running to see if all I needed was plenty of rest to fully recover, and that may have done the trick—I went out for a 3.33-mile run, and I had no foot pain whatsoever.

I don’t wear my Oura ring for the kettlebell workouts (or other workouts where I have to grip something, because handles, bars, and (gymnastic) rings don’t play well with the Oura ring). However, my Polar heart rate monitor will tell Google Fit about my workout, and the phone app for the Oura ring will read that data and give me credit for what I did while the ring was off:

My peak heart rate during the kettlebell swings would have seen me to much higher activity levels than the just-barely “High” levels shown, but that’s because it’s an interval workout. A set of 25 swings takes me just about 50 seconds, and then it takes about 3 minutes for my HR to drop low enough that I can do another set. The software is averaging those periods together. Unless I’m doing sprints (which I didn’t today) a run is just a steady-state effort. I try to keep my HR down in the MAF range, but didn’t manage it today (because of the prior HIIT workout).

Looking at my “readiness” score for today I’m perhaps slightly less ready than I was five days ago, when I let my Oura ring mislead me into postponing a rest day in favor of some hill sprints.

In fact, I felt enormously better today, and my performance shows that. Today’s run was a bare one minute longer than my run at the beginning of the week, but I ran a full mile further:

I’m not sure there’s anything to learn from this. Maybe “don’t skip rest days” would be a good start. I’m sure “listen to your body” is always good advice. Whatever lame platitude you want to go with is fine with me. As for me, I’m just glad I got in a good run.

In other news, the replacement kettlebell for the one I ordered on July 1st, but which vanished into some black hole at FedEx’s Ellenwood, GA location, only to vanish itself in exactly the same way, seems to have been discovered, and is now supposed to be delivered next week! We shall see.

View from a run

My Oura ring produces a “readiness” score each day, and I’ve found it to be a pretty good indication as to whether or not I’m up for a long run or a hard workout. The times I’ve ignored it when it said I needed to take it easy, I’ve often found it was right and I was wrong. Today was a rare instance of the reverse.

According to my plan, today should have been a rest day. But I wanted to go for a run.

The ring gave me a readiness score of 88 (out of a possible 100), which is rather above my average (my average this month has been 80), and I took that as a license to go for the run I wanted, instead of taking the rest day my plan suggested.

Turns out—this time—my plan was right and my ring was wrong. I went for my run, but I felt tired and sluggish throughout.

It wasn’t a catastrophe. I didn’t hurt myself. I just don’t think I did myself much good. I ran to Colbert Park, did three hill sprints (in actuality, feeble jogs), and then ran home again. But I didn’t have any oomph behind the sprints, so I don’t expect they’ll have done their job in terms of boosting leg strength or aerobic capacity.

The Oura ring’s readiness score has been a very reliable indicator for me—which is why it helped me fool myself this time. So this is a good reminder to me to interrogate all of the factors that go into making a workout decision—my plan, my intuition, my ring, etc.

So one thing I’m doing is looking back at the factors that feed into the score, looking to see if there’s one that looked better than it really was.

Nothing really jumps out at me. Given the same information, I’d also figure that I was ready for a hard workout. (In fact, I had that information, plus my own sense that I felt ready for a hard workout. That’s exactly how I overrode my plan and went out for a tired, tiresome run.)

Oh, well. Insert your own pithy “live and learn” aphorism here.

I’d heard this, but I’m not sure I really believed it.

I’ve been running in “barefoot” shoes for a good 5 years now. The improvement in my gait was dramatic and immediate. But serious barefoot advocates are very firm about the point that it’s only when you run with actual bare feet that you acquire the huge upside that comes with barefoot running.

Reduced injury rates (due to the improved gait) are one of those upsides. Increased running efficiency (due to the improved gait, but also due to not having to carry the weight of a shoe on each foot) is another upside.

But there are alleged to be further sources of improved efficiency that come from barefoot running. When you’re actually barefoot, you’re going to hit the ground much more gently (because without cushioning it would hurt to hit the ground hard). Your foot is going to hit the ground with zero forward velocity (because if your bare foot slides along the concrete, the friction will cause blisters almost immediately).

In both cases—not slamming your foot into the ground, and not grinding your foot into the ground—the upshot is improved efficiency.

But it’s one thing to hear that “improved efficiency” is a thing, and another to actually see it. Check out this comparison of a run from one month ago, versus a run today.

Here’s the first three-quarters of mile of a run from one month ago, wearing minimalist shoes:

I left off the first few tens of seconds because it took until then for my heart rate monitor to stabilize on my actual heart rate. Then I went on for about three-quarters of a mile (out of a longer run) to match the distance that I ran today.

The things to note are that I ran at a 14:20 min/mil pace (very slow), that my heart rate averaged 117 bpm, and that the majority of my run was spent in zone 3.

Now check out my graph from today’s run, run with actual bare feet:

I’ve matched the distances (the former is the first part of a much longer run, the latter my entire barefoot run today). Today’s run was at a considerably faster pace (37 seconds per mile faster), while at the same time keeping my heart rate considerably lower (averaging 109 bpm, entirely in zone 2).

I have to say, this is very promising for future endeavors. I need to boost my confidence a bit, so I feel comfortable going for longer runs barefoot. I also need to get a bit more familiar with pacing—my MAF heart rate is probably more like 124. I need to figure out what it feels like when I run that pace barefoot. Because: who knows how fast I can run at that heart rate barefoot?

(The shortcode below won’t work until I get an updated version of the plugin for displaying GPX maps.)