If a SW dev applicant gives a 20-file generated output for a 20-line assessment problem and can’t explain single lines of “their” code, either what they should be doing or why “they” had written it, it’s gonna be a no from me, dawg. A standard problem might have different solutions, but fixing the issue of the day to the satisfaction of a rabidly vocal customer base might have one at most, and it will change multiple times on a whim.
So the LLM might have helped them cheat their way to an MSc, but there’s no cheating your way through real life.
If a SW dev applicant gives a 20-file generated output for a 20-line assessment problem and can’t explain single lines of “their” code, either what they should be doing or why “they” had written it, it’s gonna be a no from me, dawg. A standard problem might have different solutions, but fixing the issue of the day to the satisfaction of a rabidly vocal customer base might have one at most, and it will change multiple times on a whim.
So the LLM might have helped them cheat their way to an MSc, but there’s no cheating your way through real life.
What you’re describing is “vibe coding”. For the difference between vibe coding and engineering, I’ll refer you to my previous comment.
Edit: had problems with opening your link, replying to your linked comment now…