Understanding of the role of the gut microbiome is continually being expanded. It is resposible for a lot of important hormones, for example. It goes way beyond digestion.

Same. I have most of those listed on my table, and hardly ever use Tabasco. Too much vinegar and very one-note.

I thought Isaacson's biography was good and balanced.

These podcasters (who I quite like but may be an acquired taste) call him out on how little he pushes back or does basic fact checking:

* https://podcasts.apple.com/us/podcast/elon-musk/id1651876897... * https://podcasts.apple.com/nz/podcast/elon-musk-part-2/id165...

Besides lamp shading what are arguably Elon's biggest/most interesting flaws, it contained factual errors that he had to retract later.

Agreed. Also pretty telling that Ashlee Vance refused to collaborate or share his recordings with Gibney.

Yes, comments might be my biggest gripe with CC due to what you said. 9 out of 10 of my revisions to Claude's work is deleting or rewriting comments. Such a silly thing for it to fail on.

(I do have detailed instructions for it on how to comment (or not) but it has not fixed this.)

That's why I prefer the flip format, over fold. Typing this on a Flip 3 I've had since 2021, very happy with it.

> significant lines of code per human-landed diff

Claude would be proud.

That said, code reviews have never worked well, and it's a weird argument for wanting to preserve them.

Pairing is great and under-utilized. On one hand it's a hard sell to managers (let's use two people to do one person's job) and from the developer's point of view, it's intense and exhausting.

What's a weird argument? Did you read this article?

She's arguing that most code reviews aren't necessary. Some can be automated if they are deterministically predictable (eg. formatting, lint, standardization changes). Others should be reviews of design before the coding phase.

She gives a few specific examples of when code reviews should be maintained.