"Stealing" from the company?
-
If you create the libraries on the company time, chances are that they own them. I have this in place in my company - all work created using company resources is covered as belonging to the company. If you worked for me and took your own laptop and did your work on there in your breaks, then I wouldn't have a problem with you using the code for yourself, but if you did it when you were supposed to be working on my projects and/or used my equipment, I would be very annoyed at you taking the code for yourself. The practical example of this was the creators of Barbie suing (and winning) the creators of Bratz because they created the Bratz dolls when they were working for Barbie.
Pete O'Hanlon wrote:
If you create the libraries on the company time, chances are that they own them.
Probably. Would they own the ideas of the libraries as well? I could easily re-create the libraries at home.
-
Pualee wrote:
You have already been compensated for their creation
Yeah, very true. How about the ideas? Would it be a problem if I re-created anything. After all, I've been compensated for that too ;)
I think it is a gray area. Are you working for a military/defense contractor? Did/will the company create a patent around it? Are you planning to open source it? Are you going to resell it? Are they going to resell it? There can be big consequences for the action. If it is a trivial thing and no risk of the above, you could be ok. Talk with your manager.
-
Suppose I created some libraries at work that we use thoroughly because they are awesome. And suppose I wanted to use them for private projects and maybe even professionally (just not at work where I created them). Would it be allright for me to just copy/paste those libraries to my own computer? Why would I think this might not be a problem? First of all I used the internet to create those libraries. Very few code is literally copy/pasted, but the code isn't completely mine either (and so not completely my companies', or maybe it is...). Secondly, I am the only one who wrote those libraries and the only one who knows how they work internally. I could re-create them at home in a couple of days. I even took some code from home and used it at work, although there is no way of proving this. For now I am fine with not having these libraries at home. If I really wanted them I could probably ask my boss and he'd be okay with it. I think legally if I took these libraries and my employer found out he could sue me and I'd be in big trouble (although it might be hard to prove I actually took those libraries and not re-created them, especially when I change some variable names etc.). I was just wondering how people here think about this, personally (as opposed to legally). Does anyone have experience with such matters?
Most of the companies I have worked for cover that in the contract of employment: they own the rights to everything you produce while working for them - and one or two contracts have gone further and claimed ownership of everything produced while employed by them: which covers time outside working hours as well, but that is probably difficult to enforce in a court. Lawyers would enjoy the profits of trying though. If you are at work when you do any work on them, they own it. Taking it home without permission would be theft and could be enforced pretty easily: if it came to court, you'd almost certainly lose. On good terms with your boss? Explain and ask him for permission!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt -
Suppose I created some libraries at work that we use thoroughly because they are awesome. And suppose I wanted to use them for private projects and maybe even professionally (just not at work where I created them). Would it be allright for me to just copy/paste those libraries to my own computer? Why would I think this might not be a problem? First of all I used the internet to create those libraries. Very few code is literally copy/pasted, but the code isn't completely mine either (and so not completely my companies', or maybe it is...). Secondly, I am the only one who wrote those libraries and the only one who knows how they work internally. I could re-create them at home in a couple of days. I even took some code from home and used it at work, although there is no way of proving this. For now I am fine with not having these libraries at home. If I really wanted them I could probably ask my boss and he'd be okay with it. I think legally if I took these libraries and my employer found out he could sue me and I'd be in big trouble (although it might be hard to prove I actually took those libraries and not re-created them, especially when I change some variable names etc.). I was just wondering how people here think about this, personally (as opposed to legally). Does anyone have experience with such matters?
As others are saying if written on company time then they own it, but I say how is it licensed? If a piece of software is available to others under a certain license I would say it applies to you as well.
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever! Rich Tennant 5th Wave
-
Suppose I created some libraries at work that we use thoroughly because they are awesome. And suppose I wanted to use them for private projects and maybe even professionally (just not at work where I created them). Would it be allright for me to just copy/paste those libraries to my own computer? Why would I think this might not be a problem? First of all I used the internet to create those libraries. Very few code is literally copy/pasted, but the code isn't completely mine either (and so not completely my companies', or maybe it is...). Secondly, I am the only one who wrote those libraries and the only one who knows how they work internally. I could re-create them at home in a couple of days. I even took some code from home and used it at work, although there is no way of proving this. For now I am fine with not having these libraries at home. If I really wanted them I could probably ask my boss and he'd be okay with it. I think legally if I took these libraries and my employer found out he could sue me and I'd be in big trouble (although it might be hard to prove I actually took those libraries and not re-created them, especially when I change some variable names etc.). I was just wondering how people here think about this, personally (as opposed to legally). Does anyone have experience with such matters?
Legally, you probably can't do that (depends, check contract, I've had one that said I could take 30% of the code). In practice, you can. No one's going to know, and no one's getting hurt so no one has any reason to try to find out if you did anything. Or at least that was until you posted about it under your real name. Now there would be reason to suspect you.
-
Suppose I created some libraries at work that we use thoroughly because they are awesome. And suppose I wanted to use them for private projects and maybe even professionally (just not at work where I created them). Would it be allright for me to just copy/paste those libraries to my own computer? Why would I think this might not be a problem? First of all I used the internet to create those libraries. Very few code is literally copy/pasted, but the code isn't completely mine either (and so not completely my companies', or maybe it is...). Secondly, I am the only one who wrote those libraries and the only one who knows how they work internally. I could re-create them at home in a couple of days. I even took some code from home and used it at work, although there is no way of proving this. For now I am fine with not having these libraries at home. If I really wanted them I could probably ask my boss and he'd be okay with it. I think legally if I took these libraries and my employer found out he could sue me and I'd be in big trouble (although it might be hard to prove I actually took those libraries and not re-created them, especially when I change some variable names etc.). I was just wondering how people here think about this, personally (as opposed to legally). Does anyone have experience with such matters?
I think as long as the methods are generic code that can be used anywhere, and they're not connected too, or utilizes company proprietary code (usually interface related), you should be okay. I've been given the go ahead to include such methods and techniques in any article I write for CP, as long as I follow the fore-mentioned criteria.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Most of the companies I have worked for cover that in the contract of employment: they own the rights to everything you produce while working for them - and one or two contracts have gone further and claimed ownership of everything produced while employed by them: which covers time outside working hours as well, but that is probably difficult to enforce in a court. Lawyers would enjoy the profits of trying though. If you are at work when you do any work on them, they own it. Taking it home without permission would be theft and could be enforced pretty easily: if it came to court, you'd almost certainly lose. On good terms with your boss? Explain and ask him for permission!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Related to R&D: Anything related to your position while a Federal (US) government employee is owned by the US Government; similar rules for many large companies. It makes sense: the US Gov't point of view is that you are using knowledge gained while employed by them, so the creation of the knowledge is their property. This all comes about, actually, as a consequence of the rules/laws that a Federal Employee is not permitted (aside from wages, etc.) from profiting from his association with the government. This extends to gifts from vendors (beyond, perhaps, a cup of coffee or very cheap pen). For a period of time, due to some scandals in congress, rules (=laws) were enacted of a nature whereby a Federal Employee could not earn money form speaking, even if totally unrelated to their work. This law, naturally, excluded senators and congressmen. It has since been fixed - only applying to work-related material (it's owned by the people and you cannot charge them for what is already theirs).
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Legally, you probably can't do that (depends, check contract, I've had one that said I could take 30% of the code). In practice, you can. No one's going to know, and no one's getting hurt so no one has any reason to try to find out if you did anything. Or at least that was until you posted about it under your real name. Now there would be reason to suspect you.
harold aptroot wrote:
Or at least that was until you posted about it under your real name. Now there would be reason to suspect you.
Oops! :laugh: I'm not a thief. I suspect I could take it if I asked. If I can't I'd write something similar in my spare time. I was just wondering how others thought about the issue and it's pretty much what I thought ;)
-
I think as long as the methods are generic code that can be used anywhere, and they're not connected too, or utilizes company proprietary code (usually interface related), you should be okay. I've been given the go ahead to include such methods and techniques in any article I write for CP, as long as I follow the fore-mentioned criteria.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Nope, I'd have to change some namespaces, but other than that it's pretty generic code. As I said, some of it is taken from the internet. It's not like I want to take some Controls with our company logo on them :laugh: Actually I have thought about writing an article about one of those libraries before.
-
I think as long as the methods are generic code that can be used anywhere, and they're not connected too, or utilizes company proprietary code (usually interface related), you should be okay. I've been given the go ahead to include such methods and techniques in any article I write for CP, as long as I follow the fore-mentioned criteria.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Most of the companies I have worked for cover that in the contract of employment: they own the rights to everything you produce while working for them - and one or two contracts have gone further and claimed ownership of everything produced while employed by them: which covers time outside working hours as well, but that is probably difficult to enforce in a court. Lawyers would enjoy the profits of trying though. If you are at work when you do any work on them, they own it. Taking it home without permission would be theft and could be enforced pretty easily: if it came to court, you'd almost certainly lose. On good terms with your boss? Explain and ask him for permission!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
OriginalGriff wrote:
and one or two contracts have gone further and claimed ownership of everything produced while employed by them: which covers time outside working hours as well
That's ridiculous... And, as you say, almost impossible to check. Of course you shouldn't write articles while employed... :~
-
Suppose I created some libraries at work that we use thoroughly because they are awesome. And suppose I wanted to use them for private projects and maybe even professionally (just not at work where I created them). Would it be allright for me to just copy/paste those libraries to my own computer? Why would I think this might not be a problem? First of all I used the internet to create those libraries. Very few code is literally copy/pasted, but the code isn't completely mine either (and so not completely my companies', or maybe it is...). Secondly, I am the only one who wrote those libraries and the only one who knows how they work internally. I could re-create them at home in a couple of days. I even took some code from home and used it at work, although there is no way of proving this. For now I am fine with not having these libraries at home. If I really wanted them I could probably ask my boss and he'd be okay with it. I think legally if I took these libraries and my employer found out he could sue me and I'd be in big trouble (although it might be hard to prove I actually took those libraries and not re-created them, especially when I change some variable names etc.). I was just wondering how people here think about this, personally (as opposed to legally). Does anyone have experience with such matters?
If you write a general log in script for a website on company time and then send yourself a copy of that script to use on your own personal website I think ethically you're fine. However, if you make that script available to the competition or compete with your current employer then you've got a problem. I think the intent of these restrictions is "we don't want our developers writing code for the competition".
-
Related to R&D: Anything related to your position while a Federal (US) government employee is owned by the US Government; similar rules for many large companies. It makes sense: the US Gov't point of view is that you are using knowledge gained while employed by them, so the creation of the knowledge is their property. This all comes about, actually, as a consequence of the rules/laws that a Federal Employee is not permitted (aside from wages, etc.) from profiting from his association with the government. This extends to gifts from vendors (beyond, perhaps, a cup of coffee or very cheap pen). For a period of time, due to some scandals in congress, rules (=laws) were enacted of a nature whereby a Federal Employee could not earn money form speaking, even if totally unrelated to their work. This law, naturally, excluded senators and congressmen. It has since been fixed - only applying to work-related material (it's owned by the people and you cannot charge them for what is already theirs).
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
W∴ Balboos wrote:
so the creation of the knowledge is their property
So when going out of employment you should forget everything you learned while employed? That's a bit hard... Unless you're with the MIB ;)
-
OriginalGriff wrote:
and one or two contracts have gone further and claimed ownership of everything produced while employed by them: which covers time outside working hours as well
That's ridiculous... And, as you say, almost impossible to check. Of course you shouldn't write articles while employed... :~
Their attitude was that they don't pay developers by the hour; they pay by the month, so anything you did during that month was theirs! I did ask if I should take a plastic bag with me on bathroom visits, but just got a stern look... :laugh:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
If you write a general log in script for a website on company time and then send yourself a copy of that script to use on your own personal website I think ethically you're fine. However, if you make that script available to the competition or compete with your current employer then you've got a problem. I think the intent of these restrictions is "we don't want our developers writing code for the competition".
Yeah, I've got an anti-competition clause, or what's it called, in my contract. In my case I can't do anything for a direct competitor while or three years after employment (but who are our competitors?). That last part goes without saying ;)
-
Their attitude was that they don't pay developers by the hour; they pay by the month, so anything you did during that month was theirs! I did ask if I should take a plastic bag with me on bathroom visits, but just got a stern look... :laugh:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
OriginalGriff wrote:
Their attitude was that they don't pay developers by the hour; they pay by the month, so anything you did during that month was theirs!
They pay for x hours per month, so anything produced in those x hours can be theirs. What I do outside office hours is none of their business though!
OriginalGriff wrote:
I did ask if I should take a plastic bag with me on bathroom visits, but just got a stern look... :laugh:
:laugh: Doesn't sound like a company I would want to be working for... :~
-
OriginalGriff wrote:
Their attitude was that they don't pay developers by the hour; they pay by the month, so anything you did during that month was theirs!
They pay for x hours per month, so anything produced in those x hours can be theirs. What I do outside office hours is none of their business though!
OriginalGriff wrote:
I did ask if I should take a plastic bag with me on bathroom visits, but just got a stern look... :laugh:
:laugh: Doesn't sound like a company I would want to be working for... :~
Do you get overtime payments if you work more than that?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt -
Do you get overtime payments if you work more than that?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
Yep. Or I wouldn't be working overtime :)
Lucky devil! I haven't had paid overtime for decades! :sigh: One company gave me an unexpected pay rise - and a generous one- which purely-by-accident just happened to move me above the 'you don't get paid overtime' threshold... :(
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
OriginalGriff wrote:
Their attitude was that they don't pay developers by the hour; they pay by the month, so anything you did during that month was theirs!
They pay for x hours per month, so anything produced in those x hours can be theirs. What I do outside office hours is none of their business though!
OriginalGriff wrote:
I did ask if I should take a plastic bag with me on bathroom visits, but just got a stern look... :laugh:
:laugh: Doesn't sound like a company I would want to be working for... :~
Sander Rossel wrote:
What I do outside office hours is none of their business though!
It is if you're doing work that competes with your employers line of business. I have it written into my contract that I'm not allowed to do other work in the same line of business. Unnecessarily though as it's already in the law. They can't lay any claims to code you write that's not relevant to them though. What's relevant is obviously a grey area. :~
Wrong is evil and must be defeated. - Jeff Ello[^]
