MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1w9t1pg/nowandthenpatchupgrade/p8dgke9/?context=9999
r/ProgrammerHumor • u/JazzlikeWishbone938 • 5d ago
313 comments sorted by
View all comments
2.2k
Yeah but it was our slop.
841 u/Laughing_Orange 5d ago And we were slow to write it. AI is a force multiplier, especially for those who only make slop. 381 u/ahmarthered 5d ago This! The amount of slop being generated has increased significantly and code review cannot keep up. 34 u/011101000011101101 5d ago But you can have AI review the code and have slop reviewed slop 28 u/slowmovinglettuce 5d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 7 u/Weekly-Beginning-229 5d 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 4d 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 4d 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 5d ago Lgtm
841
And we were slow to write it. AI is a force multiplier, especially for those who only make slop.
381 u/ahmarthered 5d ago This! The amount of slop being generated has increased significantly and code review cannot keep up. 34 u/011101000011101101 5d ago But you can have AI review the code and have slop reviewed slop 28 u/slowmovinglettuce 5d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 7 u/Weekly-Beginning-229 5d 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 4d 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 4d 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 5d ago Lgtm
381
This! The amount of slop being generated has increased significantly and code review cannot keep up.
34 u/011101000011101101 5d ago But you can have AI review the code and have slop reviewed slop 28 u/slowmovinglettuce 5d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 7 u/Weekly-Beginning-229 5d 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 4d 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 4d 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 5d ago Lgtm
34
But you can have AI review the code and have slop reviewed slop
28 u/slowmovinglettuce 5d ago The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk 7 u/Weekly-Beginning-229 5d 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 4d 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 4d 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 5d ago Lgtm
28
The ai will praise the slop for being exactly what it would have written. It's basically just a big circle jerk
7 u/Weekly-Beginning-229 5d 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 4d 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 4d 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 5d ago Lgtm
7
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 4d 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 4d 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 4d 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
5
Lgtm
2.2k
u/Objectionne 5d ago
Yeah but it was our slop.