lance said:what I'm amidst of - running very high weekly mileage
If you're running a hundred a week, you're running "solid" or
"moderately high" mileage by competitive male marathon standards.
"*Very* high" would be more like 140+. And surely you'd prefer to be
measured by competitive male marathon standards, not against the TNT
types, right?
Of course you're spending more time running than the 2:22 guys, and
that's what's most important; but it'd be misleading to call time
"mileage". Time is *money*, after all, not distance.
Quoted message said:In the article according to David Costill, Ph.D.
Yawn. Best I can tell Costill contributed big-time to scientific
understanding of aerobic exercise; but he's worthless or worse when it
comes to prescriptions for training to run competitively. Which is no
big surprise - the best coaches like Lydiard who know about the best
training often stumble badly when they try to talk about the science,
while the labcoats tend to pooh-pooh anything which doesn't show up on
one of their blood or breath meters despite its perfect correlation
with actual success in actual racing.
Quoted message said:"I really have no idea," says Costill.
At least he's being honest.
Quoted message said:Because it is hard to prove cause and effect, it is not clear
whether high mileage runners become more economical by running
more miles or are innately more economical and can therefore
handle higher mileage without getting injured.
What we do know:
- Zillions of highly driven marathoners continue to improve, year
after year for quite some time, on diets of relatively high mileage.
I bet most of 'em don't obsess too much whether it's that they're
getting "more economical", "stronger", "more experienced", or just
better.
- This constant perpetuation over the years and decades of the
unquestioned assumption that most injuries are generally caused by
exceeding one's mileage limit is awfully wrong-headed. Sure, no doubt
certain varieties of injury are linked to mileage. But so so so many
injuries are also linked to speedwork (broad, common definition which
includes things like VO2 intervals).
Mileage gets disproportional blame, IMO, because [a] it's the ultimate
quantifiable variable, expressed as a nice easy to deal with weekly
number, and so amenable to the simplistic rules we crave: just keep it
under 40 (,70, 100) miles and you'll be fine; [b] we'd like to believe
you can always get more returns on less work, hey let's work smarter
not harder, so let's demonize high mileage and pretend a few compact
sessions of intervals can make up for slashing forty-five minutes of
running each day from serious marathon training. (And then when all
those intervals injure us, proclaim: "see, even sixty miles a week is
dangerous to us non-elites. Ninety or a hundred is outright lunacy!"😉
When mileage injures, N-1 times out of N it's because of, yeah, too
much too soon, not just plain ol' too much. If you're ready for the
mileage, you'll probably get exhausted from the nonstop slogging long
before you get injured.
And of course lance's typical fall style seems to be "too much too
soon", plunging headlong into hundred mile weeks rather than ramping
up smoothly, best I recall; but I'm hoping that's worked out OK for
him this time. lance, if you're still healthy at this point, don't do
anything stoopid between now and the race! No last-minute extra hard
workouts to try and squeeze out that last second per mile. The hay,
as they say, is pretty much already in the barn. And no listening to
exercise physiologists. If they say you've got to do such-and-such to
optimize your VZmax3 Threshold or whatever the hell, pause to ask
yourself why they're writing for active.com and not coaching our best
to Olympic glory.