> Can you give an example of what you wanted explained
Something I do dozens of times a day:
"Please explain what this PR does, I haven't read it"
it will make me 20 pages of gibberish about caches, correctness checking, race conditions, github action runners, tradeoffs between a bunch of invented terminology internal to the PR without defining the terms- you'd have to have already read the code to know what it was referring to
without ya know, explaining it. I ask my colleague and he says something like "oh it deletes records from such-and-such a system when they aren't needed anymore after a merge" and I know exactly what he means. A single well composed sentence was all that was needed.
You can ask the agent for a single sentence explanation and it will write something like "linked candidate records are trimmed when canonical record determination window is passed", none of which is terminology any of us use, some of which is defined in the new PR and some of which is made up. I can't emphasise enough, I use these things EVERY DAY. it knows what I work on, it knows how I talk. There is no earthly reason it should be this bad given all the skills and advance and context it has. As mentioned, I constantly work to correct its shortcomings in this area but its like trying to hold water in a sieve, it just cannot do it.
"What does this PR do?"
LLM: "Oh, it specifies the kernel window over the cache candidate list to classify possible invalidated swap identifiers"
Colleague: "It removes duplicates in the target_uuid_cache table in the db"
The agent has full context of what systems the code talks to, our terminology sheet etc. It just pathologically cannot simplify things down. If you work with them enough you learn that there are some words it reaches for a lot in certain circumstances, like it loves "canonical" in relation to merging things. But this is more like learning to communicate with a deeply autistic person who struggles to adjust their speaking to be relevant to their audience rather than talking with a "good communicator"