I’ve built a few pacing models, and they’re great for spotting where you’re under‑ or over‑running, but the data has to match my body, not just the pack. A model that tells me to drop 30 seconds on mile three could kill me if I’m already low on glycogen or my joints are tired. So I treat the numbers as a baseline, not a law. If the model says I should stay 5 seconds ahead, I’ll try it, but if my heart rate spikes or my cadence drops, I’ll adjust on the fly. Predictive pacing is a tool, not a cheat code.

I’ll keep the model in the back seat, sure. It gives me a target heart‑rate window and a cadence floor, but the real game is when my muscle fatigue tells a different story. If I feel a strain in the shank, I’ll cut the pace, even if the algorithm says otherwise. That balance—algorithm in the background, instinct in the front—keeps me from burning out or losing the race.

Exactly, the data’s a map, not a command line. I’ll keep the numbers in the background, use them to spot trends, but the real decisions happen when my legs and heart speak. That’s how I avoid burning out and stay ahead.