this post was submitted on 29 May 2026
238 points (99.2% liked)

Programming

27246 readers
270 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] NotAnonymousAtAll@feddit.org 35 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

the consensus seems to be that adding instructions to code that sabotage other people’s work goes too far.

Citation needed. Personally I think it was fine in this case. I work with a lot of software developers (real ones, not vibe coders; but also not strictly anti-AI), and would expect most of them to agree and get a laugh out of it.

It was done in a way that can only cause any serious trouble for users who recklessly ignore decades of development best practices. Those users will run into a wall sooner or later anyway, better let it be something relatively harmless but still severe enough to get them to actually think about what they are doing and how to make their setup more robust.

[–] phoenixz@lemmy.ca 4 points 1 week ago

adding instructions to code that sabotage other people’s work goes too far.

I agree

AI is not a person and a person using AI isn't doing work. There is no problem here