3 ms·
OK, I was contracting in my previous life so I've seen these issues pop up many times before. Here's few words. A) is illegal. You have no ownership of ANY cod
by nickb 19y ago
OK, I was contracting in my previous life so I've seen these issues pop up many times before. Here's few words.
A) is illegal. You have no ownership of ANY code or IP that you work on at the company that employs you. That's what they're paying you for, after all.
B) is also illegal. Unless the company in question has open sourced their code and allows anyone to use it under some kind of a BSD-like license, you have absolutely no right to use that code or IP.
Not only are both of these cases illegal, they're also highly unethical. Also, if you're forming a company around someone else's IP, you're gonna crash and burn.
When I worked as a contractor, I would use my own libraries to save me some time but before I used them, I notified the management that I was using them and told them that I own the code and that I give them full right to use it without any licensing fees and I also told them I would use them on my other contracting jobs. They always accepted these stipulations an I've never had any problems. They loved the fact that I was not wasting my time and their money re-implementing the wheel and that I was solving their problems in record time. The key is to be open and put it all on the table before you start working.
Also, after I'd finish working on a project and if I was using my own computer, I'd wipe my computer clean of all of their code. I would do that on the last day of my job and I ALWAYS made sure that someone from the management was there to witness it. Sure, that might be going overboard but trust me... it's worth it. It shows them that you care about these sorts of things and it also makes sure that they won't have a strong case if they ever decide to sue you down the road because you end up inventing something amazing that's in their marketspace or you end up working for competition.
- menloparkbum 19y agoYou are totally wrong. In a contracting situation, the CONTRACTOR owns all the code he or she produces unless the contract specifically states otherwise.
- jsjenkins168 19y agoThe contract almost always states otherwise though. Unless maybe you're working in an area where the companies doesn't care about their IP or are just simply ignorant.
- juwo 19y agoThis is the other extreme - which I didnt mention in the op. I agree that copying code is wrong - but what about a good idea that you come up with, or a neat design or technique in code? It seems unfair given that doctors, scientists, marketing and many other professionals can keep a record of their work. Maybe not reams of data, but something. (I am not 100% sure of the extent they are allowed to). All art professionals have portfolios. Is your brain just a vessel to be washed clean before it is rented out again? Again, I am not talking of secret algorithms that would break a company, not someone else's work.
- menloparkbum 19y agoI've worked on over 20 software contracts and never once did the contract contain a clause that forced me to assign copyright agreement to the person paying for the software. Note that this only applies to contractors, not exempt employees. http://www.developerdotstar.com/mag/articles/daniels_softwarecopyright.html http://www.developerdotstar.com/mag/articles/daniels_softwar...
- jsjenkins168 19y agoEnterprise software? That surprises me based on my limited experiences, but all the better for you I imagine you own a sizable amount of useful code by now. Great article btw, thanks.
- menloparkbum 19y agono problem. I've never worked on enterprise software. mostly weird, short term stuff for startups, researchers and artistes. the code was sometimes fun, but sadly, almost never useful outside of the specific contract.
- nostrademons 19y agoInteresting...at the places I've worked (as an employee), it was considered a dealbreaker if a contractor wanted to own the source code they produced. We passed up some really, really good contractors because they wanted to own the product.
- nickb 19y agoWhere exactly am I wrong? Point the sentence. Of course you have to assign them IP! That's what they're paying you for! Ever contracted for the government?! Look at their 20 page assignment agreement. http://www.developerdotstar.com/mag/articles/daniels_softwarecopyright.html http://www.developerdotstar.com/mag/articles/daniels_softwar...
- menloparkbum 19y agoYou are right in the case of a full time employee. You are wrong in the general case of contract software engineering. Most software development contracts DO NOT have a 20 page assignment agreement that assigns copyright to the person/company paying for the work. It sounds counterintuitive and false, but that really is the case. You, the contractor, own the IP unless you sign your rights away. And even if you do, it probably won't hold up in court. In regards to the government, I admit I don't know, I've never contracted for the government. Also, I find it strange that the link you provided argues directly against your position.
- staunch 19y agoYou can absolutely sign away your IP rights in a contract. Unless the contract is crap it will certainly hold up in court. The contracting business would be a lot less healthy if this wasn't the case. Everything else you said is correct from what I know -- at least in California. The neat thing about the labor laws in California (and some other states) is that they protect you from signing away lots of other rights as a full-time employee. It's difficult to enforce non-competes against former employees for example.
- randallsquared 19y agoI write software as the largest part of my business, and I don't think I've ever been asked to assign copyright to the purchaser. I go out of my way to point out in written materials that I use licenses like GPL, BSD, and put stuff in the public domain when that's compatible with library licenses and such, but no client has ever actually asked me about that. In my experience, people who are buying custom software don't even think about copyrights and licenses; it just never occurs to them.