|
Ideas are not subject to copyright so unless you've signed something that explicitly excludes you from using them, I see no problem with re-creating something similar at home, as long as you don't do it with the work code visible to you (to remove any possibility of copying). I've done something similar at work to re-use ideas I had working for one client in internal work and the consensus was that that is fine as long as you don't use any of the code you wrote before.
|
|
|
|
|
The ideas are yours. If you need those libraries recreate them.
|
|
|
|
|
Yep, you'd be a thief.
The only exception would be if they gave you permission.
|
|
|
|
|
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.
|
|
|
|
|
Sander Rossel wrote: Would they own the ideas of the libraries as well?
Yes - depending on whether the libraries themselves were unique or just an implementation of existing ideas.
e.g. if you wrote a maths library to perform various mathematical functions, then you couldn't take the source code and use it yourself, but you could write another maths library based on your knowledge, because maths libraries pre-existed your development of one.
But if you wrote something unique then reproducing even the idea could be an issue.
|
|
|
|
|
"Ideas" are NOT patentable ... only HOW they are implemented.
You cannot patent a "light bulb" (though a "patent troll" might try) ... tungsten wire vs halogen vs sodium vs mercury, etc ... that's something different. There is always room for a better mouse trap.
Renaming class names, variables, etc. won't help you ... courts will look at "code patterns" at the "byte code" or machine level to make a determination if a copyright was violated. The same "constants" in a program can make this particularly easy. Of course, "experts" will always need to be brought in.
|
|
|
|
|
This also depends to some extent on the nature of your contract. I've been a developer for more years than I care to remember, but I have always been very careful to ensure that copyright in the code remained with me (except for very specific contracts).
In the UK at least, code is considered a creative work for copyright purposes, so unless your contract of employment explicitly states that anything you write on company time, using company equipment, becomes the property of (and the copyright therein also becomes the property of) the company, then you retain all the intellectual property rights.
These days, of course, most employers are aware of this and structure their contracts accordingly, but this certainly wasn't the case generally until quite recently.
Now I work for my own company, this isn't much of a problem 8)
|
|
|
|
|
This is in my current contract. Anything I create using company resources, on company time, is sole property of the client I'm on contract with.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
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 |
|
|
|
|
|
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 
|
|
|
|
|
If I recall correctly, there was some sort of time limit. It may have been as short as when one's gov't employment is terminated (which is what would happen if you violated the rules).
For private sector, it's likely in the contract that one cannot make of use of their intellectual property for some set period. The rest buys Porsche's for Intellectual Property Lawyers.
| "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 |
|
|
|
|
|
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... 
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...
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 – ∞)
|
|
|
|
|
Yep. Or I wouldn't be working overtime 
|
|
|
|
|
Lucky devil!
I haven't had paid overtime for decades! 
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 – ∞)
|
|
|
|
|
To me it's simple, I sign a contract for 40 hours and a salary both my employer and I see fit. That's a salary for 40 hours, not 45 or 50. If I do work 45 or 50 hours I expect to be compensated accordingly.
That said, I do all my work related study in my own time. When my company decided to use Entity Framework I spent some hours at home figuring out how that stuff works.
I'm also not to uptight about working an exact 8 hours a day (like today I wanted to finish something and stayed 15 minutes longer) or getting every extra minute compensated.
And it depends on the employer. If they're getting uptight about something then so will I
|
|
|
|
|
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.
|
|
|
|
|
Agreed on that. I was replying to the following:
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
I think it's totally an employers business what I do in my spare time as long as it concerns them. For example if I drink too much, party too hard or practice extreme sports, and as a result call in sick from work every monday or at least a month a year etc. In the Netherlands the employer pays for sick employees. And they cost A LOT!
Another example is studying (or absolutely no studying!) during my private time.
|
|
|
|
|
Sander Rossel wrote: What I do outside office hours is none of their business though!
That isn't true even in a general way. Certainly not in the US and probably most everywhere else as well.
Lets go through the reasonable cases.
- You commit a felony hate crime Saturday night and the press come knocking at your work to ask about you on Monday. You get fired right then.
- You have a written contract with an company, you are not even an employee, but the contract states that any work in the financial industry belongs to them (any work, any time) and further there is a morals clause that specifically allows them to terminate you if you commit any serious crime. And you fail to meet one or both.
And the unreasonable ones.
- Drugs. You do something Saturday nite and get tested Monday. And you are fired Tuesday for drug use.
- The boss doesn't like you much but keeps you around because he isn't much of a manager, but he did see you on a date with his daughter on Saturday night - so you get fired Saturday.
- You write a letter to the newspaper that gets published on sunday but expressing a political view opposite that of your boss, and you get fired Monday.
- You get a tattoo on Saturday because you have been cancer free for 10 years. You boss doesn't like tattoos, so...
|
|
|
|
|
Yeah, I already commented somewhere that anything you do in your private time, but influences your boss' time is your boss' business.
Most of what you say doesn't hold true in the Netherlands though. You need a VERY good reason to fire an employee, getting a tattoo or not getting along is no good reason...
If you really want to fire an employee (especially when he's been with the company for some time) you better start building a dossier and document every reason to fire that employee. All of them added up might be a good reason, although it's probably still going to cost you a lot of money to have him fired.
If you own a small company with little profit a bad employee can literally ruin you and there's little you can do...
My dad's employer has a few employees who have been sick for at least two years (you know, they do some lifting and strain their back or something) and they're still paying for those people (they can't be fired).
Things work a little different here than in America / (sometimes for the better and sometimes for the worse) 
|
|
|
|
|
Sander Rossel wrote: Most of what you say doesn't hold true in the Netherlands though
Fair enough.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
