Hacker News new | ask | show | jobs
by mgaunard 527 days 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.
4 comments

Depends 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.
That seems a gross overgeneralization--although you might want to check if it might be an issue.
Get a better contract I guess.
What? Do you know you can code for yourself and not for your employer?
I think the GP is referring to practices like [1] "Google claims copyright on employee side projects".

[1] https://news.ycombinator.com/item?id=21823413

Any 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.
That's absurd.