131–136 of 136 posts
Earlier quoted context omitted.
Do you have some examples of IBM torpedoing companies in California on this basis?
This is about individuals (ex-IBM employees), not companies. This might be an example: https://www-03.ibm.com/press/us/en/pressrelease/26551.wss
Earlier quoted context omitted.
About your point about Lotus Notes: I interned at IBM 3 times, and was never forced to use Lotus Notes. No one whom I worked with at IBM used Lotus Notes either. We used either Open Office or MS Office. The most popular IBM software we used was SameTime for instance messaging and it was actually not bad at all.
Just as a counterpoint: when I interned at IBM, we were forced to use various Lotus products including Notes. Lotus Symphony was especially painful, and we begged to be allowed to just use Powerpoint (and were told, emphatically, "No.")
I learnt Python from "Dive Into Python 3", but that hasn't been updated for few years now. Any similar book with recent updates?
Earlier quoted context omitted.
Not sure why you think that. Here's California's moonlighting law: "Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer’s equipment, supplies, facilities, or trade secret information…
> without using the employer’s equipment, supplies, facilities, or trade secret information Good luck trying to prove that against IBM's lawyers and patent portfolio.
Anybody? https://en.wikipedia.org/wiki/Sun_acquisition_by_Oracle
Despite both being big enterprise corporations, IBM is nothing like Oracle. Oracle is pretty much one huge ego trip swallowing everything like the Borg.
Earlier quoted context omitted.
" * The IP agreement was Draconian (and we aren't in a state with nice moonlighting laws) " None of these exist in the US (particularly when you work for someone like IBM). Employees who think otherwise are simply misunderstanding the law :)
Not sure why you think that. Here's California's moonlighting law: "Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer’s equipment, supplies, facilities, or trade secret information…
You forgot the super-important part, which are literally the words after what you quoted, which say: " except for those inventions that either: (1) Relate at the time of conception or reduction to practice of the invention to the employer’s business, or actual or demonstrably anticipated research or development of the employer; or (2) Result from any work performed by the employee for the employer."
#1 covers pretty much everything tech related that tech related people do. For example, if you work for IBM, i doubt you can find anything not related to IBM's business, or the R&D of IBM. Becuase it's not what you think IBM's business is, it's what IBM think it's business is. It also doesn't matter whether it's a secret project you don't know about, or historical, or anything.
It makes no difference what you do for the company either. If I work as an IP lawyer for Google, and Google builds self-driving cars (among other things), any work i do on my own time related to self driving cars is Google's.
Note also "related to", not "exactly the same as". So if it's in the same area, field, etc, you are screwed.
But you don't have to take my word for it, look at court cases in CA, which find the same :)
Now, maybe if you work for a small, super-focused company, you may be okay.
But good luck if you work for any mid or large sized tech company, which often have so many projects, strategic initiatives, and research that it covers pretty much everything in the world.
To wit: In every case an employee has come to me saying "well, we don't do that, so why would you own it", it has been a case that the employee did not know there was a team doing it. I have never had a case of an employee coming to me and it turned out "yeah, you know what, we don't really do anything in that area"