This tracks with my experience as well, but as an interesting counterpoint, creating “investment” in the outcome seems to boost utility considerably. Perhaps being right in an adversarial interaction is a type of investment?
To add on to this, and I am not sure if it's just confirmation bias, but I've had consistently decent results when I play along as the hard working collaborator with a goal orientated mindset.
"Hey, I've [done small task / fix / tweak]. Now, let's [describe the next task at hand]" - it's a different axis than kind vs. rude, but using the framing of "Us" and "We're a team working together" feels like the code produced is less hogwash than it is with more direct commands: "Add feature XYZ"
My thinking is that it borrows from the archetype of the "good guys working together to overcome adversity" which is pretty universally common in most fiction.
I’m totally onboard with this. I’ve had really good results through framing the interaction as collaborative, and although the framing is “load bearing (lol)” I think it also becomes accurate as the model becomes much more proactive and useful. Need to temper it a bit so it doesn’t get ahead of the supervisory ooda loop, but I’ve also noticed a great deal of improvement in “judgement“ and “creativity”.
"Hey, I've [done small task / fix / tweak]. Now, let's [describe the next task at hand]" - it's a different axis than kind vs. rude, but using the framing of "Us" and "We're a team working together" feels like the code produced is less hogwash than it is with more direct commands: "Add feature XYZ"
My thinking is that it borrows from the archetype of the "good guys working together to overcome adversity" which is pretty universally common in most fiction.