News for hackers. Stuff that matters.
Re:We're entering the decade of the developer by Silhouette on Monday November 29, 2010 @01:22AM (#1949570)
1. Never work on your personal project on your employer's time. They're paying for that time, and probably the resources you're using during that time as well, so they have a legitimate claim on anything you do at work.

2. Never sign an employment contract that gives any rights to stuff you do away from work to your employer, or that gives your employer any right to control what you may do out of hours as long as it doesn't affect your ability to do your job properly when you're at work.

In short, you should completely firewall any side project from work. If your contract doesn't allow for this and your employer won't give you a clear, specific exception, then you have to decide whether to keep the employer or the side project, but you can't do both.

Re:We're entering the decade of the developer by wallflower on Monday November 29, 2010 @12:04PM (#1950945)
When I was more naive than I am now, I signed the yeah-all-your-IP-belongs-to-us employment agreement as a condition of employment. This was many years ago and I am still at the same company.

To counteract this, I only do contract work and work on fairly large team collaborations. My thinking is if I don't own it but the client does (since they are paying me to work on it after hours) - the day job company won't have much to go on because I didn't own the code in the first place. For the second - since I don't have full ownership/sole contributor - maybe that will make them less likely to go after me than a clean cut single owner situation.

All of these projects are done on non-company time, network, and hardware. I don't usually bring my MacBook in but when I have a client deadline, I will work on my train commute and not even charge the MacBook using (company) power - I tote around a second battery.