Slashdot Mirror
Software Development Practices At Google
prostoalex writes "It's widely known that Google allows its engineers to spend 20% of paid work time on personal projects (that are nevertheless considered property of the company). But how does the practice actually work? Joe Beda provides a helpful insight in his blog, pointing out other interesting software development practices at Google. The code database is open for everyone, the snippets and pieces are documented and one is encouraged to re-use existing code. The intranet is transparent to the max and the company accepts the fact that there's more than way to accomplish something, so a better method is always welcomed. Interesting to note that just like Hawaiian shirt days in Office Space, the 20% per projects are "actively encouraged" - Joe suspects his review ratings might slip if he doesn't have one soon."
Here
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Except California law states that if you do it on your own time and on your own equipment, you own it. Its not legal to request an employee to sign that away, and is not enforcable. Burden of proof is on the employer to prove the employee did it on work time, rather than the reverse. In this state those IP agreements are a scare tactic, nothing more.
I still have more fans than freaks. WTF is wrong with you people?
Except California law states that if you do it on your own time and on your own equipment, you own it. Its not legal to request an employee to sign that away, and is not enforcable. Burden of proof is on the employer to prove the employee did it on work time, rather than the reverse. In this state those IP agreements are a scare tactic, nothing more.
No, that's not at all true. The first exception in CA Labor Code Section 2870 says it doesn't apply to inventions which:
(Feel fre to Check it yourself.)
If you work for a large software company, that covers a *lot* of ground.