Code's easy to evaluate because there's finite number of things it needs to do and its end goal isn't to be perceived by a person. An image can always be wrong.
> "Forty percent chance of precipitation." I never understood what forty percent of rain meant.
You don't understand the world's most understandable statement?
> On Monday my manager wrote in the team chat: "On Friday we'll discuss roles." No emoji. For three days I wondered what my role was.
Three whole days with no contact with your manager at all? Zero opportunity to ask anything amongst all the other activities and communication?
> And now I remember the whole morning minute by minute
You have a perfect-as-if-traumatic memory of specifically the day that your manager sent a cryptic message in chat that you didn't follow up on for three days?
> With a shirt, at least, everything is defined: here's the collar, here are the sleeves, here's the crease that shouldn't be there.
Oh, you're going to love when you discover other objects. Just you wait.
I often wonder about the chance of precipitation, what exactly does it mean? Not looking for an explanation here, I'm just saying I found this bit very relatable.
Three whole days with no contact with your manager, while not a good sign, is not that unlikely. I've gone with weeks. Again, not usually a good sign, but this person is describing a bad time, with a hint of "AI made us redundant".
As for why this person is remembering their morning minute-by-minute, did you get they are dying? It's a final minute kind of thing, an Owl Creek moment. I wonder if you undertood the whole story happens within this minute, the main character telling us how it all came to this.
I don't know that that analogy fits for this comment. The argument is that the old skill is genuinely no longer needed in favour of the new skill, but the new skill requires experience from the old skill. I don't think being a good driver needs you to have already been a good cyclist.
If the second LLM is just describing the content of the commit doesn't that defeat the purpose of the description, to capture the context that doesn't make it to the code?
The second LLM is prompted to actually research the code, not just the diff, with fresh eyes to figure out what it does and why, before writing the commit message.
> It’s one of the really famous cartoons. If you’re reading this newsletter, you’ve probably watched it yourself.
I've never heard of it and would have appreciated at least a cursory definition. I thought I was going to see an article about an ad for Opera the browser.
They're writing for a newsletter called "Animation Obsessive" - given that, I think they're 100% correct, you're a random driveby :-) That said, https://www.youtube.com/watch?v=TJI_gygXsfs has the first three minutes if you want to get the gist (I don't know where to find a full version, but that's an official-looking Warner Bros. channel, not a bootleg.)
reply