I just want to vent out some frustration. I am UNIX Admin and I work as a Contractor for the U.S. Government. I am also prior Military. I have been working with this woman who constantly steals my code from my scripts and then claims it as her own. It has gotten to the point where I can see her copying it verbatim and then making one change. I work very hard and take my job seriously and to see this moron doing this insults me very much. I mentioned it to her superior who is my friend. He was like don't worry I know where the real credit should go. But, nothing comes out of it...I do not want to start any drama, but I am getting fed up. The main problem is the fact that I am a contractor and she is a Government Civilian. I guess I was wondering if anyone had any similar situations and how did you handle it?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Code Stealers 3
- Thread starter coffeysm
- Start date
SantaMufasa
Technical User
How RUDE of your colleague! I generally place disclaimers at the top of my code that say, among other things, that I (by name) authored the code; that the code is protected under common copyright laws of the United States; that others may use the code within these circumstances: <place circumstances here>, provided that this disclaimer remains, as written, with the code during any use/reference of the source code; and that non-compliance with these restrictions represents personal damages to the author.
Then, when she uses the code outside of the restrictions that you place on the code, you can say,
![[santa]](/data/assets/smilies/santa.gif "[santa] [santa]")
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
Then, when she uses the code outside of the restrictions that you place on the code, you can say,
Let us know your thoughts, Coffeysm, about this approach.Coffeysm said:
Mufasa(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
-
1
- #3
sleipnir214
Programmer
Under what circumstances did you write these scripts from which your coworker copies code? If, for example, these are scripts you wrote as a contractor to the U.S. government, then she's not stealing code from you, but rather reusing U.S.-owned code in another U.S.-owned script.
Want the best answers? Ask the best questions! TANSTAAFL!
Want the best answers? Ask the best questions! TANSTAAFL!
Programming code is one of the most recyclable things there is. I routinely steal code from people on this site, and while I do not run anywhere and brag about how I wrote this code, I do build it into my applications if I think it is worthwhile, or superior to what I have written.
I normally have to do fairly serious modification to this code to get it to work in my apps, that is what I think makes it alright for me to 'pass it off as my own'. Whiel I make no claim to the specific piece of code, I do claim (and I think rightly so) that I wrote the application.
</disclaimer>
I think in your case, that it is not acceptable, because in the case of a script, what your colleague is doing is the equivalent to a colleague of mine taking my application, changing the name of the database that the application works with, and saying 'Hey boss, check out this application I wrote'. Taking and modifying code snippets is one thing, but entire scripts (programs) is another entirely.
However, sleipnir has an EXCELLENT point about who really owns the code. I think you have a legitimate beef, not in that you have any actual ownership of your code, but because you do deserve some credit for it. This would probably be best discussed with your co-worker though, as she might not even know that what she is doing upsets you.
Good LUck,
ALex
Ignorance of certain subjects is a great part of wisdom
I normally have to do fairly serious modification to this code to get it to work in my apps, that is what I think makes it alright for me to 'pass it off as my own'. Whiel I make no claim to the specific piece of code, I do claim (and I think rightly so) that I wrote the application.
</disclaimer>
I think in your case, that it is not acceptable, because in the case of a script, what your colleague is doing is the equivalent to a colleague of mine taking my application, changing the name of the database that the application works with, and saying 'Hey boss, check out this application I wrote'. Taking and modifying code snippets is one thing, but entire scripts (programs) is another entirely.
However, sleipnir has an EXCELLENT point about who really owns the code. I think you have a legitimate beef, not in that you have any actual ownership of your code, but because you do deserve some credit for it. This would probably be best discussed with your co-worker though, as she might not even know that what she is doing upsets you.
Good LUck,
ALex
Ignorance of certain subjects is a great part of wisdom
- Thread starter
- #5
I agree with you sleipnir, I was actually going to post that in my response before you did. However, the problem I have is she is not reusing it, she is copying my work and taking credit for it. She goes and tells everyone that she wrote these scripts and did this or did that. The changes she does make if any are minor. She might change what a dialog box says. But, essentially she is making herself look better for all the work I do. I do not have a problem with her modifying it or using it to learn. But, she does not even give me credit or mention the fact that she "sourced" it from somewhere. I know i'm a contractor and I am there to provide a solution. But, if I spend two or three days perfecting something and someone just comes and takes it, I have a problem with that.
- Thread starter
- #6
SantaMufasa
Technical User
<tongue planted firmly in cheek>
Under the circumstances you mention, Coffeysm, I see no ethical problem with doing whatever possible to sabotage her job.![[rofl]](/data/assets/smilies/rofl.gif "[rofl] [rofl]")
</tongue planted firmly in cheek>
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
Under the circumstances you mention, Coffeysm, I see no ethical problem with doing whatever possible to sabotage her job.
</tongue planted firmly in cheek>
Mufasa(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
sleipnir214
Programmer
Have you thought about using a CVS system to record who changes what?
Want the best answers? Ask the best questions! TANSTAAFL!
Want the best answers? Ask the best questions! TANSTAAFL!
- Thread starter
- #9
Santa, LOL....I am not the mean. Besides, she messes enough stuff up on her own, I won't need to do anything. However, since she is a Gov't employee it is nearly impossible for them to get fired. I have a better chance of losing my job then she does.
Well, she doesn't modify the original code. She copies it to her home directory or literally re-writes it on another system from the screen. LOL, I have done my homework...I browse her home directory and see what she does. I also have VNC installed, to troubleshoot my user's remotely. I have checked on her session seen her with my files open copying them, LOL. Yea, I know probably a little wrong what I did. But, I wanted to be sure I was correct. I just don't know if I should let it go and forget about it.
Well, she doesn't modify the original code. She copies it to her home directory or literally re-writes it on another system from the screen. LOL, I have done my homework...I browse her home directory and see what she does. I also have VNC installed, to troubleshoot my user's remotely. I have checked on her session seen her with my files open copying them, LOL. Yea, I know probably a little wrong what I did. But, I wanted to be sure I was correct. I just don't know if I should let it go and forget about it.
what if there was an error in your code. would she take credit for that as well, lol. i am not suggesting that you write code with errors for her to copy, but if you made a mistake, it would be fun to see her blame you for it, after she claimed she wrote it.
i do not think there is anything you can do about it, unless you have an agreement in your contract stating restrictions on the code you write.
i do not think there is anything you can do about it, unless you have an agreement in your contract stating restrictions on the code you write.
OK..
So, you work for the US government as a contractor ?
And you are contracted to build x,y and z scripts ?
Your employer obviously knows what these scripts are and do, as they *should* have defined the requirement ?
That makes sense, but what is puzzling me is why there is a need for the same script - to be written by you, and to be written by your colleague ? It sounds more like she is 'deploying' your scripts where they are needed (with a little customisation) than 'stealing' your code if she is taking the same script/program and using it pretty much as-is. Or do she not work in the same team as you, and have the same instructions from her boss as you do from yours .. ?
Also, if she is re-using your code to create other, larger or somewhat different programs then that is an industry best-practice.
So in either case it seems perfectly fine to actually use your scripts.
It is also relatively reasonable for her to pass the action/work of deploying or compositing the script off as her own. After all just writing code is only a small part of the delivery process.
HOWEVER... telling people that she actually wrote the entire code inside is not appropriate. She can say that as a general statement if it is only used as a small part of a larger system and is referring to that larger system as a whole, but if it is mainly your code, then she can only rightfully say she has 'implemented' it.
As for any legal nonsense, don't be so precious... you are a contractor, your time and skills are purchased (probably at a premium) to create IP for the organisation, which is likely to remain their IP, and almost certainly with no rights to yourself. (unless you have worked out IPR in your favour during contract negotiations, which is unlikely) Leaving any reference to yourself or company would be a courtesy or 'contact'/'history' reference - not a proof of ownership, or anything else.
I don't think you mentioned who this colleague is telling that your code is hers, but it sounds like your manager already knows the source of this code (and so they should). So, is it just your other peers ? How have they not seen the script / program when you wrote it, but have when this other colleague 'wrote it' ?
One way to circumvent her (and possibly embarrass her if she's really thick) is to make announcements to the groups that she is telling fibs to... e.g. A Status report that describes the completion of script "abc" that does "x,y and z" - even post the contents for their reference.
If she really is telling full blown lies, she won't get very far when everyone already has the facts to hand.
I would also be tempted to not include her on the distribution if it was possible, just to see what the reaction would be. But that's a little mean, and likely to cause issues that really aren't needed, so I wouldn't recommend it.
Good luck, but please remember that you are a contractor, and likely have no actual legal rights to the code, and that although it may 'appear' she is falsely claiming credit for your work, it may be a misunderstanding. Besides as a contractor (as you pointed out) you can be booted far easier than she can.. fair or not.
A smile is worth a thousand kind words. So smile, it's easy!
Just to add there, surely if you work in the same team (correct me if im wrong) then you are working for the same goal, I frequently copy "other peoples" code within my company but to acheive an end goal, I would expect the same. If there is an easier way of doing it etc, sorry if I have missed the point...
===
Fatman Superstar (Andrew James)
CCNA
===
Fatman Superstar (Andrew James)
CCNA
RandeKnight
Programmer
Since she's copying the code by hand, I'd do one of those old tricks. eg.
@Putting a semicolon (or equivalent) way at the right hand side off the end of the margin.
@Linking the script to a large library of routines.
@Use some foreign characters that look the same as the base ascii, but aren't, and then make them dependant on a character number conversion.
@Write a very long script where 90% of it is never actually run. Doesn't stop her using it, but lets her have lots of fun retyping.
@Putting a semicolon (or equivalent) way at the right hand side off the end of the margin.
@Linking the script to a large library of routines.
@Use some foreign characters that look the same as the base ascii, but aren't, and then make them dependant on a character number conversion.
@Write a very long script where 90% of it is never actually run. Doesn't stop her using it, but lets her have lots of fun retyping.
RandeKnight..
Where does it say she's copying by hand ?
I would expect she is just copying as most do.. e.g. ctrl-a, ctrl-c and ctrl-v.... or [tt]cp ascript.sh bscript.sh[/tt] or the many many other ways you can duplicate electronic information without 'hand typing' it....
Oh, and the 'very long script' or 'large library of routines' approach would only make the original author of the code look like an incompetent fool.
Besides, the re-usability and ease of maintenance of code is a measure of it's quality.
A smile is worth a thousand kind words. So smile, it's easy!
damber,
I am not trying to speak for coffeysm, but I have worked as a contractor for a government branch before. Unlike with the private sector, thre often times seems to be a very distinct "us" and "them" mentality with the Government employees. To parlay into an annaology, think Civilian Contractors on a military base. All are equal employees, some are just "more equal" then others (i.e. we "really" belong here, you are just helping out). In my situation, it was not uncommon to have multiple contracting agencies working with the government - this provided countless hours of "us" against "them" and "them" and "them" - and oh yeah - forgot about "them". Since these are contracts, it soon becomes a competitive issue as the top government bean counters asking "why are we paying these contracts when we are developing these issues ourselves?" Moreover, most of these making budgets and decisions are not even in the same branch or area as those that are on the contracts.
So it does come down to more then a colaborative effort between mutual agents focused on a common goal - it is corporate politics as usual - and often times, a contractors position hangs in the balance of the shift of power. So what should be "for the common good" is almost always twisted into 'MY team accomplished this goal, lets take "THEIR" team off of it and put them on something else. Oh their contract is only for this project? ok, lets end their contract, "WE" are doing all the work anyway".
And one last caveat, many times within government offices, it is about seniority, so a government supervisor may have little to no experience in a particular field, but due to "time served" they are given a position of authority. I had that case with a Web Dev. She had transfered out of 18 years within the secretarial pool, and as her time was approaching a close, needed to "expand her horizons" to prepare for time in the private sector. Since the internet was new at the time, it was seen as little more then typing skills. This further exacerbates the problem of an unqualified government employee taking credit for the contractors work.
I am not trying to speak for coffeysm, but I have worked as a contractor for a government branch before. Unlike with the private sector, thre often times seems to be a very distinct "us" and "them" mentality with the Government employees. To parlay into an annaology, think Civilian Contractors on a military base. All are equal employees, some are just "more equal" then others (i.e. we "really" belong here, you are just helping out). In my situation, it was not uncommon to have multiple contracting agencies working with the government - this provided countless hours of "us" against "them" and "them" and "them" - and oh yeah - forgot about "them". Since these are contracts, it soon becomes a competitive issue as the top government bean counters asking "why are we paying these contracts when we are developing these issues ourselves?" Moreover, most of these making budgets and decisions are not even in the same branch or area as those that are on the contracts.
So it does come down to more then a colaborative effort between mutual agents focused on a common goal - it is corporate politics as usual - and often times, a contractors position hangs in the balance of the shift of power. So what should be "for the common good" is almost always twisted into 'MY team accomplished this goal, lets take "THEIR" team off of it and put them on something else. Oh their contract is only for this project? ok, lets end their contract, "WE" are doing all the work anyway".
And one last caveat, many times within government offices, it is about seniority, so a government supervisor may have little to no experience in a particular field, but due to "time served" they are given a position of authority. I had that case with a Web Dev. She had transfered out of 18 years within the secretarial pool, and as her time was approaching a close, needed to "expand her horizons" to prepare for time in the private sector. Since the internet was new at the time, it was seen as little more then typing skills. This further exacerbates the problem of an unqualified government employee taking credit for the contractors work.
- Thread starter
- #16
attrofy you are 100% correct that is one of the reasons why I am bothered by it. I do work on a Military installation and was in the Military for five years. I always have to wonder "gee when is my time up". Now, her superior is my friend and knows about UNIX. The problem though is that does not mean anything, because if it came down to it they would get rid of a contractor before a GS.
Damber, she does copy it by hand, LOL. She has it open on one screen and will type it in another screen on a different system. See, we have different networks at classification levels. I have offered to help her before and she is like I am not doing anything blah blah.
Fatman, I agree with you we are on the same team. However, as atty mentioned. That does not matter when it comes down to final cost. If they decide to re-work their budget and be like "Wow, we pay Steve's company this much money..." Yet, we can get it down internally why do we need them here?
I have had several run-ins with her not just involving scripts. She has changed things on servers and denied it...she messed my Jumpstart stuff, then sent an e-mail to EVERYONE saying I had it setup wrong. I then had to get involved in an e-mail war, saying this what you did and you changed lines blah, blah, and blah.
Damber, she does copy it by hand, LOL. She has it open on one screen and will type it in another screen on a different system. See, we have different networks at classification levels. I have offered to help her before and she is like I am not doing anything blah blah.
Fatman, I agree with you we are on the same team. However, as atty mentioned. That does not matter when it comes down to final cost. If they decide to re-work their budget and be like "Wow, we pay Steve's company this much money..." Yet, we can get it down internally why do we need them here?
I have had several run-ins with her not just involving scripts. She has changed things on servers and denied it...she messed my Jumpstart stuff, then sent an e-mail to EVERYONE saying I had it setup wrong. I then had to get involved in an e-mail war, saying this what you did and you changed lines blah, blah, and blah.
Of course you could just not do anything about it (though I do like the introduction of code bloat someone mentioned above). Just grin and consider how much pain she will be in after you leave and she suddenly has to actually try to write her own code
attrofy / coffeysm,
Whilst I can appreciate the challenges faced by a contractor in a government establishment (and others), I have to say that.. well (with the best will in the world).. you are just that, contractors... you are there for the contract that was signed and to deliver what was agreed upon. You chose to be a contractor.
I've had a lot of contractors work for me, both individuals and groups from 'consultancies', and what is important is that they achieve what they are contracted to achieve... and ideally do it with flare.. because the most important thing is that any one that values their own career or even has any pride whatsoever in themselves, will want to keep those that help them achieve their goals close by... if a contractor does a good job, with no hassle, then great - it makes the managers job that bit easier. If the full timers are completely hopeless and cannot think for themselves, then how long do you think it will be before said contractor is hired back.... ? It is in the managers best interest to get the best they can for their money.
Of course, if the internal staff can do it (or learn from the contractors), then there isn't a need for the contractors, and the organisation should not renew their contracts... there is a reason why contractors are paid a premium.. because it is risky work - should you be fantastic at your job, then *usually* you will have plenty of work to do - people will want you around because you do a good job and help to make them succesful. But you cannot rely on having a permanent stable role with any company.. you have your contract, and the impression you made on the hirers/firers whilst you were there. If it were 'permanent' then wouldn't you be a normal FTE ?
So, politely issuing status updates which include the work you've done is a good way to
a) keep everyone up to speed on what is happening
b) make sure you get all the credit for your work and
c) remind people that you are still there and are productive
Politics are horrible... but lead by example, don't play the game. Just do what is right for the organisation, and ensure (politely, with subtlety) that people appreciate where credit is deserved... and not just in your favour either. Help the team to be a success, ensure they share your glory (even if the work is primarily yours) but keep your manager up to date with what you are working on, and what has been done that week. If done properly, the team will want you to stay because you make them look good and the manager will want you to stay because you make his/her job easier.
The bean counters will not be happy with anything other than numbers in a spreadsheet/accounting system... without project leadership it can be difficult to demonstrate to those people what your real value is.... but, if you have a somewhat supportive team and manager, you will be much better off... A useful method if you have the know-how is to report on value of your work when submitting your status report. This should show the cost savings/avoidance/opportunities or profit increases that are a direct result of your work. That's the message bean counters listen for.
So, organisations usually hire external people to help do what they cannot do themselves and to do 'better' than they could do themselves.. sometimes they hire them just as another body... but do you know what ? You are a contractor, you're paid a premium over internal staff and you offer not only your knowledge, but also your flexibility to the organisation... which means, you live contract by contract - the organisation has no other commitment to you... if that is what your real concern is, then.. is contracting the thing for you ?
As I've already stated, there is a simple and effective way around this.. if this is just an effect, rather than a cause of your concern, then you have some things to think about.
Either way, I hope you get the recognition you deserve, but whatever you do, don't let it eat you up as it will only make you come across badly to the people you work with, and make your working life depressing.
oh... and the copying by hand thing... geez... ! she is desperate !
A smile is worth a thousand kind words. So smile, it's easy!
Whilst I can appreciate the challenges faced by a contractor in a government establishment (and others), I have to say that.. well (with the best will in the world).. you are just that, contractors... you are there for the contract that was signed and to deliver what was agreed upon. You chose to be a contractor.
I've had a lot of contractors work for me, both individuals and groups from 'consultancies', and what is important is that they achieve what they are contracted to achieve... and ideally do it with flare.. because the most important thing is that any one that values their own career or even has any pride whatsoever in themselves, will want to keep those that help them achieve their goals close by... if a contractor does a good job, with no hassle, then great - it makes the managers job that bit easier. If the full timers are completely hopeless and cannot think for themselves, then how long do you think it will be before said contractor is hired back.... ? It is in the managers best interest to get the best they can for their money.
Of course, if the internal staff can do it (or learn from the contractors), then there isn't a need for the contractors, and the organisation should not renew their contracts... there is a reason why contractors are paid a premium.. because it is risky work - should you be fantastic at your job, then *usually* you will have plenty of work to do - people will want you around because you do a good job and help to make them succesful. But you cannot rely on having a permanent stable role with any company.. you have your contract, and the impression you made on the hirers/firers whilst you were there. If it were 'permanent' then wouldn't you be a normal FTE ?
So, politely issuing status updates which include the work you've done is a good way to
a) keep everyone up to speed on what is happening
b) make sure you get all the credit for your work and
c) remind people that you are still there and are productive
Politics are horrible... but lead by example, don't play the game. Just do what is right for the organisation, and ensure (politely, with subtlety) that people appreciate where credit is deserved... and not just in your favour either. Help the team to be a success, ensure they share your glory (even if the work is primarily yours) but keep your manager up to date with what you are working on, and what has been done that week. If done properly, the team will want you to stay because you make them look good and the manager will want you to stay because you make his/her job easier.
The bean counters will not be happy with anything other than numbers in a spreadsheet/accounting system... without project leadership it can be difficult to demonstrate to those people what your real value is.... but, if you have a somewhat supportive team and manager, you will be much better off... A useful method if you have the know-how is to report on value of your work when submitting your status report. This should show the cost savings/avoidance/opportunities or profit increases that are a direct result of your work. That's the message bean counters listen for.
So, organisations usually hire external people to help do what they cannot do themselves and to do 'better' than they could do themselves.. sometimes they hire them just as another body... but do you know what ? You are a contractor, you're paid a premium over internal staff and you offer not only your knowledge, but also your flexibility to the organisation... which means, you live contract by contract - the organisation has no other commitment to you... if that is what your real concern is, then.. is contracting the thing for you ?
As I've already stated, there is a simple and effective way around this.. if this is just an effect, rather than a cause of your concern, then you have some things to think about.
Either way, I hope you get the recognition you deserve, but whatever you do, don't let it eat you up as it will only make you come across badly to the people you work with, and make your working life depressing.
oh... and the copying by hand thing... geez... ! she is desperate !
A smile is worth a thousand kind words. So smile, it's easy!
Well put damber!
And I simply cannot fathom copying by hand. To spend that much time, you might as well actually figure out how it works and type it up yourself. I think to copy by hand, she is doing herself (and the taxpayers) quite a disservice. You should be laughing and sharing things like this with us, rather than worrying about her taking your credit If she in fact is, I am sure she will be exposed soon enough.
If you want to be truly vicious, try taking a vacation around a time that something you haven't developed a script for yet needs to be completed![[evil]](/data/assets/smilies/evil.gif "[evil] [evil]")
Ignorance of certain subjects is a great part of wisdom
And I simply cannot fathom copying by hand. To spend that much time, you might as well actually figure out how it works and type it up yourself. I think to copy by hand, she is doing herself (and the taxpayers) quite a disservice. You should be laughing and sharing things like this with us, rather than worrying about her taking your credit
If she in fact is, I am sure she will be exposed soon enough. If you want to be truly vicious, try taking a vacation around a time that something you haven't developed a script for yet needs to be completed
Ignorance of certain subjects is a great part of wisdom
I don't have a problem with people copying my code -- after all, I got paid to write it, and it's a team effort.
But someone taking credit for it is where I have a problem.
I think you choices are: Stay where you are, and put up with her behavior; start logging what you do in your status report so that you get (initial) credit; or start looking to transfer to another workcenter.
Her lack of honesty will eventually poison the air there, and cause morale problems. All you can do is point this out to her supervisor (2-3 times, max), and after that it's their problem.
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
But someone taking credit for it is where I have a problem.
I think you choices are: Stay where you are, and put up with her behavior; start logging what you do in your status report so that you get (initial) credit; or start looking to transfer to another workcenter.
Her lack of honesty will eventually poison the air there, and cause morale problems. All you can do is point this out to her supervisor (2-3 times, max), and after that it's their problem.
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first
- Status
Similar threads
