FootWorks started at 5:15 Saturday morning, and the group was doing 13 miles. I finished with 13.30 miles in 2:53:34, averaging 13:03 per mile with an average heart rate of 136. It was cooler than it has been, I felt okay, and I really did not have much trouble. Given some of my recent long-run adventures, I was perfectly happy with that and figured the work for the day was done.
Then I got home, started downloading the watch and finally opened TrainingPeaks. Seventeen miles. Sigh. Technically, the 17-miler was scheduled for Sunday, but I had to work Sunday, so if I was going to get it done at all, it had to happen Saturday. I had also just gotten back from Louisiana and had not unpacked, so before I could contemplate another four miles, I needed to get my life into something resembling working order.
That was more or less the theme of the previous couple of weeks anyway. A minor surgical procedure two Fridays earlier required two days of rest, and the trip to Louisiana disrupted the normal training structure after that. I still ran a few miles at a time while I was away, but I did not have my Garmin, so none of those runs exist in the sacred record. Apparently miles only count if Garmin witnesses them.
The interruption, then, was more about structure and telemetry than a complete break from running. The first 13.3 miles made me feel pretty good about that. I could still get up before sunrise, fall in with FootWorks and cover a substantial distance without turning the morning into an ordeal. Training continuity seemed to have survived even if the calendar had gotten knocked sideways.
About six hours later, after unpacking and generally trying to make the house look like somebody who intended to function on Sunday lived there, I went back out.
The Afternoon Was Where the Bill Came Due
I usually start slowly on purpose. I know by now that my first mile often has very little to do with the rest of the run, so I give the machinery time to wake up and trust that I will gradually pick up speed. Usually the legs loosen, the stride gets easier and somewhere down the road the whole operation begins to feel like running.
That did not happen this time. After the first mile I was still putting one foot in front of the other, almost shuffling, and I kept waiting for it to get easier. It never really did. The sun was intense by then, and the 13 miles from that morning were quite clearly still in my legs despite the six-hour break.
The second run was only 4.48 miles, but it took 1:02:45, an average pace of 14:01 with an average heart rate of 129. That heart rate is interesting because cardiovascularly nothing particularly dramatic was happening. I was not blowing up. My legs were just tired, and there is apparently no Garmin metric labeled YOU ALREADY RAN THIRTEEN MILES THIS MORNING, DUMMY.
Toward the end I had to walk a couple of stretches. Eventually I found a rhythm that was less “running” than a workable negotiated settlement: jog for about a minute, walk a few steps, then start again. It was not pretty, but it moved me in the right direction, and by then the right direction had become very specific.
There Was a Cheeseburger at the End of This
At some point during those last miles I promised myself that if I finished this thing I could have a cheeseburger kids meal. I am aware that this probably does not appear in the TrainingPeaks literature, but the universe provides many forms of motivation and I saw no reason to become doctrinaire about it. Run another minute, walk a few steps, start again, get closer to cheeseburger.
The plan worked, and then Burger King improved on it. They had brought back the Mandalorian toys, and the first time those were out I had never managed to get Mando’s Razor Crest. This time I did. So by then the whole ridiculous sequence of events had clearly been meant to happen exactly as it did.
Almost 18 Miles Is Not an 18-Mile Run
The day added up to 17.78 miles and 3:56:19 of moving time, about 13:17 per mile overall, with an average heart rate around 134. That is a meaningful amount of work, but it did not feel like an 18-mile run because it wasn’t one. Six hours is a substantial break, and I had time to eat, cool down, unpack, move around and partially reset before heading back out.
I do not want to turn the total into something it was not and congratulate myself for having run a continuous 18 miles. On the other hand, pretending the total means nothing would be just as silly. I still put almost 18 miles into my legs in one day after a couple of disrupted weeks, and the second run demonstrated pretty convincingly that my body remembered every mile from the first one.
The part I keep coming back to is what happened afterward. I had some ache later that day, which did not surprise me much, but the next morning I felt fine. Nearly 18 accumulated miles, an average heart rate around 134, and the body was basically okay the following day. I am not going to turn one split long-run day into a physiological manifesto, but that seems like useful durability evidence.
Keeping the Thread
TrainingPeaks calls the coming week Peak Vol Week, which sounds appropriately ominous, and there is a 20-mile long run sitting there waiting for me. That does not mean I am about to taper; Philadelphia is Nov. 22, and there is still a good bit of building left between here and there. I would also very much prefer to do the 20-miler as one actual run rather than discovering some creative new way to assemble it from spare parts.
What this weekend leaves me wondering about is what continuity really means in marathon training. There is the clean version where you follow the calendar, hit the prescribed mileage and let adaptation accumulate in neat little boxes. Then there is the version where you have a procedure, travel to Louisiana, run several unrecorded miles, come home, discover the actual assignment after you have already run 13.3, unpack your suitcase and head back outside because Sunday is unavailable.
I am learning that adaptation is not the same thing as improvisation, but sometimes improvisation may be what keeps the adaptation going. This was not perfect execution, and I do not want to pretend it was. But training continuity survived even when the calendar didn’t, and the body absorbed more of the day than I expected it to.
That is enough for now. The next test is simpler and harder: 20 miles, preferably all at once.
I still do not know whether marathon readiness is measured more by executing the plan correctly or by being able to adapt without losing the thread. Presumably the answer is some aggravating combination of both. Philadelphia is close enough now that I will get a chance to find out.
For this weekend, though, I got the miles in, felt fine the next day, and finally got Mando’s ship. I’m calling that a decent return on the effort.
RUNNING FOR PARKINSON’S
I’m training for the Philadelphia Marathon as a Parkinson’s Foundation Champion. If you’d like to support the Parkinson’s Foundation while I work toward Philadelphia, you can donate through my fundraising page.

Leave a Reply