Earlier quoted context omitted.
I wonder if this would become more common with things like ChatGPT. Let's say you've been working in place A, you show your code to an LLM service (like the dozen or so Copilot-like services) and tell them to refactor. And for the sake of argument, let's say the LLM uses your code and questions for its next training dataset. A few years pass, then you go to work at Place B, and ask a question that happens to be relat…
For this reason, and a few others, my workplace simply put a blanket ban on these kinds of tools. If our code is never exposed to the learning tool, it’s never in danger of being showing up somewhere else. Incidental to that, I feel like these tools expose the reality behind “copyrighting code/math” and how fallacious it is. If the tool can generate the efficient methods of achieving a result, I think it becomes obvi…
Nvidia sued for stealing trade secrets: blunder showed rival company's code
161–170 of 242 posts
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#162Tertiary point but one that been on my mind… What’s the difference between one person doing it individually and a company doing it to train an AI? I mean isn’t this exactly what a lot of LLm training data is built on as well? I get there might be different legalities, but morally isn’t it all basically merely degrees of theft? Like this is trade secret theft, but training an AI on the code isn’t? You can download a c…
How is this morally theft anymore than hiring someone who has experience solving the problem to solve the problem again? As long as they aren’t reproducing the solution verbatim it’s already morally acceptable to hire experts for their experience. Why would “hiring” software for its “experience” be different?
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#163Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#164Earlier quoted context omitted.
There is tremendous upside. You can look like a rockstar at the new company and propel yourself upwards with that momentum.
More like a shooting star once your perfidy is discovered.
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#165Earlier quoted context omitted.
At some point I was told to never ever look at a competitor's patents, because doing so would worsen the penalties if it turned out that our design infringed upon them. Can you confirm that's true? Doesn't that mean that in general it is also a really bad idea to ask an engineer questions about a particular piece of tech that they patented at a previous employer, even though the specific information is a matter of pu…
Willful infringement allows for up to triple damages. The expectation is you can't do willful infringement if you're not aware of competitor's patents, and you can't be aware of them if your policy is to never look at patent documents. Or that's the idea anyway.
"Willful blindness" can be a danger (according to the Supreme Court, albeit in a different context).
Possibly a bigger danger: Your product gets kicked out of the market by an injunction (a court order to stop making, using, selling, etc.)
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#166Earlier quoted context omitted.
I’m sure we’ll all be glad one day that Apple shared this research breakthrough: https://www.theverge.com/2017/11/6/16614038/apple-samsung-sl...
A good example of a patent that was challenged in court and wasn’t totally invalidated is Amazon’s 1-click ordering. They patented storing customer shipping and payment details in a database so they could purchase something with a single click. It expired in 2017 but for the period it was in force, Amazon collected millions in licensing fees.
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#167Earlier quoted context omitted.
> Nvidia did hire him precisely for his previous experience at this rival company, on the very same project that the two companies were partnered on, which is the same project that Nvidia hired him for. Yes, this happens all the time. > There is no argument to be made that Nvidia wasn't aware he'd be coming with secrets. This is not a logical conclusion from the above. Hiring for the exp is fine. Hiring for the trade…
A thought that came to me recently in the shower: Isn't all knowledge effectively based on previous knowledge, and by extension, experience? i.e: A programmer knows how to do X, leaves a company to do Y, where Y is in the same field of work as X. Doesn't X still affect the programmer on a subconscious level and henceforth, their thoughts indirectly?
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#168Earlier quoted context omitted.
I wonder if this would become more common with things like ChatGPT. Let's say you've been working in place A, you show your code to an LLM service (like the dozen or so Copilot-like services) and tell them to refactor. And for the sake of argument, let's say the LLM uses your code and questions for its next training dataset. A few years pass, then you go to work at Place B, and ask a question that happens to be relat…
For this reason, and a few others, my workplace simply put a blanket ban on these kinds of tools. If our code is never exposed to the learning tool, it’s never in danger of being showing up somewhere else. Incidental to that, I feel like these tools expose the reality behind “copyrighting code/math” and how fallacious it is. If the tool can generate the efficient methods of achieving a result, I think it becomes obvi…
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#169TFA makes it sound as if the entirety of the blame can be placed on one employee. Sure, his actions do seem to support that view, but then again, Nvidia did hire him precisely for his previous experience at this rival company, on the very same project that the two companies were partnered on, which is the same project that Nvidia hired him for. There is no argument to be made that Nvidia wasn't aware he'd be coming w…
A problem here is that while the companies will generally make very clear that they don't want you to have any single line of code, any schematic, any drawing, anything at all from your previous company; they may also expect you to bring "experience" from the previous company, thereby pressuring more junior employees into doing exactly that - bringing some docs from the previous company - but not telling about it. Th…
Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code
#170Earlier quoted context omitted.
At some point I was told to never ever look at a competitor's patents, because doing so would worsen the penalties if it turned out that our design infringed upon them. Can you confirm that's true? Doesn't that mean that in general it is also a really bad idea to ask an engineer questions about a particular piece of tech that they patented at a previous employer, even though the specific information is a matter of pu…
Just search it in Yandex with a VPN, and in a Tails VM just for paranoid-icity. I did similar for medical self-symptom before ACA prevented "pre-existing condition" scam.