The problem is that now, when your colleagues/contributors push out shitty code that you have to fix... you don't know if they even tried or just put in bad code from an LLM.
You don't need to. Focus on the work, not the person.
I recall a coworker screaming at a junior developer during a code review, and I set up a meeting later on to discuss his reaction. Why was he so upset? Because the junior developer was being lazy and not trying.
How did he know this?
He didn't. He used very dubious behavioral signals.
This was pre-LLM. As applicable now as it was then. If their code is shitty, let them know and leave it at that.
On the flip side, I often review code that I think has been written by an LLM. When the code is good, I don't really care if he wrote it or asked GPT to write it. As long as he's functioning well enough for the current job.
I work for a university. I have literally caught student workers putting the result of an LLM in the code without reading it, because they did it during screen sharing. You can't teach somebody who does not want to learn (because they just want to pass the semester and have no incentive to try hard). Now it's just way more easy to pretend to have put in effort.
It's also natural to ask why you think the growing fraction is because they cheated.
Look, I don't know how old you are, but the quality of the average developer has been dropping for decades. Prior to GPT, I routinely had to deal with developers who refused to learn anything (e.g. version control) and needed hand holding.[1] They didn't want to read man pages, etc. It's silly to suddenly get upset because LLMs are yet another reason for this phenomenon.
If there's a problem, it's hiring practices. Not LLMs.
> Especially because you can't know which fraction tried their best and deserve patience and mentoring, and which fraction are lying and wasting your time.
Given your comments, it's trivial to see why they would lie to you. They wouldn't to me, because I'm not going to discourage LLM usage.
> I work for a university.
Even before I read your comment, I was about to point out how your stance is valid in the domain of education, and not the workplace. And you just validated it :-)
The concept of cheating when it comes to education is vastly different compared to the work place. The goal of teaching is to learn, and even more relevant, for teachers to evaluate how well someone is learning. If they're using LLMs (or calculators, for that matter), then it becomes harder to evaluate. The goal is not to get something done, but to learn. That's why the environment in school is very constrained, and very different.
The worst jobs I've had are when people failed to realize that they're now in a different environment and they continue to apply those principles where they don't make sense. The main goal at work is to get something done, regardless of the tools.[2]
If someone tries to put good code in, stop caring if it comes from an LLM.
If someone tries to put bad code in, stop caring if it comes from an LLM.
[1] And yes, today's LLMs do a better job than many crappy developers I've had to put up with. Had LLMs existed back than and they used them, I'd be a happier man.
[2] As long as you're not violating laws, copyright, licenses, patents, etc.
It's a very invalid point. Perhaps in your life you've never encountered people who cheat and later change their ways, but it's fairly common for them to change their ways.
Would you also say it's ok for people to steal because they might one day not-steal? So an increase in robberies does not hurt? I am not sure I understood you correctly.
Several people have asked you, and you still haven't explained why it's OK to waste time with "non-cheaters" and not with "cheaters".
> Would you also say it's ok for people to steal because they might one day not-steal?
No. Unless stealing is permitted, which it usually isn't. LLMs, OTOH, are merely a tool and their use has no morality attached to it. It's you that seem to attach some morality to LLM use.
(Of course, if your company disallows LLM usage, that's another story).
> I am not sure I understood you correctly.
Your comments seem to make the assumption that LLM based code is shittier than what a typical poor developer would write, which I pointed out in another comment is often not true.
Just treat the code based on its merit. If it's utter crap, tell the developer it's utter crap. Just stop second guessing whether he wrote it or an LLM did. There is a threshold below which even I won't review code.
Aside: it’s confusing that parent commenter used “cheating” in a completely different way than the title of the article.