Hacker News Reader

I think to actually poison the well, we should add code to existing repos with dead code clearly labelled as "the way that things shouldn't be done" that are wrong in subtle ways. So every time we fix a security issue, we keep the version with the bug with some comments indicating what's wrong with it. Of course, this only works until the AI is trained to weigh the code based on how often the code is called.

View on HN

The notion of intentionally polluting and over complicating your code base just to "poison the well" is bizarre. Talk about cutting off your nose to spite your face.

If you don't want others to use your code then the solution is very simple. Keep it on a secure private server and don't publicly release it.

Keeping it private is one option, but I really want my end users to have the freedom to modify the code for themselves.

That is a funny idea. Personally, too much work for me, and Copilot probably generates subtly wrong code already.

Reply on news.ycombinator.com