2 ms·
Yeah I always check this too - and if needed add a clause to my contract to make it clear that programming work I do outside of business hours & using my own eq
by josephg 2y ago
Yeah I always check this too - and if needed add a clause to my contract to make it clear that programming work I do outside of business hours & using my own equipment remains mine. I do a lot of opensource work and it would be a disaster to have copyright ownership clouds hanging overhead.
But for a company to assert a copyright like this, they would have to actually sue. And companies will always be loathe to sue employees over incidental stuff like this because the negative press will almost always make it not worth it.
- bruce511 2y agoThe point raised by the article is the reverse. They agree with you that your company does not want to sue. Specifically (in some cases) they explicitly remove your ability to sue violators. Obviously each company and employee situation is different, but the default position is they own the copyright, and they'd prefer not to sue anyone. This leads to copyright violations being ignored. Whether violations are something you care about or not is up to you. Personally I don't get over wound up by it (my code is pirated all the time) but others feel very strongly in this space. This article is pointing out that if you do care, then it pays to make sure where your copyright exists.