|
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
|
|
|
|
|
Nope, 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 
Actually I have thought about writing an article about one of those libraries before.
|
|
|
|
|
Yes, but you are an Outlaw Programmer, that certainly mitigates your obligations a litlle bit. 
[Flags]
public enum Bool {
True, False, ForSure, Maybe, ProbablyNot, Depends, NotDecidedYet, Undefined
}
private interface IShy { }
|
|
|
|
|
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 
|
|
|
|
|
My understanding is that those types of clauses are pretty much unenforceable here in Australia under anti-competitive laws... Once you stop working for a company your obligation to them ceases. Unless they want to pay you until the expiry of the no work clause!!
|
|
|
|
|
_Damian S_ wrote: My understanding is that those types of clauses are pretty much unenforceable here in Australia
Same goes for the Netherlands, but an employer can try...
|
|
|
|
|
I've only been asked to sign one of those one time, and I refused. It essentially inhibits your ability to work in your chosen field. If it was at all enforceable, the big companies in Silicon Valley wouldn't be able to hire each others employees.
".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
|
|
|
|
|
You were paid, so it ain't yours.
You might be able to claim intellectual copyright, but that would cost you a Hell of a lot more time (and lawyers' fees) than just writing new libraries -- they can't stop you from using your brain to do something in a similar way when you need to do something similar.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: they can't stop you from using your brain to do something in a similar way when you need to do something similar.
Yes they can.
See Apple vs Samsung
If you develop something new for a company then that new idea is theirs not yours. If you reproduce the idea, even using different methods, it is the idea that still belongs to the company.
|
|
|
|
|
That's only true if the idea is patented.
|
|
|
|
|
BobJanova wrote: That's only true if the idea is patented.
That is simplistic.
If in fact you do start from scratch and write something similar then, at least in some cases, you are allowed to do that. It depends on implicit and explicit contracts where one is.
However that doesn't stop legal challenges. And in such cases one side will attempt to show that it is a copy (modified or not) and the other will attempt to show it isn't.
Neither is a sure thing.
Given that and presuming that that one really did re-write it then, legally, one can only hope that what one created would be deemed significantly different enough that it would be ruled unique. But at best that is risky.
|
|
|
|
|
Sander Rossel wrote: Suppose I created some libraries at work
Wherever I've worked, any work done for the company becomes the property of the company. Of course, open-source and other publicly available information referenced in these works is not part of the company's IP, even though their code may be included. The terms of use of the open-source licenses always hold.
Sander Rossel wrote: I could re-create them at home in a couple of days
Recreating work based on your learnings is permissible (that's what devs do throughout their career), as long as it doesn't infringe on patents, and even then, may be permissible by licensing use of the patent. Chances are, this will not apply to you.
Disclaimer: I am not a lawyer.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: Disclaimer: I am not a lawyer.
Good, because I was going to sue you if any of the above DID apply to me 
Luckily we don't have patents of any kind. That would suck if I wanted to re-use my idea's 
|
|
|
|
|
Technically, it's only theft if you get caught. Otherwise it's serendipitous coincident development.
Will Rogers never met me.
|
|
|
|
|
Good point!
|
|
|
|
|
Yeah, one Russian programmer who used to work for Goldman Sachs or some such moneyfleabag got several years in prison for doing exactly that.
Can't be arsed to look the thing up. Do the Google search yourself.
|
|
|
|
|
You could always explain to the employer/contract owner that you used various internet sources to develop this library and that corporate citizenship demands that you should share alike.
Get permission to publish it with a liberal OS license. Depending on where you obtained some of the code and the license that applied to that code, you might be legally obligated to share alike.
Barring that, you should be able to recreate it on your own time. Since this is the second time you would be doing it, it should turn out even better than the first implementation. Just make sure that it is a "clean room" implementation.
|
|
|
|
|
I didn't read through the entire thread yet, but this is a no brainer.
You said: "I could re-create them at home in a couple of days."
That is what you need to do. Besides if you hit some snag, just go revisit the spot in the code you are stuck on the next day at work.
The rule of thumb is if you got paid to write some code you do not own that code. Unless you have a written agreement/contract explicitly stating otherwise.
|
|
|
|
|
From reading the comments I'm not sure that I have anything new to add, but I will reiterate what others have said just to make sure the point is clear - it is definitely stealing. Even if you were copying/pasting from code you located on the internet it is still stealing because you found that code during time that you were being paid.
Like Pete and some others that have commented, I have my own company and anyone that works for me (regardless of whether it is full-time or on contract) is required to sign-off the entirety of the work that they create - after all, that's why they're being paid. Check your work agreement because it should clarify some of this for you. If you don't have an agreement then it will come down to whatever is considered "default" for the legalities where you live - in many cases that means that your employer owns your work.
Some others have suggested rewriting the libraries in your own time making sure to change class and variable names to identify it as "yours" and to document the personal time you took to create the libraries. That is definitely one option, but I would suggest that the best way of avoiding any legal mess is talking to your employer. The problem is that all of this quickly falls into very gray area - whether you're talking about creating Bratz while working for Barbie or something much less malicious it will often come down to perception. What are using these libraries for? Are you building a product that is similar to your employers? Is it a competing product? Is it a product that fits to your employer's industry horizontally or vertically? Are the libraries that you're reusing unique to these types of products? If the answer is yes to any of those then you're more likely to be heading down a dark path versus reusing a completely generic library for a completely unrelated product in a completely unrelated industry.
Bottom line - talk to your employer. If you haven't talked to them because you're afraid of the answer then I think that gives you the moral answer to your question right there! You can always go and talk to a lawyer to cover the bases, but I would suggest you're better off spending your time talking to your employer than wasting time and money on a lawyer - after all, isn't it best to know your employer's position before getting a lawyer involved? Oh, and whatever your employer might agree to be sure to get it in writing so that you are both protected.
|
|
|
|
|
I have been in this situation and what we ended up doing was getting management to put an open source license (MIT, APACHE, etc.) on the libraries... not their proprietary finished product but on some of the low level libraries we had written. They agreed and everyone was happy forever. 
Eric
|
|
|
|
|
Simple, go ask your boss, if he says no, then go and read your contract, if it says that anything done in your time is yours, go ahead and recreate the libraries from scratch.
|
|
|
|
|
You can rationalize all you want, but your employer owns that code. Taking it from them would be stealing.
If you can get permission to use the library, do so. In writing. Where its clearly stated that you have permission to use it for outside professional projects. I can't see that happening.
Or, you can just recreate the libraries at home from scratch. Not steal and try to obscure its origin by changing variable names, an actual ground up rewrite. There's always tons of stuff to improve in a rewrite anyway. However, check your IP agreement carefully, many companies' agreements claim to own everything you develop, inside or outside of work.
Instead of any of the above, you could try to convince them to give something back to the community that helped their developers and release an open source fork of that library. Then everybody wins. They win at least in the goodwill & public image departments, and perhaps by having other the community make it better.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
That's exactly what my attorney confirmed. If you're developing something (off company time on your own equipment) you can use it as long as it doesn't compete on any level with your employer. My employment agreement reads that any inventions, discoveries, yadda yadda yadda that I make that relate to their product belongs to them whether I do it on my time, equipment or anything else. Now if I come up with something totally outside their business then that's different according to my contract. However yours may be written to say ANYTHING you invent (regardless of whether it relates to their business or not) belongs to them ... then that's it.
In my case this means I can develop a whole bunch of things of my own on my time as long as I'm no competitive threat ... which is actually a very generous way to write it from their end. They don't mind me creating things on my own, just not stuff that will cut into their business.
YMMV
|
|
|
|
|
CodeBubba wrote: which is actually a very generous way to write it from their end. They don't mind me creating things on my own, just not stuff that will cut into their business.
Why would they mind and why is that generous? I call it common sense and courtesy 
Besides, any knowledge you get at home developing your own projects you take to work where it will probably benefit your employer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
