Earlier quoted context omitted.
For Computer Science Ph.D.'s, I think you should get credit for writing code. Either production-quality open source code, or pedagogical code. I'm looking at the Stanford Pintos kernel and MIT xv6 kernel. While there were minor papers from those projects, I think they were more like a labor of love. When you consider the coding effort, those projects probably took 10x the effort than a typical paper. But yeah it woul…
Part of being a scientist is learning how to communicate your results. And anyway, writing is required for good thinking. As a PhD student implementor, yes, my theory colleagues get way more publications than I hypothetically could even if I were a better student than I am. That makes it hard to get an academic job, but otherwise doesn't matter too much.
“Close to 10% of the papers we receive show some sign of academic misconduct”
21–30 of 49 posts
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#22Earlier quoted context omitted.
For Computer Science Ph.D.'s, I think you should get credit for writing code. Either production-quality open source code, or pedagogical code. I'm looking at the Stanford Pintos kernel and MIT xv6 kernel. While there were minor papers from those projects, I think they were more like a labor of love. When you consider the coding effort, those projects probably took 10x the effort than a typical paper. But yeah it woul…
I'm not sure you can really write production quality code in a Ph.D., because that requires a production environment, which just isn't available in academia, and also because writing such code conflicts with research goals.
Your second argument is circular -- I'm saying a valid research goal should be to write solid and useful code, and then explain it.
For example, you could write an OS kernel or kernel subsystem to fill some particular part of the design space. A great but rare example is what the authors of Lua have done.
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#23To make matters worse, the same experimental setup is frequently used to run experiments that result in several publications. When you have several papers authored by different overlapping groups of researchers in various stages of review simultaneously things can get very confusing. The first paper you submit is frequently the last one published. The last paper you submit will then wind up referencing arxiv pre-prints instead of published articles, and if you did plagiarize yourself by mistake, the publisher of the paper submitted last might have absolutely no chance of detecting it. On top of it all, there is frequently interference from editors and reviewers. A well-written and coherent paper on a theory an experiment testing that theory might be considered "too long" or "too confusing" by a referee, and the editor will jump on that comment and demand the paper be split into two, sometimes only one of which they feel like publishing in their journal. If the researcher had done this of his/her own initiative many would consider it CV-padding!
Yes, self-plagiarism can be a means to pump up your publication list, but it also happens innocently because publishing is such a confusing counter-intuitive mess! It's probably an idiotic idea, but some kind of pan-journal version control system, even just for figures, would be a tremendous headache reducer if done right!
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#24Important issue. It is good to see Elsevier, a publisher often thought to be more concerned with profits, highlighting the problem.
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#25Earlier quoted context omitted.
For Computer Science Ph.D.'s, I think you should get credit for writing code. Either production-quality open source code, or pedagogical code. I'm looking at the Stanford Pintos kernel and MIT xv6 kernel. While there were minor papers from those projects, I think they were more like a labor of love. When you consider the coding effort, those projects probably took 10x the effort than a typical paper. But yeah it woul…
I'm not sure you can really write production quality code in a Ph.D., because that requires a production environment, which just isn't available in academia, and also because writing such code conflicts with research goals.
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#26Half the plagiarism violations are "self-plagiarism", which I assume means copying from your own previously published works. Hardly seems like such an ethical problem to copy from yourself except of course if you're paid by the word.
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#27Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#28Half the plagiarism violations are "self-plagiarism", which I assume means copying from your own previously published works. Hardly seems like such an ethical problem to copy from yourself except of course if you're paid by the word.
I felt a little uneasy reading this in the article. I write CS conference papers that are all in the same area, so obviously, some of the background information (which is a pretty small part of the overall paper) is basically copied from paper to paper. And that part is the most polished. I don't feel uneasy because I'm doing anything remotely unethical---I'm not. I feel uneasy because it sounded a bit like the descr…
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#29Half the plagiarism violations are "self-plagiarism", which I assume means copying from your own previously published works. Hardly seems like such an ethical problem to copy from yourself except of course if you're paid by the word.
It increases the amount of crap out there, plus it pads the CV
Plus, if the competition wasn't so gruesome and that evaluation criteria weren't shallow, the pressure to pad one's CV wouldn't be so great.
"Holy ethical violation batman, the slaves are slipping out of their manacles and they certified on their honor they would not do that"
Re: “Close to 10% of the papers we receive show some sign of academic misconduct”
#30Earlier quoted context omitted.
It increases the amount of crap out there, plus it pads the CV
Sure but crap as such isn't an ethical problem. In fact, theoretically it would be the job of publications, not authors, to prevent crap from being published. Plus, if the competition wasn't so gruesome and that evaluation criteria weren't shallow, the pressure to pad one's CV wouldn't be so great. "Holy ethical violation batman, the slaves are slipping out of their manacles and they certified on their honor they wou…
I know it's an oversimplification, but the essence of it is true: curing cancer is already hard enough. It shouldn't be made any harder by ambitiously exceeding your dead tree quota.
Sauce: abandoned an academic career :-)