The title threw me off. When I read self-plagiarism, I read that as using your own work that you already wrote before. Reading into it a little more revealed the catch. He took content he wrote for another publication and used it for his current publication. The issue is: who owns it, the publication or the writer? As the author points out, it comes down to what's in the writer's contract, although I have to agree with the author: even if it was in the writer's contract that he retains copyright over his articles and he is legally permitted to reuse his work for other publications, it just doesn't feel right that he used work someone else paid him to do to finish work his current employer is paying him to do.
even if it was in the writer's contract that he retains copyright over his articles and he is legally permitted to reuse his work for other publications, it just doesn't feel right that he used work someone else paid him to do to finish work his current employer is paying him to do.
If programmers thought like this, we would all still be using ENIAC.
Comments
The title threw me off. When I read self-plagiarism, I read that as using your own work that you already wrote before. Reading into it a little more revealed the catch. He took content he wrote for another publication and used it for his current publication. The issue is: who owns it, the publication or the writer? As the author points out, it comes down to what's in the writer's contract, although I have to agree with the author: even if it was in the writer's contract that he retains copyright over his articles and he is legally permitted to reuse his work for other publications, it just doesn't feel right that he used work someone else paid him to do to finish work his current employer is paying him to do.
even if it was in the writer's contract that he retains copyright over his articles and he is legally permitted to reuse his work for other publications, it just doesn't feel right that he used work someone else paid him to do to finish work his current employer is paying him to do.
If programmers thought like this, we would all still be using ENIAC.