

It’s like trying to prove an author didn’t use a ghostwriter. You might be able to find some clues, but the smaller the sample and the more cleanup the author did, the less chance there is to detect it.
Now what if they’re using AI for debugging? Code from the AI may not even make it into the project, but that doesn’t mean AI wasn’t used. So how do you enforce a “no AI” policy in that scenario?
If there’s no practical way to enforce a rule or tell if it has been broken, it’s a pointless rule. Better programmers than me have settled on the policy of “If you track in shit on your shoes, you will be the one cleaning it up, and may well be told to not come back if you do.” Make people responsible for the code they submit, and if they can’t do it right, however they do it, don’t merge their code and kick them out.

I’ve been using duck for at least 3 years, probably closer to 6 or 7. When I first used it, its searches were okay, but if I couldn’t find what I was looking for a quick trip to Google would fix that. I felt like it improved slightly over some time, but also Google got a lot worse. Now with the AI proliferation, I never bother going to Google, and duck is still better than it was a year or two ago. Their AI has about a 20 or 30% success rate for me, but I just use it as a top search if I use it at all. I would love it if the results didn’t change when I run the same search 2 minutes apart, though.