3 ms·
The main reason not to code on evenings and weekends is that your employer will own everything you do and might not allow you to do whatever you want anyway.
by mgaunard 2y ago
The main reason not to code on evenings and weekends is that your employer will own everything you do and might not allow you to do whatever you want anyway.
- recursive 2y agoGet a better contract I guess.
- ghaff 2y agoThat seems a gross overgeneralization--although you might want to check if it might be an issue.
- sarchertech 2y agoDepends on the state and the terms of employment you agreed to. I’ve never agreed to let an employer own anything outside of a very specific scope. And I’ve rarely had to turn down a job because of that constraint. Employers have almost always had a reasonable scope with respect to what they own to begin with or have been fine with changing the scope to be more reasonable.
- phito 2y agoWhat? Do you know you can code for yourself and not for your employer?
- skirmish 2y agoI think the GP is referring to practices like [1] "Google claims copyright on employee side projects". [1] https://news.ycombinator.com/item?id=21823413 https://news.ycombinator.com/item?id=21823413
- mgaunard 2y agoAny employer that pays decent money will claim ownership on everything you do even if you do not use any of the company's resources to do so.
- phito 2y agoThat's absurd.