4 ms·
Have you tried asking it for a lay explanation of what it did? That’s usually all it takes for me. Sends garbage -> request -> sends something readable
by conception 2mo ago
Have you tried asking it for a lay explanation of what it did? That’s usually all it takes for me. Sends garbage -> request -> sends something readable
- basch 2mo agoBrilliant way to get people to waste tokens. Maybe just don’t generate garbage in the first place?
- D13Fd 2mo agoYeah but Sol shows it is possible to just send the readable explanation in the first instance. And I don't want to spend tokens and time on asking for a better version of each response.
- StilesCrisis 2mo agoWhen I ask it to make a CL description, it's worthless unless I tell it to dumb it down as much as possible, assume the reader has zero knowledge of the codebase. And then it makes a perfectly cromulent description that just needs a touch of trimming-down. If I don't do this, the description is just a wall of gibberish and paraphrasing of every little thing it encountered.
- anon7000 2mo agoNo, I’m not interested in fighting my model all day long. Plus is fucking annoying to talk to and collaborate with, so I’m not using it when Sol 5.6 is about 1000 times better in that regard. I have colleagues who spent a lot of time trying to improve their harness with user rules and whatnot and Opus really does not want to follow them.
- hughw 2mo agoYeah my trick is "Restate concisely" Just those two words. I use it A LOT recently.