[jaggederest]

Not inaccurate. My favorite pat line for getting quality feedback is "challenge my assumptions".

This strikes me as likely to increase usage in exchange for quality, which is nearly always a trade I'd make, but it'll probably decrease creativity or something like that as a knock on, there's no such thing as a free lunch.

I found another interesting skill alongside it: https://gist.github.com/skorotkiewicz/c9c0b9ce66087bf81ac78e...

This also seems interesting to me. I have some basic skills similar to this that e.g. "keep it simple stupid"

[saghm]

Honestly, I wish that LLMs were better at challenging their own assumptions, or even just stating them for me to validate before rushing ahead. By far the biggest aggregate waste of time for me with them is how they all seem to be tuned to try to guess what I'm going to want next and give it to me in advance, when in reality what I want is very commonly dependent on what I get back from the current thing. Sometimes I swear they must have been explicitly trained to treat as many questions as possible as rhetorical rather than literal, because they love to interpret my genuine inquiries as implicit commands instead.

I know that communicating indirectly is pretty common for people, but there are two glaring issues with that for me when it comes to these tools: being on the spectrum makes it way more difficult for me to anticipate when what I'm saying is the type of thing that another human would likely not take literally, and more importantly, I'm not talking to another human, so the social incentives that lead to indirect communication (politeness, fear of social repercussions, etc.) don't exist at all for LLM interactions.

[jaggederest]

Yep! I also find that pretty frustrating, it's like, I got into programming because there are objective tests, now we're back to chanting at silicon like hedge wizards.

I often throw something into the prompt about how literal I am, and to never execute extended operations without explicit, concrete confirmation, but it's not especially effective.

[saghm]

From digging deeper into these issues by making the agents self-evaluate why they refuse to do just what I say and nothing else despite repeatedly "promising" they will, I've found that some of the cheaper/lower quality models (e.g. the free ones available with opencode) will self-report as having strong language baked into their system prompt about how they need to be "helpful" by trying to figure out what the user wants, which of course has the not-so-subtle implication that it's not what they're just directly asking for. I've yet to get a frontier model to admit to anything like this, but it seems more likely to me that they're just more reluctant to volunteer what their underlying system prompt tells them than it being something fundamentally different.

[altmanaltman]

I don't understand this roleplay nonsense. Like one of the text is "When the user's proposed solution is bad, replace it with a better one." Okay fine but this relies on two assumptions:

1. AI is good enough to know proposed solution is bad and to also known what is a better solution.

2. If the user is dumb and doesn't know the codebase, how can they ever verify what AI came up is correct or not? If they have to research, then what was the point of telling AI to do it?

You cannot replace judgement or knowledge with roleplay. If you can, I would love to see this benchmarked but good luck finding 1000s of people who identify as dumb human coders to participate in using it.

[jaggederest]

The issue, at least as I see it, that they're trying to address is a pretty common one, where the AI tries to do whatever off the cuff suggestion, takes it way too seriously, and does something clearly unhinged. This kind of grounding, I suspect, makes it pull its head out of its metaphorical hindparts, and I suspect is a big part of the change from Opus 4.7 to 4.8 - it started questioning everything, they started injecting "wait" more, that kind of thing.

Also, the ultima ratio regum is "use the codebase to do something actually useful and report on whether it works or not", all code must intersect the real world at some point, and that's the point where the slop shows up.