407
True story that might have happened today
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Jan 2026
407 points (98.3% liked)
Programmer Humor
28818 readers
736 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Forgetting AI for a moment, I am always shocked when I am reviewing a coworker's code and it's obvious that they themselves didn't review it.
Like, they sent me a PR that has a whole shitload of other crap in it. Why should I look at it when you haven't looked at it? If you don't review your own review requests, you're a failure of a ~~programmer~~ human.
And I would be a failure if I approved such a request.
Getting back to the post, where is all of the review? The coworker should have reviewed the AI shit, whether it was code or documentation. The person who approved the PR should have reviewed it, as well.
Every business with more than one programmer should have at least two levels of safeguards against this exact thing happening. More if you include different types of test suites.
This post describes a fundamentally broken business, regardless of the AI angle, and so it's good if everything is broken. With such a lack of discipline and principles, I say let the business fail.
Yeah, we are falling into a little bit of this where I work right now. It’s a bit of a change of mindset to begin thinking that you can’t trust a PR even a little. Yes, you should be able to but humans are humans and we get lazy and trusting the magic pattern machine is gonna impact everyone’s life in a lot of ways
It has never occurred to me that other people trust PRs, even a little. I mean, that they might think about it in those terms.
This explains a lot to me.
Why does it take me longer to review code than other people? They trust the person who wrote it, but I don't.
Why is it that when my coworkers think a person is untrustworthy, that they always end up begging me to do all of that person's reviews. It's because I'm not bothered by that. I already treat everybody as untrustworthy.
I've never understood how other people think when they do reviews, I guess.
That's really not a good sign, though. A review process to check for basic sanity is just a bandaid fix for a lack of discipline, which ultimately requires more work to be done. So, the person that asked the magic pattern machine should review that code, as they should be deeper into the context of what needs to be done, and they know which parts of the code were generated and which parts they actually logically thought about.
Yeah, we have some basic problems in there.
The documentation was from the framework. Basically the thing was misconfigured, it was said that it would do something, but that something is impossible and some of those config variables don't even exist. On top of that, the microservice got a lot worse because of the configuration (losing information kind of worse), it would have been better with the defaults.