[reader_mode]

>Although in my opinion, code review should be enough to catch any "accidental" incidents of plagiarism, the differences in writing style should make it very obvious when the employee has copied something.

You must do some CSI level code reviews. Best I'm able to do is figure out if code will work and if something can be done obviously better. Stylistic calls (beyond lint enforceable) are up to authors as far as I'm concerned.

And even then it's trivial to fix up naming schemes and such to march codebase - doubt that gets you out of copyright issues.

[zxzax]

I mean in cases where someone just copy and pastes something without making any effort to match the style, or in cases where they can't explain what a piece of code does or how they came up with it. You should be able to spot those very easily in code review. If somebody is trying to fix up the naming schemes to avoid being detected and for whatever reason is able to explain the code perfectly, then I'd imagine that person would probably be doing the same bad things regardless of using copilot -- it's not like it's hard to search stackoverflow and github for code snippets.

[reader_mode]

But I think copilot matches code style, no ?