4 ms·
"What you're proposing would of course be fine" Not if the company are claiming ownership (even in the vaguest of ways) of the code and think there is some val
by arethuza 14y ago
"What you're proposing would of course be fine"
Not if the company are claiming ownership (even in the vaguest of ways) of the code and think there is some value in it - in that case "destroying" it could be a remarkably bad thing to do.
[NB I have been involved in litigation over ownership of code and although we were 100% in the right it was an appallingly stressful experence - mostly because logic seemed to go completely out the window once things turned nasty].
- noonespecial 14y agoDestroy might not mean quite what I'd hoped in this context. I more meant make completely inaccesible to everyone. If the employer claims exclusive ownership, require the overtime pay before you allow them to benefit from it again. No matter what you signed as an employee, OSHA(1) has rules about how long you are required to work without overtime. Its a clever end run I've seen used around "we own everything you do at any time" BS that employment contracts often have in them. Yes, they may own it, but they will have to pay for the time taken to create it. Usually when faced with a big bill, thy decided it wasn't so important to own it after all. (1) Sorry, that was dumb. OSHA just enforces some of these rules. The rules are actually The Fair Labor Standards Act.
- nevinera 14y agoI am only guessing from the contents of the post, but it sounds like they were asserting possible infringement against his own previous work, not ownership of the library he developed on his own time. It is best to be careful though, I much agree. They'd have a tough time proving ownership of that code unless he was also using it in one of their applications, but that crap can get very complicated.