[axegon_]

Disagree: I applaud them for doing this. Anyone that says they've reviewed the 1000 lines of slop any AI has spit out is simply lying to everyone and even potentially themselves and has never done a single extensive code review in their life. Reading 1000 lines of text is one thing, reading and analyzing the complexity implications and edge cases in code - no chance. The "I've reviewed the slop" response is the reasons why 0 days and leaks are happening more than ever: because no one really reads the code cause "I vibe-coded it". An extensive and comprehensive code review may take days, and no slopper has ever done that. I'll get a 100 line pr and going over it can easily take hours, especially when something looks wrong and I need to test it. And it's a good reason why I'd never trust the "You are absolutely correct, apologies for the oversight, here's a revised version:"

[nonethewiser]

>Disagree: I applaud them for doing this. Anyone that says they've reviewed the 1000 lines of slop any AI has spit out

You're assuming the thing in question - that it's just AI slop. They dont offer any insight on that - they merely say he used Claude Code a lot. It shows a real lack of understanding of AI tools to equivocate those two things.

[axegon_]

No, it shows responsibility and critical thinking: I don't care if it's slaupecode, alanturingai++ code or whatever other slop machine anyone uses. It's the fact that no one and I mean NO ONE is capable of code reviewing that much crap and everyone that has written any code that was meant to last knows it: pouring a ton crap of code, even as a human, is the easy part if you learn the basics. The hard part is analyzing the problem, considering and addressing edge cases, exploits, memory leaks, resources, constraints and limitations - this is what a programmer is fundamentally responsible for and this is the only skill that matters. The code is just an abstraction, which was never the issue. Sloppers wash their hands with "look at how good it works" and "look at how beautiful the code is" and it's all fun and games before a production system crashes because, as I said, no slopper or an actual programmer has the ability to review 6000 line merge request so they hit "lgtm". Or better yet, outsource the problem to another slop machine. Anyone who believes that "AI tools" are in any shape or form viable for production, clearly do not understand a fundamental concept, called propagation of uncertainty[1].

"Sooo productive", sure, buddy, and when it breaks you have no idea why it broke and ultimately you don't know the codebase. Instructions.md containing:

``` * make no mistakes * don't hallucinate ```

Is the clear-cut evidence that we are speed running towards a technological apocalypse. Ironically, I'm in favour of it: if the house has to burn down for things to get better and people to get back to using their brains, I'm all for it.

[1] https://en.wikipedia.org/wiki/Propagation_of_uncertainty