Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Taking best practices is not the same as taking trade secrets. It's ambiguous and murky, yes, but realistically, if it is ambiguous and murky, the case is likely to fall apart. It's when it's clear that you took some secret sauce with you, and replicated it wholesale, that a case is likely to be brought, and likely to be won.


nobody can actually point out 'best practices' even if you implement them in new company.

in this case, they literally copied code and that's why there was a case after the email gaffe.


How about stuff like how you set up your automated tests, or the Python project folder structure, or that you always first test the road sign recognition on self driving cars before testing something else. Or you first pretrain your neural nets of lane detection before jointly training for road signs and lanes.

I mean you remember the code you wrote and when faced with a similar case you will solve it in a similar way. The above are just really silly simplified examples for it.


That's the point I was trying to make. You can't really 'catch' someone using the same logic to write similar code.

If I change companies, I am going to write code in the same way and test it in the same way.

It'll be very difficult for my original company to 'sue' me if I were to code for the other company unless I do something like this guy did.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: