"excursion" (means: a spike/jump — a value that rises or deviates from baseline, just say spike or outlier)

"legitimate majority-normal baseline" (means: a real majority of normal pixels)

"matched pool of pure-noise ('normal') pixels" (means: the same number of normal pixels, don't bring pools into this)

"ablation" (means: comparing before vs. after — turning a thing on/off to see what changes)

I actually used Claude Code to try and find examples like these but not entirely unexpectedly it had a very hard time detecting these, even though I encounter them like every other sentence. I can imagine this style is great when writing prose, not so much when writing documentation.

Similarly, I tried using Claude Design to make some slides, and the individual slides were fine, but just about every other slide it used different words to denote the same concept, which I would say is the fastest way to lose your audience.

Don't be naive or I might even think you're working for the Chinese :-)

Why not? It's about 60 000 London - New York City flights by the way (https://www.theguardian.com/environment/ng-interactive/2019/...). And what's the benefit again?

I am sorry for being direct but you could have just kept it to the first part of that sentence. Everything after that just sounds like pretentious name dropping and adds nothing to your point.

But I fully agree, for complex problems that require insight, LLMs can waste your time with their sycophancy.

Doesn't that come down to allowing it to directly regurgitate training data? Surely it's seen dozens of such solutions.