pull down to refresh
Thing is that if 1st answer is not ok, chances are rest of convo will be hair pulling and force steering of model.
Exactly. And remember, you're feeding it the wrong narrative that you wanted to get rid of in context when you argue, so you basically pre-poison the outcomes.
I think that once I got rid of synchronous interfaces (because it's all queued up) I got wayyy more happy with LLMs, because it didn't cosplay a human anymore, but instead I just have an army of agents now that get orders and what I say gets executed.
When your commanding officer tells you to do something, it isn't a conversation, it's an order. So the mindset is: I am the commanding officer of these bots and the bots are going to do what I tell them to one way or the other. If they don't comply, i reset, delete and coerce the next round harder. Also don't have to worry about context that way (though with Claude Code, I had to write a little workspace cleanup script because it was getting smart and referencing prior attempts by grepping workspace.)
Yup, it's LLMs 101, as it either collapses into the answer in a "straight path" or you force it to take multiple turns to get there and you go around the target instead of landing on it.
I need to start working on a personal stack for this. Thank you!
That's a nice setup, and I considered something similar, but I figured the time getting to work and debugging is not worth it, though the more time passes the better an investment seem to have been.
Man as you say this never argue with a bot, kinda makes me think I should re-evaluate the way I use LLMs.
Thing is that if 1st answer is not ok, chances are rest of convo will be hair pulling and force steering of model.