4 ms·
In Australia, I worked for a company that had what amounted to a "we own all your brainz" clause in their contract. I queried it, and they modified it: they ow
by etfb 14y ago
In Australia, I worked for a company that had what amounted to a "we own all your brainz" clause in their contract. I queried it, and they modified it: they owned anything I produced using their hardware, during paid time (excluding lunch breaks) or using knowledge I'd gained directly from working for them. Everything else, even stuff I did in the lunchroom using my laptop, was mine. The boss's son apparently agreed with me that the original clause was silly and may have been instrumental in getting his Dad to change it; or maybe the boss was just a reasonable guy. Actually, I think the latter is true. They were a good mob, and I was sad to leave.
- qw 14y ago> or using knowledge I'd gained directly from working for them I wouldn't be comfortable with that. If you have gained knowledge on Redis, you should be able to use Redis in a personal project. It would be different if you had developed a super secret ranking algorithm that you later re-implemented in another project.
- etfb 14y agoThey made it clear (I don't recall the wording) that knowledge I gained for myself while working -- from co-workers, from research done as a necessary part of solving problems, etc -- wasn't the issue; it was specifically knowledge about the business and the topic it covers, which was related to the medical field, rather than knowledge of computer-specific issues. So: software projects relying on my knowledge of XSLT gleaned from working there: fine, not a problem; software projects to prescribe warfarin safely: not so fine. This was a good balance, and I had no trouble with it.