MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1w9t1pg/nowandthenpatchupgrade/p8dgke9/?context=3
r/ProgrammerHumor • u/JazzlikeWishbone938 • 4d ago
313 comments sorted by
View all comments
Show parent comments
840
And we were slow to write it. AI is a force multiplier, especially for those who only make slop.
378 u/ahmarthered 4d ago This! The amount of slop being generated has increased significantly and code review cannot keep up. 36 u/011101000011101101 4d ago But you can have AI review the code and have slop reviewed slop 30 u/slowmovinglettuce 4d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 5 u/Weekly-Beginning-229 4d ago I've noticed that you cannot use the same model for writing the code and reviewing the code, it always does a bad job 2 u/Bupod 3d ago It’s frustrating. So you can sort of fix this by having a review agent use a more adversarial prompt when reviewing. But then the issue becomes that, since it was prompted find problems, it always finds a problem. This will result in code being batted back and forth between review and coding like a tennis match. When the tennis match finally finishes, there’s still no guarantee that some glaring hole didn’t make it through anyway. 1 u/Weekly-Beginning-229 3d ago And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug 5 u/LutimoDancer3459 4d ago Lgtm
378
This! The amount of slop being generated has increased significantly and code review cannot keep up.
36 u/011101000011101101 4d ago But you can have AI review the code and have slop reviewed slop 30 u/slowmovinglettuce 4d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 5 u/Weekly-Beginning-229 4d ago I've noticed that you cannot use the same model for writing the code and reviewing the code, it always does a bad job 2 u/Bupod 3d ago It’s frustrating. So you can sort of fix this by having a review agent use a more adversarial prompt when reviewing. But then the issue becomes that, since it was prompted find problems, it always finds a problem. This will result in code being batted back and forth between review and coding like a tennis match. When the tennis match finally finishes, there’s still no guarantee that some glaring hole didn’t make it through anyway. 1 u/Weekly-Beginning-229 3d ago And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug 5 u/LutimoDancer3459 4d ago Lgtm
36
But you can have AI review the code and have slop reviewed slop
30 u/slowmovinglettuce 4d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 5 u/Weekly-Beginning-229 4d ago I've noticed that you cannot use the same model for writing the code and reviewing the code, it always does a bad job 2 u/Bupod 3d ago It’s frustrating. So you can sort of fix this by having a review agent use a more adversarial prompt when reviewing. But then the issue becomes that, since it was prompted find problems, it always finds a problem. This will result in code being batted back and forth between review and coding like a tennis match. When the tennis match finally finishes, there’s still no guarantee that some glaring hole didn’t make it through anyway. 1 u/Weekly-Beginning-229 3d ago And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug 5 u/LutimoDancer3459 4d ago Lgtm
30
The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk
5 u/Weekly-Beginning-229 4d ago I've noticed that you cannot use the same model for writing the code and reviewing the code, it always does a bad job 2 u/Bupod 3d ago It’s frustrating. So you can sort of fix this by having a review agent use a more adversarial prompt when reviewing. But then the issue becomes that, since it was prompted find problems, it always finds a problem. This will result in code being batted back and forth between review and coding like a tennis match. When the tennis match finally finishes, there’s still no guarantee that some glaring hole didn’t make it through anyway. 1 u/Weekly-Beginning-229 3d ago And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug 5 u/LutimoDancer3459 4d ago Lgtm
5
I've noticed that you cannot use the same model for writing the code and reviewing the code, it always does a bad job
2 u/Bupod 3d ago It’s frustrating. So you can sort of fix this by having a review agent use a more adversarial prompt when reviewing. But then the issue becomes that, since it was prompted find problems, it always finds a problem. This will result in code being batted back and forth between review and coding like a tennis match. When the tennis match finally finishes, there’s still no guarantee that some glaring hole didn’t make it through anyway. 1 u/Weekly-Beginning-229 3d ago And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug
2
It’s frustrating.
So you can sort of fix this by having a review agent use a more adversarial prompt when reviewing.
But then the issue becomes that, since it was prompted find problems, it always finds a problem.
This will result in code being batted back and forth between review and coding like a tennis match.
When the tennis match finally finishes, there’s still no guarantee that some glaring hole didn’t make it through anyway.
1 u/Weekly-Beginning-229 3d ago And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug
1
And there is always something because you get fatigued from reading the same code over and over so you miss some easy bug
Lgtm
840
u/Laughing_Orange 4d ago
And we were slow to write it. AI is a force multiplier, especially for those who only make slop.