The GNOME.org Extensions hosting for GNOME Shell extensions will no longer accept new contributions with AI-generated code. A new rule has been added to their review guidelines to forbid AI-generated code.
Due to the growing number of GNOME Shell extensions looking to appear on extensions.gnome.org that were generated using AI, it’s now prohibited. The new rule in their guidelines note that AI-generated code will be explicitly rejected
You used to be able to tell an image was photoshopped because of the pixels. Now with code you can tell it was written with AI because of the comments.
and from seeing quite a few slops in my time
Emojis in comments, filename as a comment in the first line, and so on
I’ve been in the habit of putting the filename as first comment in most of my scripts forever. I don’t know when or why I started but please don’t make me change!
You’re absolutely right — we shouldn’t have to change our style just because a machine copies it.
Put a random fuck in the comment to differentiate yourself
// not AI slop. This is pure human slop! // I appreciate pull requests from people smarter than me.
it’s how example code is often written when it’s i. a book or a webpage… there’s not really a good reason to do it in a real file because it’s in the filename.
but if it helps you organize it doesn’t hurt anything.
I add a comment to he first line of unsaved files because that’s what Code displays for the tab name and it either helps or confuses me about what is in the tab.
Isn’t fine name in the comment in the first line default behavior for multiple IDE/boilerplate generations?
They werent hiding it, they started with vibe
# Optional but […]
edit to explain my very vague comment: ChatGPT loves to offer code with some lines commented as “Optional [… explanation]”. You can easily tell AI code when the monologuing comments are left in