The author describes a sensation of legs “fighting it out” from the days after a first half marathon, without any injury. Three days after the race, he describes stairs feeling like a punishment, with quads damaged, tight calves, stiff hips and the need to cling to the handrail. The main idea is that the half marathon can leave deep fatigue and a slower recovery than you might imagine.
The article then goes on to detail what happens “under the surface” after 13.1 miles, starting with micro-muscle damage. With each step, the muscles are worked and, over the distance, this builds up: the author talks about thousands of tiny micro-tears in the muscle fibres. He also links the pain to the peak in biomarkers, with creatine kinase levels rising after the race and peaking about 24 to 48 hours later.
Recovery also depends on energy, and the article links fatigue after the race to a drop in glycogen. It explains that the body stores fuel in the form of glycogen, which is “burn[ed] through” during a tough half marathon. After the event, it needs to be replenished; with adequate intake, especially carbs, rebuilding can happen in one or two days, while insufficient eating prolongs the feeling of heaviness.
The article then offers “day-by-day” recovery benchmarks after a “hard” half marathon, distinguishing day 0 from the following days. On race day, it recommends not stopping abruptly: walk for 10 to 20 minutes, hydrate and eat with carbs and protein. Day 1 is presented as often the worst: no running, but moving lightly, walking and doing gentle stretching.
Lastly, the author makes a practical point: don’t confuse “feeling better” with “being fully recovered”. He explains that you might stop feeling sore without the body being ready, and shares his own example: feeling good three days after a race, then starting a tempo session, with a “disaster” (no rhythm, no energy). His rule is to avoid proper training for at least a week after a difficult half marathon.
