this post was submitted on 19 Feb 2026
71 points (97.3% liked)

Programming

26072 readers
134 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

Publication croisée depuis https://programming.dev/post/46030028

About enshitification, open source and AI pollution

top 3 comments
sorted by: hot top controversial new old
[–] middlemanSI@lemmy.world 10 points 3 weeks ago

Sad state of afairs. Many awesome projects will get tainted into history.

[–] douglasg14b@lemmy.world 5 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

We combat this with, funny enough, AI code review.

Much MUCH stricter structural, consistency, quality, and discovery standards on code through rules and docs. Well defined expectations, stricter testing standards...etc Then let some agents loose on PR review and they catch all sorts of problems. Especially with other AI slop.

Coincidentally, the process of doing all this actually reduces the sloppiness of the slop that we receive, as the AI tools writing this code consume these rules before generating code.

[–] eager_eagle@lemmy.world 4 points 3 weeks ago

yeah, I really don't get maintainers that try to put human hours to review PRs that are potentially AI generated. This equation will never balance out. There needs to be a first triaging layer that is automated, only then bring a human in the loop if it's worth continuing.