SoylentNews is people
SoylentNews
A PhD student who shot and killed a professor before killing himself claimed that the professor had stolen his code:
The student who shot and killed his engineering professor and then himself at a Los Angeles university had accused the professor of stealing his code.
In a blog post on March 10, Mainak Sarkar, 38, said Professor William Klug, 39, "is not the kind of person when you think of a professor. He is a very sick person. I urge every new student coming to UCLA to stay away from this guy." He continued: "I was this guy's PhD student. We had personal differences. He cleverly stole all my code and gave it another student. He made me really sick. Your enemy is your enemy. But your friend can do a lot more harm. Be careful about whom you trust. Stay away from this sick guy." The post has since been taken down.
On Wednesday, nearly three months after posting it, and seemingly upset at poor grades, Sarkar drove from his home in Minnesota to Los Angeles where he confronted and gunned down Professor Klug at the university's engineering complex. Sarkar then turned the gun on himself and killed himself. The Los Angeles Times quoted an unnamed UCLA source as saying the allegation that Klug stole his student's code was "absolutely untrue."
The professor's name was found on a "kill list" written by Sarkar, along with another professor who wasn't on campus at the time of the shooting and has been confirmed to be safe. Sarkar reportedly killed his estranged wife in Minnesota before traveling to UCLA. Also at Los Angeles Times , The New York Times , CNN.
(Score: 4, Insightful) by TrumpetPower! on Friday June 03 2016, @08:54PM
Perhaps, but there's all sorts of reasonable ways it might have gone down, too. For example, the student could have written code in the same spirit as the teacher -- what students typically do, after all -- and then saw the teacher later writing code the same way the teacher always had as "evidence" that the teacher was now copying the student. Or the teacher could have drawn inspiration from the student and adapted one of the student's innovations the same way we all adapt each others's innovations. The student could even have written a library explicitly intended from the start to be shared by the department and gotten upset when people later did exactly that.
And, of course, the teacher could have plagiarized the student or the student could have been completely off his rocker.
Lacking specifics, I wouldn't get too hung up on the copying question since, regardless...
MURDER IS NOT AN ACCEPTABLE ANSWER TO PLAGIARISM!
If the student's claims actually had merit, he could have ended his teacher's career. Academic dishonesty is even less tolerated when faculty do it than when students do it. All he had to do was prove his case, even just in the court of public opinion, and the teacher's career would have been over.
But killing the guy?
Seriously. WTF!?
b&
All but God can prove this sentence true.
(Score: 1, Touché) by Anonymous Coward on Saturday June 04 2016, @05:21AM
A PhD student cannot claim "intellectual property" on code developed for the project. Unless it's code that's obviously not related to his project and field, it belongs to the department anyway, because it's written in the interest of the PhD project.
I assume in very specific circumstances, e.g. the student not being paid, they could claim copyright, but even in that case if the code came about after discussions with the teacher it's shared work...
As far as plagiarism is concerned, that's harder to assess, although in 2016 there should already be some checking mechanisms in place at universities.
In any case, I fully agree that killing the offender is not a solution for plagiarism/copyright infrigement. My personal opinion is that the concept of copyright is flawed in any case, but that's another discussion.