3 ms·
This is where I landed too. Used Cursor for a while before realizing that it was actually slowing me down because the PR cycle took so much longer, due to all t
by rco8786 1y ago
This is where I landed too. Used Cursor for a while before realizing that it was actually slowing me down because the PR cycle took so much longer, due to all the subtle bugs in generated code.
Went back to VSCode with a tuned down Copilot and use the chat or inline prompt for generating specific bits of code.
- davidmurdoch 1y agoWhat is a "PR cycle"?
- klinquist 1y agoopen a pull request, reviewer finds a bug and asks for changes, you make changes and re-request a review...
- davidmurdoch 1y agoThat's what I was afraid of, I'd never think anyone submitting AI-generated code wouldn't first read it themselves before asking others to review it!
- rco8786 1y agoI read it myself. But if one person could catch every bug in code then we wouldn't need PR reviews at all would we?
- davidmurdoch 1y agoWell yes, but I personally would never submit a PRr I could use the excuse, "sorry, AI wrote those parts, that's why this PR has now bugs than usual". All that to say that the base of your argument is still correct: AI really isn't saving all that much time since everyone has to proof-read it so much in order to not increase the number of PR bugs from using it in the first place.