Claude: “lots of people enjoy lemon in their tea, but there’s a subtlety: putting it in coffee is likely to be an unpleasant experience”.
If I asked “should I try lemon in my tea and coffee?” this would be effective communication. But Claude gives answers like this for “should I try lemon in my tea?” which is just annoying.
Captures it perfectly. I notice it more in newer sessions too where it doesn't have a clear understanding yet and is making a lot more assumptions. I wonder if this could be an emergent RLHF strategy - by drawing attention to (seemingly obvious) assumptions or context being made (e.g. I'm only interested in tea not coffee) it increases the chance that a human will correct the rare incorrect assumption sooner. If you are scored on solving problems, with no weight given to human frustration levels, this is probably a good technique.
That hasn't been my experience, but I know what you mean. Claude in particular likes to point out "things you might not have considered" and I sometimes already have. But it tends to vindicates me more than it annoys.
I'm pretty early in my career, so I probably gain more from that sort of stuff than most people. The senior devs on my team tend to get the most frustrated with it and I think this behavior is a big part of why.
Another way to look at it is "it talks to me like I don't know anything"
Which is very annoying when you do know things