Hacker News new | ask | show | jobs
by lighthawk 3925 days ago
I thought that the way you solve this in the states is by setting up an LLC and copyrighting under your LLC all of the code you write during hours you are not working for the other company. Doesn't that provide adequate additional protection? The strict IP agreements I've signed usually exclude work done for other companies.
1 comments

Some contracts have a clause where you work exclusively for this employer.
Yes, but if they enforce that, they might fire you but they won't be able to take your IP away. Not if they exclude the IP you produce for other companies as part of the IP agreement.
Often referred to as a 'moonlighting' clause and by lawyers as 'duty of loyalty'.
Love how loyalty only works one way.
When you sign up to work for the company, you agree to do X and they agree to pay you Y. You are disloyal to them if you don't do all or part of X (for instance, if X includes thinking up ideas for them, taking your really valuable ideas that you thought up while working for them and leaving and using them yourself), and they are disloyal if they don't pay you Y. Those are the terms, after all! So I don't see how loyalty only goes one way...
If I'm at home, on my own computer, on my own time, I am not "working for them".
If they don't have an impressive QER, I get axed. That's what I mean.