4 ms·

In my program, I had to sign a non-disclosure when doing an assignment for a local tech company. They didn't use anything I made, but I can't share it. It's bas

In my program, I had to sign a non-disclosure when doing an assignment for a local tech company. They didn't use anything I made, but I can't share it. It's basically gone for a minimum of 4 years. I always feel like I've lost a little bit of myself when I lose code or IP I've created, even if I'm paid for my time.

edw519 17y ago
"I always feel like I've lost a little bit of myself..." You shouldn't. Because you haven't. You are greater that then sum of what you have done. You wrote it once, you can write it again (not exactly the same, of course, but you get the idea). They can claim your work as their IP, but they can't claim who you have become in the process.
- mikedouglas 17y ago
  You wrote it once, you can write it again (not exactly the same, of course, but you get the idea). Can you? That code is now a trade secret for that company, and if you wrote a clone (or compatible version) using your knowledge of the product, that seems like a clear case of infringement.
  - edw519 17y ago
    The code may be IP, but the thinking behind it is not, and who you are most certainly is not. Once you learn how to ride a bike, the owner of that bike has no claim to prevent you from riding another.
    - mikedouglas 17y ago
      IANAL, but the thinking behind it, if not generally known, is definitely a trade secret. Using or disclosing that information to another party is trade secret infringement. If (as an employee of that bike company) you developed a way to make the bike 20% lighter that wasn't readily discernible, you can't leave and start a competing company using that idea. The law around trade secret misappropriation is such a minefield that most companies separate the reverse engineering team from the implementation team (ie. clean room design).
  - ewjordan 17y ago
    You can unless you've signed something that prohibits you from doing so. There's no default assumption of non-disclosure or non-competition when you're taking on a project for a company as a consultant, even if you are required to transfer copyright; most will force you to sign something to that effect, but if they don't, or they don't do it right, you're free to do whatever the hell you want with the information in your head. A lot of these agreements teeter on the edge of enforceability, as well, and if you aren't forced to sign a non-compete it's going to be tough in most cases for a company to prove that a clean-room reimplementation violates the non-disclosure agreement unless you really are relying on information; however, I'd suggest that you consult a lawyer before wading into these waters, and 99% of the time it's not even close to worth the trouble. You're a lot more at risk from a lawsuit (even if you win) than the company is, and you shouldn't be burning most bridges anyhow.

edw519 17y ago

"I always feel like I've lost a little bit of myself..." You shouldn't. Because you haven't. You are greater that then sum of what you have done. You wrote it once, you can write it again (not exactly the same, of course, but you get the idea). They can claim your work as their IP, but they can't claim who you have become in the process.

mikedouglas 17y ago
You wrote it once, you can write it again (not exactly the same, of course, but you get the idea). Can you? That code is now a trade secret for that company, and if you wrote a clone (or compatible version) using your knowledge of the product, that seems like a clear case of infringement.
- edw519 17y ago
  The code may be IP, but the thinking behind it is not, and who you are most certainly is not. Once you learn how to ride a bike, the owner of that bike has no claim to prevent you from riding another.
  - mikedouglas 17y ago
    IANAL, but the thinking behind it, if not generally known, is definitely a trade secret. Using or disclosing that information to another party is trade secret infringement. If (as an employee of that bike company) you developed a way to make the bike 20% lighter that wasn't readily discernible, you can't leave and start a competing company using that idea. The law around trade secret misappropriation is such a minefield that most companies separate the reverse engineering team from the implementation team (ie. clean room design).
- ewjordan 17y ago
  You can unless you've signed something that prohibits you from doing so. There's no default assumption of non-disclosure or non-competition when you're taking on a project for a company as a consultant, even if you are required to transfer copyright; most will force you to sign something to that effect, but if they don't, or they don't do it right, you're free to do whatever the hell you want with the information in your head. A lot of these agreements teeter on the edge of enforceability, as well, and if you aren't forced to sign a non-compete it's going to be tough in most cases for a company to prove that a clean-room reimplementation violates the non-disclosure agreement unless you really are relying on information; however, I'd suggest that you consult a lawyer before wading into these waters, and 99% of the time it's not even close to worth the trouble. You're a lot more at risk from a lawsuit (even if you win) than the company is, and you shouldn't be burning most bridges anyhow.