Feels like a training-data artifact. SFT and preference data are full of "here's a cleaner version of your file", not "here's the minimum 3-line diff". The model learned bigger, more polished outputs win. Prompting around it helps a bit but you're fighting the prior.
Over-editing refers to a model modifying code beyond what is necessary
191–200 of 267 posts
Re: Over-editing refers to a model modifying code beyond what is necessary
#192I'm either in a minority or a silent majority. Claude Code surpasses all my expectations. When it makes a mistake like over-editing, I explain the mistake, it fixes it, and I ask it to record what it learned in the relevant project-specific skills. It rarely makes that mistake again. When the skill file gets big, I ask Claude to clean and compact it. It does a great job. It doesn't really make sense economically for…
When I see people talking about Claude Code becoming "unusable" for them recently, I believe them, but I don't understand. It's a deeply flawed and buggy piece of software but it's very effective. One of the strangest things about AI to me is that everyone seems to have a radically different experience.
[deleted]
Re: Over-editing refers to a model modifying code beyond what is necessary
#193[flagged]
Re: Over-editing refers to a model modifying code beyond what is necessary
#194I call this overcooking. Adding unnecesary features.
Re: Over-editing refers to a model modifying code beyond what is necessary
#195Earlier quoted context omitted.
> I'm either in a minority or a silent majority. Claude Code surpasses all my expectations. I looked at some stats yesterday and was surprised to learn Cursor AI now writes 97% of my code at work. Mostly through cloud agents (watching it work is too distracting for me) My approach is very simple: Just Talk To It People way overthink this stuff. It works pretty good. Sharing .md files and hyperfocusing on various orch…
How do you collect these stats? Is it by characters human typed vs AI generated, or by commit or something?
> How do you collect these stats?
Cursor dashboard. I know they're incentivized to over-estimate but feels directionally accurate when I look at recent PRs.
Re: Over-editing refers to a model modifying code beyond what is necessary
#196I'm either in a minority or a silent majority. Claude Code surpasses all my expectations. When it makes a mistake like over-editing, I explain the mistake, it fixes it, and I ask it to record what it learned in the relevant project-specific skills. It rarely makes that mistake again. When the skill file gets big, I ask Claude to clean and compact it. It does a great job. It doesn't really make sense economically for…
The article has a benchmark and Opus has best score in two categories and the second-best in another (there are only three categories). Opus is probably the best choice when it comes to producing readable code right now. GPT (for example) lags way behind.
Re: Over-editing refers to a model modifying code beyond what is necessary
#197[dead]
Re: Over-editing refers to a model modifying code beyond what is necessary
#198I'm either in a minority or a silent majority. Claude Code surpasses all my expectations. When it makes a mistake like over-editing, I explain the mistake, it fixes it, and I ask it to record what it learned in the relevant project-specific skills. It rarely makes that mistake again. When the skill file gets big, I ask Claude to clean and compact it. It does a great job. It doesn't really make sense economically for…
Wait till you try codex so you don’t have to keep saying ‘don’t be lazy’
Re: Over-editing refers to a model modifying code beyond what is necessary
#199Here, the author means the agent over-edits code. But agents also do "too much": as in they touch multiple files, run tests, do deployments, run smoke tests, etc... And all of this gets abstracted away. On one hand, its incredible. But on the other hand I have deep anxiety over this: 1. I have no real understanding of what is actually happening under the hood. The ease of just accepting a prompt to run some script th…
I essentially have 3 modes: 1. Everything is specified, written and tested by me, then cleaned up by AI. This is for the core of the application. 2. AI writes the functions, then sets up stub tests for me to write. Here I’ll often rewrite the functions as they often don’t do what I want, or do too much. I just find it gets rid of a lot of boilerplate to do things this way. 3. AI does everything. This is for experimen…
This is the way imo, at least for now.
Re: Over-editing refers to a model modifying code beyond what is necessary
#200I'm either in a minority or a silent majority. Claude Code surpasses all my expectations. When it makes a mistake like over-editing, I explain the mistake, it fixes it, and I ask it to record what it learned in the relevant project-specific skills. It rarely makes that mistake again. When the skill file gets big, I ask Claude to clean and compact it. It does a great job. It doesn't really make sense economically for…
The article has a benchmark and Opus has best score in two categories and the second-best in another (there are only three categories). Opus is probably the best choice when it comes to producing readable code right now. GPT (for example) lags way behind.
Anecdotally it’s the exact opposite for me: gpt 5.4 is leagues ahead of opus for the kind of backend work I do. Opus keeps making stupid mistakes while overengineering the irrelevant parts. However when I have to work on the backoffice ui, I still pick opus.