3 ms·
Fully agree. The very 1st thing you do after you get a proposed set of changes from an AI model is to review them carefully before applying them. Most of the t
by asam-0 1y ago
Fully agree.
The very 1st thing you do after you get a proposed set of changes from an AI model is to review them carefully before applying them. Most of the time it duplicates code because it skipped specific tokens or context that was out of it's window and the user didn't include it in their prompt.
Batch applying any changes is just a way to create even harded code to debug and accumulating such bulk code injections will definietly break your code much earlier than you think.
B, Sam
- bhaktatejas922 1y agoif you've used cursor, you've probably felt how seamless fast apply can feel - fast apply is accurate and fast to the point where most don't even realize its a model
- animuchan 1y agoAbsolutely, when stuff runs fast it's better UX compared to when the stuff runs slow. I think what parent comments suggest is, the speed of applying a diff is not the major bottleneck in LLM-assisted coding, and improvements in other aspects are much more desirable (e.g. correctness, or even speed of thinking models themselves). In a world where diff application is a real pain point, it's likely one of the last pain points in the field.