This is a great step by Rackspace, to be clear. All I'm saying is that it's mistaken to believe that most big companies will force you to sign an agreement stating that your code written on your own free time is theirs.
Actually, I was slightly mistaken originally. One time an employer tried to pull that, but when I pointed it out, they were willing to cross out the clause, because I was willing to walk away.
The catch here is you read the fine print. Many employees don't, and even if they do they miss assignment of invention clauses, non competes, etc. I too have asked to strike our the invention clauses - in one case they said ok, then backtracked and "lost" the struck through portion when I quit, the other refused "what are you hiding/planning".
It stinks that it's 2014 and invention clauses and non competes are basically default boilerplate, even in jurisdictions where they're unenforceable.
Comments
This is a great step by Rackspace, to be clear. All I'm saying is that it's mistaken to believe that most big companies will force you to sign an agreement stating that your code written on your own free time is theirs.
Actually, I was slightly mistaken originally. One time an employer tried to pull that, but when I pointed it out, they were willing to cross out the clause, because I was willing to walk away.
Perhaps I was just lucky three times in a row?
The catch here is you read the fine print. Many employees don't, and even if they do they miss assignment of invention clauses, non competes, etc. I too have asked to strike our the invention clauses - in one case they said ok, then backtracked and "lost" the struck through portion when I quit, the other refused "what are you hiding/planning".
It stinks that it's 2014 and invention clauses and non competes are basically default boilerplate, even in jurisdictions where they're unenforceable.