Re:The Knowledge Economy Is Over. Welcome to the Allocation ...
by ta988 on Saturday January 20, 2024 @11:43AM
(#39069416)
This is our experience as well and is an immediate rejection if the person is not honest about it. If they say "i need to check this quickly on a search engine or chatgpt" that's fine. But if they make it sound like it is their own answers, that's dishonesty and you don't want to work with people you can't trust when you are given the choice.
Re:The Knowledge Economy Is Over. Welcome to the Allocation ...
by cynicalsecurity on Saturday January 20, 2024 @12:02PM
(#39069687)
You caught only those who are just bad at lying.
Re:The Knowledge Economy Is Over. Welcome to the Allocation ...
by ta988 on Saturday January 20, 2024 @01:01PM
(#39070367)
Potentially yes, but that still reduce the population of liars in the end.
If you have a recipe to catch people good at lying I'm all ears.
Re:The Knowledge Economy Is Over. Welcome to the Allocation ...
by cynicalsecurity on Saturday January 20, 2024 @04:49PM
(#39072763)
Onsite interviews.
Re:The Knowledge Economy Is Over. Welcome to the Allocation ...
by tonyarkles on Saturday January 20, 2024 @11:05AM
(#39068908)
Back when I was marking assignments in university that was by far the most reliable way to catch cheating: two assignments with the same quirky error in the same spot. It didn’t even have to be a shared code/logic error; a misspelled comment or variable name was enough to mentally pop up a red flag and go back to find the other assignment with the same error in it.
On some of the assignments we gave out we would provide a set of, say, 10 initial test cases that the students could use to verify their work with the expectation that they would write more of their own. As a marking team we would also generate our own more detailed test suite; partly to make our job easier, partly to try to identify trends of places where students might not be understanding the course material. That ended up being another interesting way to identify plagiarism: if only 2 or 3 assignments failed a given unit test we would go and look to see if the implementations on those assignments was identical…
I interview remotely. The long pauses that get longer as the questions go from superficial to "you need to have done this for a while to know" are frustrating and obvious but also a great indicator if what is going on.
I always ask "what is happening during the long pauses". No one yet has said " I'm thinking". That's probably because I have always said going in "if you need time to think, or don't know, we can just talk about your thought process; noone knows everything and we all learn as we go". So a non-threatening out exists.
Only happened a few times.
Last time I had a senior dev on the call typing in the questions to chatgpt as we went and he was getting the same answers as the candidate with points in the same order. Some of these were wrong in very specific ways.