Earlier quoted context omitted.
>I've resorted to append things like "THIS IS JUST A QUESTION. DO NOT EDIT CODE. DO NOT RUN COMMANDS". Which is ridiculous. Funny to read that, because for me it's not even new behavior. I have developed a tendency to add something like "(genuinely asking, do not take as a criticism)". I'm from a more confrontational culture, so I just assumed this was just corporate American tone framing criticism softly, and me com…
I've been using chat and copilot for many months but finally gave claude code a go, and I've been interested how it does seem to have a bit more of an attitude to it. Like copilot is just endlessly patient for every little nitpick and whim you have, but I feel like Claude is constantly like "okay I'm committing and pushing now.... oh, oh wait, you're blocking me. What is it you want this time bro?"
Shall I implement it? No
201–210 of 603 posts
Re: Shall I implement it? No
#202The "Shall I implement it" behavior can go really really wrong with agent teams. If you forget to tell a team who the builder is going to be and forget to give them a workflow on how they should proceed, what can often happen is the team members will ask if they can implement it, they will give each other confirmations, and they start editing code over each other. Hilarious to watch, but also so frustrating. aside: I…
Re: Shall I implement it? No
#203Earlier quoted context omitted.
Asking a yes/no question implies the ability to handle either choice.
To an LLM, answering “no” and changing the mode of the chat window are discrete events that are not necessarily related. Many coding agents interpret mode changes as expressions of intent; Cline, for example, does not even ask, the only approval workflow is changing from plan mode to execute mode. So while this is definitely both humorous and annoying, and potentially hazardous based on your workflow, I don’t complet…
Re: Shall I implement it? No
#204Codex has always been better at following agents.md and prompts more, but I would say in the last 3 months both Claude Code got worse (freestyling like we see here) and Codex got EVEN more strict. 80% of the time I ask Claude Code a question, it kinda assumes I am asking because I disagree with something it said, then acts on a supposition. I've resorted to append things like "THIS IS JUST A QUESTION. DO NOT EDIT COD…
Re: Shall I implement it? No
#205Re: Shall I implement it? No
#206Often times I'll say something like: "Can we make the change to change the button color from red to blue?" Literally, this is a yes or no question. But the AI will interpret this as me _wanting_ to complete that task and will go ahead and do it for me. And they'll be correct--I _do_ want the task completed! But that's not what I communicated when I literally wrote down my thoughts into a written sentence. I wonder wh…
Re: Shall I implement it? No
#207Earlier quoted context omitted.
I've been using chat and copilot for many months but finally gave claude code a go, and I've been interested how it does seem to have a bit more of an attitude to it. Like copilot is just endlessly patient for every little nitpick and whim you have, but I feel like Claude is constantly like "okay I'm committing and pushing now.... oh, oh wait, you're blocking me. What is it you want this time bro?"
"Don't act, just a question" works for me.
Re: Shall I implement it? No
#208Earlier quoted context omitted.
I feel like people are sleeping on Cursor, no idea why more devs don't talk about it. It has a great "Ask" mode, the debugging mode has recently gotten more powerful, and it's plan mode has started to look more like Claude Code's plans, when I test them head to head.
Cursor implemented something a while back where it started acting like how ChatGPT does when it's in its auto mode. Essentially, choosing when it was going to use what model/reasoning effort on its own regardless of my preferences. Basically moved to dumber models while writing code in between things, producing some really bad results for me. Anecdotal, but the reason I will never talk about Cursor is because I will…
You just described their “auto” behavior, which I’m guessing uses grok.
Using it with specific models is great, though you can tell that Anthropic is subsidizing Claude Code as you watch your API costs more directly. Some day the subsidy will end. Enjoy it now!
And cursor debugging is 10x better, oh my god.
I have switched to 70% Claude Code, 10% Copilot code reviews (non anthropic model), and 20% Cursor and switch the models a bit (sometimes have them compete — get four to implement the same thing at the same time, then review their choices, maybe choose one, or just get a better idea of what to ask for and try again).
Re: Shall I implement it? No
#209[flagged]
Honestly I don't think it's optimized for that (yet), though it's tempting to keep on churning out lots and lots of new features. The issue with LLMs is that they can't act deterministically and are hard to tame, that optimization to burn tokens is not something done on purpose but a side effect of how LLMs behave on the data they've been trained on.
But I assume you mean predictable in the sense of reacting simiarly to similar inputs.
Re: Shall I implement it? No
#210[flagged]
[flagged]
Pure ideology, as a certain sniffing slav would say