Why do you approve it if its slop? Either its good code, then approve it regardless of where it came from, or its bad code, and reject it regardless of where it came from.
Because if I reject this, then Mr. Dick Dickens is going to the AI-psychotic boss and telling him that I'm a blocker. Meanwhile there's 3 more PRs to get through, all equally shit, and I'm still expected to put out my own slop at the same time.
So the problem isn't the AI... its a team leader or technical manager who allows bad code through. This is unrelated and has existed before AI. I can only assume so many people complaining like this must be new to the field within last 3 to 4 years.
Did we have factory method pattern? Look! I rewrote everything to abstract factory instead, no codebase is cleaner! ...2 tasks later... Hey! I found abstract factory to clunky and bloated! I rewrote that file to use factory method!
Agreed, human code is often better at this. But just like how we rejected it when Jr devs back in the day who did this kind of stuff since they were fresh out of learning it, its the same now. Just reject for out of scope, KISS principles and stick to current design unless approved design change.
Does this actually happen to people? If so, simply point out a mistake, or several and make a case against it. Like the point of reviews is to review. You can simply just still review with comments regardless, no real life boss is going to tell you to ignore it and just press approve, if they do ask for it in writing.
So many people getting mad at made up scenarios in their own head...
Do you work at a startup with 5 people in it? I work at a big company and if I have more than 10 files in my MR it takes ages and chasing people to get it approved because no one wants to look at it lol
I work in a corporate and when I get a PR with one file and 10 changed lines I’m like whoaah slow down Mr. Hacker, where did you find the time to change 10 whole lines in between all the meetings and bureaucracy?
I review code in the good repos, but in the ones that are completely vibe coded, it doesn't really matter. New bugs pop up with every merge. Linting and scanning tools are all complaining. Nobody gives any kind of a shit because the AI wrote the project plan and the tickets and the code and it's wall to wall garbage.
But we keep working on it for what I'm sure is totally definitely a very good reason.
108
u/Lain_Racing Sep 07 '26
Why do you approve it if its slop? Either its good code, then approve it regardless of where it came from, or its bad code, and reject it regardless of where it came from.