Fix: traduction contre la montre
This commit is contained in:
parent
309138f880
commit
04ccd88942
1 changed files with 25 additions and 17 deletions
|
|
@ -4,33 +4,41 @@ draft = false
|
|||
tags = [ "running","watch" ]
|
||||
title = 'Against the clock'
|
||||
+++
|
||||
Tuesday, I was convinced I’d had a good session.
|
||||
I ran very slowly, stayed in the endurance zone, even managed to finish without any pain.
|
||||
In short, I thought it was a success.
|
||||
|
||||
I’m on my fourth run now.
|
||||
And it feels better each time: I’ve found my easy pace, the one that lets me hold the distance without pain. My heart rate doesn’t spike as much, and I don’t have to stop nearly as often to walk.
|
||||
Except… today, after comparing, I realize I was completely wrong.
|
||||
|
||||
**All good, right?**
|
||||
##xTuesday — the misleading session
|
||||
|
||||
Not for everyone.
|
||||
There’s one who doesn’t agree: my Polar Pacer Pro. Run after run, it keeps scoring me lower and lower.
|
||||
At the time, I thought I felt “fine.”
|
||||
But to avoid blowing up my heart rate, I had to slow down drastically — over 10 minutes per kilometer, almost walking.
|
||||
My Polar watch gave me a mediocre score, and I figured it was exaggerating.
|
||||
|
||||
**Why?**
|
||||
In reality, I was just tired. Too tired to run properly.
|
||||
The watch picked up on it before I did.
|
||||
|
||||
I honestly don’t know. Maybe it’s reading between the lines.
|
||||
Today — the difference
|
||||
|
||||
Has nothing to do with running itself, but I haven’t been sleeping well lately. Choppy nights, built-up fatigue… Maybe that’s messing with my heart rate. Maybe that’s enough to throw the numbers off and make me look worse than I feel. Could be.
|
||||
Two days later, I ran under the same conditions.
|
||||
Result: one more kilometer in 30 minutes, a much faster recovery afterward, and a feeling of ease I didn’t have on Tuesday.
|
||||
|
||||
Or maybe it’s just because I’m running shorter distances.
|
||||
Proof that that day, I was pushing too hard without realizing it.
|
||||
|
||||
**So, who should I trust?**
|
||||
## The real lesson
|
||||
|
||||
The watch?
|
||||
Or how I feel?
|
||||
What I’ve learned is that the watch isn’t a judge — it’s a mirror.
|
||||
It doesn’t “criticize” my runs; it shows me when I’m struggling, even if I don’t want to admit it.
|
||||
|
||||
I’ve chosen to trust my body.
|
||||
Because at the end of the day, the watch still does one useful thing: it forces me to slow down. No red-zone cardio, no unconscious sprinting. Just a steady rhythm I can hold without suffering.
|
||||
Fatigue isn’t always visible. You think you’re fine, but the numbers tell another story.
|
||||
And in that case, the smartest thing to do isn’t to push harder — it’s to adjust.
|
||||
|
||||
If fatigue is skewing the numbers, then fine. That’s life. What matters isn’t impressing a watch.
|
||||
|
||||
What matters is not getting injured, building consistency, and keeping the joy alive.
|
||||
## What I take away
|
||||
|
||||
Better a slow jog at 10 minutes per kilometer than no jog at all.
|
||||
And sometimes, accepting to slow down is exactly what keeps you progressing — and injury-free.
|
||||
|
||||
So yes, on Tuesday I thought I felt fine.
|
||||
But today, I realize slowing down was the right call.
|
||||
Not for performance — but for longevity.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue