It's his first marathon ever, but he's a very experienced runner. It would be hard to find a better prospect for a good first marathon. He's a multiple (former) world record holder and medalist at shorter distances from the mile up to half marathon. His half marathon is still 2nd all time.
I wouldn't have predicted this out of nowhere, but if you told me a marathon debut went this well and asked me to guess whose it was, I like to think I'd have come up with Kejelcha in my top few picks.
That said, great 5000/10000 athletes don't always have great marathon careers. An example from this race is the world record holder at both those distances, Joshua Cheptegei. He's run several marathons but none spectacular by his standards. He was in this race too but 7 minutes back.
I've read that even if you absorb it all, there's some question about whether it's useful. This Alex Hutchinson article suggests, among other things, that it may spare your fat stores rather than your muscle glycogen:
> Even if you can absorb 120 grams per hour, it might not make you faster. In Podlogar’s study, cyclists burned more exogenous carbs when they consumed 120 rather than 90 grams per hour, but that didn’t reduce their rate of endogenous carb-burning—that is, they were still depleting the glycogen stores in their muscles just as quickly.
It doesn't take much. If an elite burns 1500-2000 kcal running a marathon, even ignoring glycogen and exogenous carb, that's only ~195-260g of body fat (~7.7 kcal/g). Even at an extremely lean 4% body fat, Kejelcha would have 2360g of body fat available. (He's probably in the slightly higher 5-10% range.)
(And obviously, the majority of those 1500-2000 kcal are coming from stored glycogen rather than fat.)
If we're only talking about the marginal difference between 90 and 120 g/hr of exogenous carb, then that's 60g over two hours or 240 kcal -- equating to 31g of stored body fat. That's nothing.
What is wrong in that quoted sentence? Do you mean "articulacy" should instead be "articulateness"? "Articulacy" is also a word, and correct in this context.
I have terrible news for you. Linguistics is descriptive, not prescriptive. We will torment you with word game playing until such time as you loosen up.
Yes, thankfully! It's amusing to read what they say about fetch on nodejs.org [1]:
> Undici is an HTTP client library that powers the fetch API in Node.js. It was written from scratch and does not rely on the built-in HTTP client in Node.js. It includes a number of features that make it a good choice for high-performance applications.
Note that node-fetch will silently ignore any overrides to "forbidden" request headers like Host, since it's designed for parity with fetch behavior in the browser. This caused a minor debugging headache for me once.
Regarding the noise you mention, I wonder if memento's use of the git 'notes' feature is an acceptable way to contain or quarantine that noise. It might still not add much value, but at least it would live in a separate place that is easily filtered out when the user judges it irrelevant. Per the README of the linked repo,
> It runs a commit and then stores a cleaned markdown conversation as a git note on the new commit.
So it doesn't seem that normal commit history is affected - git stores notes specially, outside of the commit (https://git-scm.com/docs/git-notes).
In fact github doesn't even display them, according to some (two-year-old) blog posts I'm seeing. Not sure about other interfaces to git (magit, other forges), but git log is definitely able to ignore them (https://git-scm.com/docs/git-log#Documentation/git-log.txt--...).
This doesn't mean the saved artifacts would necessarily be valuable - just that, unlike a more naive solution (saving in commit messages or in some directory of tracked files) they may not get in the way of ordinary workflows aside from maybe bloating the repo to some degree.
(Yes, this article is about an extension of the deadline. I don't remember what happened after that.)
reply