this post was submitted on 13 Dec 2025
477 points (99.0% liked)
Linux
10784 readers
979 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So then the policy doesn't make sense and should focus on what specific issues are associated with llm-generated code that are problematic. For example, I've seen llms generate fairly unreadable loops because it uses weird variable names. That's a valid offense to criticize.
However I've also read C code before so I've seen an obscene amount of human generated code with shitty variable names that don't mean anything. So why is the shitty human C code ok but shitty LLM code is not? And if no shitty code is accepted (it's gnome so I doubt that), then why does anyone need a new rule?
i'd love to review some of the code that you personally wrote.
That's cool, but why? I tend to use longer variable names that are mostly self-explanatory because, well, intellisense exists so I don't really need to make them short.
did you read their statement? they do.
Yes, it says there was an unnecessary try/catch, that's pretty weak if that's the only reason.
read their text again, the problem is that people submit code that they don't understand. and this will grow the more people decide to stay stupid / employ LLMs.
Well that's an assertion they are claiming, maybe. I see people on lemmy claim that all of the time about people who use LLM tools but thinking a thing doesn't make it fact.
Edit: I just reread the blog and actually see zero mention of that claim. So I'm not sure where you're reading that I'm not seeing.