Further, "employer's line of business" is very loosely defined. If you could share the technical skills between your job and the side project, you are most likely in the same line of business.
Here's a book I highly recommend: http://www.amazon.com/Intellectual-Property-Open-Source-Prot...
(California has a carve-out in state law: an employer can't claim stuff that was not done on company time, nor with company resources, and which does not relate to the company's business. But many states, perhaps most, have no such carve-out. And even the California rules are subject to interpretation; what isn't related to the company's business if the company is Google? So, it's wise to consult a lawyer regardless...)
Trying to fight your way out from under a noncompete, or lawyer up on account of a side consulting gig or independently conceived and developed idea, really stinks. And the further you get in your career the more likely you'll encounter such a situation.
Such cases ultimately seriously dampen both enthusiasm for the employer, and the odds of finding talent interested in working under such a regime.
Of course, the ultimate negative would be for California's exceptions to be attacked by corporate interests.
Georgia recently amended our constitution to make non-competes much more likely.
I and much of the tech scene hugely lobbied against this effort, oh well. We didn't need to work for in state companies anyhow.
Those sorts of clauses really suck the fun out of life. "Gee, I'd have a hobby and share my work with the world, but my employer owns everything I do. I think I'll play video games instead. They can't take that from me!"
If, according to the contract you may have signed with the employer, the IP you create belongs to the employer, and that IP is earning a lot of money, then the employer is liable to the shareholders for recovering that money or an appropriate portion since it legally belongs to them.
This is in addition to the point in the OP, which is you may be exhausted while at work.
Ability for <Company> Employees to Accept Project Work Outside of <Company> Time
It is the policy of <Company> to allow employees to accept and function as independent contractors for other companies/projects while on their own personal time. That being said, the non-compete/confidentiality agreement remains in force at all times and <Company> trusts that this binding agreement will be upheld on the part of all employees and contractors.
Here are my thoughts:
* My side projects have—without fail—made me better at my day job. For instance, when I had my last 'real' job as an iOS developer for a startup, my side project was Cocoa Controls[2] (http://www.cocoacontrols.com), which shaved dozens-to-hundreds of hours off our development schedule.
* My side projects don't compete with my employer's line of business (or potential future directions). The last thing I want is to get embroiled in a lawsuit down the road over IP theft.
* My side projects never use company resources. That means no working on it at work, and no using that company laptop.
* I do my best not to discuss my side projects with my coworkers. I'm happy to chat about them if they bring them up, but I don't go out of my way to discuss them.
* Way back when, when I worked at Microsoft, I had to sign a moonlighting agreement that specifically spelled out what belonged to whom and what each party's responsibilities were. If your company doesn't have one, I recommend trying to introduce one.
[1] http://www.seattlepi.com/business/article/Seattle-startup-Di...
[2] Which is now my real job. Win.