Should I include a copyright notice on job application submissions?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
3
down vote
favorite
A job for which I am applying has, as part of the application / interview process, a test which requests real source code. Should I include a copyright notice on this code?
I'm guessing the practice would be similar to portfolios for art folks, but for code in particular I think the opportunity to point out an interest in IP law ( and disapproval of related clauses of many employment agreements ) shouldn't be passed up.
software-industry applications
add a comment |Â
up vote
3
down vote
favorite
A job for which I am applying has, as part of the application / interview process, a test which requests real source code. Should I include a copyright notice on this code?
I'm guessing the practice would be similar to portfolios for art folks, but for code in particular I think the opportunity to point out an interest in IP law ( and disapproval of related clauses of many employment agreements ) shouldn't be passed up.
software-industry applications
2
If the code is yours, no reason not to. One other thing you can do is make a few subtle changes to the code that make it not function correctly and put a prominent note to that effect at the top. (Point here being that samples are to show your programming style.) Any shop smart enough to debug it probably doesn't need to steal it.
– Blrfl
Apr 8 '13 at 2:48
2
Do you want the job, or to make a point about IP law?
– Michael Kohne
Apr 8 '13 at 13:39
I figured worst case scenario, I can just say that my editor automatically inserts that stuff. For this particular assignment, I read the question as requiring 'real' code, so at least SOME copyright notice should go on it, along with things like unit tests.
– Sesquipedalian
Apr 8 '13 at 15:00
What kind of copyright notice are we talking about? A full-blown proprietary license, or a GPL/BSD style thing?
– acolyte
Apr 8 '13 at 16:03
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
A job for which I am applying has, as part of the application / interview process, a test which requests real source code. Should I include a copyright notice on this code?
I'm guessing the practice would be similar to portfolios for art folks, but for code in particular I think the opportunity to point out an interest in IP law ( and disapproval of related clauses of many employment agreements ) shouldn't be passed up.
software-industry applications
A job for which I am applying has, as part of the application / interview process, a test which requests real source code. Should I include a copyright notice on this code?
I'm guessing the practice would be similar to portfolios for art folks, but for code in particular I think the opportunity to point out an interest in IP law ( and disapproval of related clauses of many employment agreements ) shouldn't be passed up.
software-industry applications
edited Apr 8 '13 at 7:24
gnat
3,23273066
3,23273066
asked Apr 7 '13 at 22:44
Sesquipedalian
183
183
2
If the code is yours, no reason not to. One other thing you can do is make a few subtle changes to the code that make it not function correctly and put a prominent note to that effect at the top. (Point here being that samples are to show your programming style.) Any shop smart enough to debug it probably doesn't need to steal it.
– Blrfl
Apr 8 '13 at 2:48
2
Do you want the job, or to make a point about IP law?
– Michael Kohne
Apr 8 '13 at 13:39
I figured worst case scenario, I can just say that my editor automatically inserts that stuff. For this particular assignment, I read the question as requiring 'real' code, so at least SOME copyright notice should go on it, along with things like unit tests.
– Sesquipedalian
Apr 8 '13 at 15:00
What kind of copyright notice are we talking about? A full-blown proprietary license, or a GPL/BSD style thing?
– acolyte
Apr 8 '13 at 16:03
add a comment |Â
2
If the code is yours, no reason not to. One other thing you can do is make a few subtle changes to the code that make it not function correctly and put a prominent note to that effect at the top. (Point here being that samples are to show your programming style.) Any shop smart enough to debug it probably doesn't need to steal it.
– Blrfl
Apr 8 '13 at 2:48
2
Do you want the job, or to make a point about IP law?
– Michael Kohne
Apr 8 '13 at 13:39
I figured worst case scenario, I can just say that my editor automatically inserts that stuff. For this particular assignment, I read the question as requiring 'real' code, so at least SOME copyright notice should go on it, along with things like unit tests.
– Sesquipedalian
Apr 8 '13 at 15:00
What kind of copyright notice are we talking about? A full-blown proprietary license, or a GPL/BSD style thing?
– acolyte
Apr 8 '13 at 16:03
2
2
If the code is yours, no reason not to. One other thing you can do is make a few subtle changes to the code that make it not function correctly and put a prominent note to that effect at the top. (Point here being that samples are to show your programming style.) Any shop smart enough to debug it probably doesn't need to steal it.
– Blrfl
Apr 8 '13 at 2:48
If the code is yours, no reason not to. One other thing you can do is make a few subtle changes to the code that make it not function correctly and put a prominent note to that effect at the top. (Point here being that samples are to show your programming style.) Any shop smart enough to debug it probably doesn't need to steal it.
– Blrfl
Apr 8 '13 at 2:48
2
2
Do you want the job, or to make a point about IP law?
– Michael Kohne
Apr 8 '13 at 13:39
Do you want the job, or to make a point about IP law?
– Michael Kohne
Apr 8 '13 at 13:39
I figured worst case scenario, I can just say that my editor automatically inserts that stuff. For this particular assignment, I read the question as requiring 'real' code, so at least SOME copyright notice should go on it, along with things like unit tests.
– Sesquipedalian
Apr 8 '13 at 15:00
I figured worst case scenario, I can just say that my editor automatically inserts that stuff. For this particular assignment, I read the question as requiring 'real' code, so at least SOME copyright notice should go on it, along with things like unit tests.
– Sesquipedalian
Apr 8 '13 at 15:00
What kind of copyright notice are we talking about? A full-blown proprietary license, or a GPL/BSD style thing?
– acolyte
Apr 8 '13 at 16:03
What kind of copyright notice are we talking about? A full-blown proprietary license, or a GPL/BSD style thing?
– acolyte
Apr 8 '13 at 16:03
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
1
down vote
accepted
When making a decision on this I would ask myself what is it I hope to achieve. If the code is property of a third party company but you are submitting it as an example of the type of work that you do then including the third party copyright is appropriate so that you can indicate that the code is not owned by you and that you do not have permission to grant licence to use it. Generally I would follow the guidelines of the third party owner of the code, in the sharing of the code and the copyright status.
If the copyright to the code is owned by you and you have the right to grant licence to use it then you have a decision to make. Most companies I have worked with require that any code submitted be done so with a licence that would prevent my making a claim against them for any contents of code submitted to them in the application process. The reason is that you could submit some very easily duplicated code, then make a claim against them. So it is in their interests to demand the rights to use any code you submit to them.
For this reason I never include my "best" stuff. If there is a need I would remove the code that does work I wish to protect and insert a comment that the code is proprietary and you are unable to grant a blanket licence. If you feel the need to protect your code then you may be best served by contacting a lawyer and getting them involved in reviewing what you plan to submit to the client.
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
add a comment |Â
up vote
1
down vote
Legally, at least in the US, you own the copyright to anything you create the moment it is created (provided you aren't creating the work under a work-for-hire arrangement). So there is no legal need for it in that sense.
However, for a sense of pride, I say go for it. It certainly wouldn't hurt anything (and if anything, maybe would help as it shows you take some ownership in your work).
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
 |Â
show 4 more comments
up vote
0
down vote
Is this code that you write for the interview (like a coding test?), or pre-existing code that they want to see?
If it's pre-existing code, (for instance, something you did on your own time), then yes, absolutely keep the notices on there.
If it's written for the interview, then no, don't. If you are writing to answer a coding test, then putting a copyright notice on the answer indicates that you are more concerned with outside affairs than the problems they are looking to hire you to solve.
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
When making a decision on this I would ask myself what is it I hope to achieve. If the code is property of a third party company but you are submitting it as an example of the type of work that you do then including the third party copyright is appropriate so that you can indicate that the code is not owned by you and that you do not have permission to grant licence to use it. Generally I would follow the guidelines of the third party owner of the code, in the sharing of the code and the copyright status.
If the copyright to the code is owned by you and you have the right to grant licence to use it then you have a decision to make. Most companies I have worked with require that any code submitted be done so with a licence that would prevent my making a claim against them for any contents of code submitted to them in the application process. The reason is that you could submit some very easily duplicated code, then make a claim against them. So it is in their interests to demand the rights to use any code you submit to them.
For this reason I never include my "best" stuff. If there is a need I would remove the code that does work I wish to protect and insert a comment that the code is proprietary and you are unable to grant a blanket licence. If you feel the need to protect your code then you may be best served by contacting a lawyer and getting them involved in reviewing what you plan to submit to the client.
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
add a comment |Â
up vote
1
down vote
accepted
When making a decision on this I would ask myself what is it I hope to achieve. If the code is property of a third party company but you are submitting it as an example of the type of work that you do then including the third party copyright is appropriate so that you can indicate that the code is not owned by you and that you do not have permission to grant licence to use it. Generally I would follow the guidelines of the third party owner of the code, in the sharing of the code and the copyright status.
If the copyright to the code is owned by you and you have the right to grant licence to use it then you have a decision to make. Most companies I have worked with require that any code submitted be done so with a licence that would prevent my making a claim against them for any contents of code submitted to them in the application process. The reason is that you could submit some very easily duplicated code, then make a claim against them. So it is in their interests to demand the rights to use any code you submit to them.
For this reason I never include my "best" stuff. If there is a need I would remove the code that does work I wish to protect and insert a comment that the code is proprietary and you are unable to grant a blanket licence. If you feel the need to protect your code then you may be best served by contacting a lawyer and getting them involved in reviewing what you plan to submit to the client.
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
When making a decision on this I would ask myself what is it I hope to achieve. If the code is property of a third party company but you are submitting it as an example of the type of work that you do then including the third party copyright is appropriate so that you can indicate that the code is not owned by you and that you do not have permission to grant licence to use it. Generally I would follow the guidelines of the third party owner of the code, in the sharing of the code and the copyright status.
If the copyright to the code is owned by you and you have the right to grant licence to use it then you have a decision to make. Most companies I have worked with require that any code submitted be done so with a licence that would prevent my making a claim against them for any contents of code submitted to them in the application process. The reason is that you could submit some very easily duplicated code, then make a claim against them. So it is in their interests to demand the rights to use any code you submit to them.
For this reason I never include my "best" stuff. If there is a need I would remove the code that does work I wish to protect and insert a comment that the code is proprietary and you are unable to grant a blanket licence. If you feel the need to protect your code then you may be best served by contacting a lawyer and getting them involved in reviewing what you plan to submit to the client.
When making a decision on this I would ask myself what is it I hope to achieve. If the code is property of a third party company but you are submitting it as an example of the type of work that you do then including the third party copyright is appropriate so that you can indicate that the code is not owned by you and that you do not have permission to grant licence to use it. Generally I would follow the guidelines of the third party owner of the code, in the sharing of the code and the copyright status.
If the copyright to the code is owned by you and you have the right to grant licence to use it then you have a decision to make. Most companies I have worked with require that any code submitted be done so with a licence that would prevent my making a claim against them for any contents of code submitted to them in the application process. The reason is that you could submit some very easily duplicated code, then make a claim against them. So it is in their interests to demand the rights to use any code you submit to them.
For this reason I never include my "best" stuff. If there is a need I would remove the code that does work I wish to protect and insert a comment that the code is proprietary and you are unable to grant a blanket licence. If you feel the need to protect your code then you may be best served by contacting a lawyer and getting them involved in reviewing what you plan to submit to the client.
answered Apr 8 '13 at 16:26


IDrinkandIKnowThings
43.9k1398188
43.9k1398188
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
add a comment |Â
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
ANd if you are using code that belongs to a third party like your curent or previous employer, then make sure you have the rights to use it for a code sample.
– HLGEM
Apr 8 '13 at 17:16
add a comment |Â
up vote
1
down vote
Legally, at least in the US, you own the copyright to anything you create the moment it is created (provided you aren't creating the work under a work-for-hire arrangement). So there is no legal need for it in that sense.
However, for a sense of pride, I say go for it. It certainly wouldn't hurt anything (and if anything, maybe would help as it shows you take some ownership in your work).
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
 |Â
show 4 more comments
up vote
1
down vote
Legally, at least in the US, you own the copyright to anything you create the moment it is created (provided you aren't creating the work under a work-for-hire arrangement). So there is no legal need for it in that sense.
However, for a sense of pride, I say go for it. It certainly wouldn't hurt anything (and if anything, maybe would help as it shows you take some ownership in your work).
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
 |Â
show 4 more comments
up vote
1
down vote
up vote
1
down vote
Legally, at least in the US, you own the copyright to anything you create the moment it is created (provided you aren't creating the work under a work-for-hire arrangement). So there is no legal need for it in that sense.
However, for a sense of pride, I say go for it. It certainly wouldn't hurt anything (and if anything, maybe would help as it shows you take some ownership in your work).
Legally, at least in the US, you own the copyright to anything you create the moment it is created (provided you aren't creating the work under a work-for-hire arrangement). So there is no legal need for it in that sense.
However, for a sense of pride, I say go for it. It certainly wouldn't hurt anything (and if anything, maybe would help as it shows you take some ownership in your work).
edited Apr 9 '13 at 14:41
answered Apr 8 '13 at 3:37
DA.
2,0511116
2,0511116
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
 |Â
show 4 more comments
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
@chad copyright is a legal construct. If we can't answer a legal question with legal information, then legal questions shouldn't be asked.
– DA.
Apr 8 '13 at 17:31
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
Actually...you DON"t own the copyright to everything you create. Especially if you create it for work or for work-related things. Heck, even using a company computer to jump on google and get some advice to fix a problem you're encountering makes the code the company's (or at least it would if the company had a half-decent legal team).
– acolyte
Apr 8 '13 at 18:13
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
@acolyte yes, very good point. Work for Hire is another legal construct. Not sure if I'm allowed to talk about it. ;)
– DA.
Apr 8 '13 at 18:14
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
also, OP is asking not for the legal ramifications of adding a copyright notice, but more about the cultural/workplace repercussions of such an act (if there are any to begin with).
– acolyte
Apr 8 '13 at 18:20
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
@chad good point. I added a reference link.
– DA.
Apr 9 '13 at 14:41
 |Â
show 4 more comments
up vote
0
down vote
Is this code that you write for the interview (like a coding test?), or pre-existing code that they want to see?
If it's pre-existing code, (for instance, something you did on your own time), then yes, absolutely keep the notices on there.
If it's written for the interview, then no, don't. If you are writing to answer a coding test, then putting a copyright notice on the answer indicates that you are more concerned with outside affairs than the problems they are looking to hire you to solve.
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
add a comment |Â
up vote
0
down vote
Is this code that you write for the interview (like a coding test?), or pre-existing code that they want to see?
If it's pre-existing code, (for instance, something you did on your own time), then yes, absolutely keep the notices on there.
If it's written for the interview, then no, don't. If you are writing to answer a coding test, then putting a copyright notice on the answer indicates that you are more concerned with outside affairs than the problems they are looking to hire you to solve.
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Is this code that you write for the interview (like a coding test?), or pre-existing code that they want to see?
If it's pre-existing code, (for instance, something you did on your own time), then yes, absolutely keep the notices on there.
If it's written for the interview, then no, don't. If you are writing to answer a coding test, then putting a copyright notice on the answer indicates that you are more concerned with outside affairs than the problems they are looking to hire you to solve.
Is this code that you write for the interview (like a coding test?), or pre-existing code that they want to see?
If it's pre-existing code, (for instance, something you did on your own time), then yes, absolutely keep the notices on there.
If it's written for the interview, then no, don't. If you are writing to answer a coding test, then putting a copyright notice on the answer indicates that you are more concerned with outside affairs than the problems they are looking to hire you to solve.
answered Apr 8 '13 at 13:42
Michael Kohne
3,28111327
3,28111327
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
add a comment |Â
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
Yes, this. In addition, if you blatantly assert your ownership over a few hours' work in pursuit of a job, it would be natural for them to wonder if you're going to be like that if they hire you. ("Well, in order to solve your problem I had to write this script, but that's mine"... um, no.) Just don't go there; it can't help and it might hurt.
– Monica Cellio♦
Apr 8 '13 at 14:29
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f10935%2fshould-i-include-a-copyright-notice-on-job-application-submissions%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
If the code is yours, no reason not to. One other thing you can do is make a few subtle changes to the code that make it not function correctly and put a prominent note to that effect at the top. (Point here being that samples are to show your programming style.) Any shop smart enough to debug it probably doesn't need to steal it.
– Blrfl
Apr 8 '13 at 2:48
2
Do you want the job, or to make a point about IP law?
– Michael Kohne
Apr 8 '13 at 13:39
I figured worst case scenario, I can just say that my editor automatically inserts that stuff. For this particular assignment, I read the question as requiring 'real' code, so at least SOME copyright notice should go on it, along with things like unit tests.
– Sesquipedalian
Apr 8 '13 at 15:00
What kind of copyright notice are we talking about? A full-blown proprietary license, or a GPL/BSD style thing?
– acolyte
Apr 8 '13 at 16:03