Earlier quoted context omitted.
Dont repeat yourself. IF you have code that solves a problem, dont rewrite it at every gig...
Now thats a philosophy I both agree and disagree with. Agree: omg do i need to write this form again? Seriously just write a library already! Disagree: this problem is subtly yet incompatibly different to what I've seen and dealt with before. The library would need x,y,z but their IP demands mean I'd lose rights to my closed-source library or be forced to open source it to keep using it elsewhere.
Google claims copyright on employee side projects
261–270 of 399 posts
Re: Google claims copyright on employee side projects
#262Earlier quoted context omitted.
Intellectual Property isn't really a thing in itself. It's a vague collection of a couple of different concepts, including Copyright, Patents and Trademarks. Those are three very different kinds of temporary monopolies granted by the government, but the people who promote the phrase "intellectual property" want them to be considered as not a government-granted monopoly on a certain kind of business, but as a natural…
Perhaps we could try to rebrand IP as "Innovation Protections"?
Re: Google claims copyright on employee side projects
#263Oh, please. It's standard industry practice for companies to claim ownership of everything a software engineer comes up with, even "on their own time". The problem is it's extremely difficult to say, figure out when someone might have invented some super clever idea which can be pantented "on their own time". This was true when I worked for MIT, VA Linux, IBM, and Google. At VA Linux it was the VC's which insisted on…
Re: Google claims copyright on employee side projects
#264Re: Google claims copyright on employee side projects
#265Earlier quoted context omitted.
> The worst thing that happened to the OP is that he pissed off some lawyers, and got into an argument with a guy The worst thing that happened to OP was that he lost control of his project. > I ended up having to hand over maintainership of usbmuxd. ---- > You can just always ignore what lawyers say, and just work on open source projects under a pseudonym while you're employed there I am not a lawyer, but this seems…
> I am not a lawyer, but this seems like very bad advice. That's kind of my point. Millions of people have been employed by companies with similar policies, and undoubtably many of them chose to ignore the "correct" legal moves because it's just easier. If Google really wanted to screw people over, they could, but that doesn't seem to be happening.
But again
> I ended up having to hand over maintainership of usbmuxd.
What's your personal criteria for getting screwed over? From my perspective, it already happened with OP.
Re: Google claims copyright on employee side projects
#266Earlier quoted context omitted.
> Google has become just another US corporation They’ve always been that to me. We should all try to look past hype and focus on the reality, not just the perception of the moment. Does Google handle scale better than the vast majority of other companies? Yes. Did Google build an industry leading search engine? Yes. Did Google steal the patented idea[0] that ended up giving them essentially f!?k you money that has en…
I am never sure why people dismiss hype. Hype is a perception and perception, for better or worse, is reality. My boss thinks I am a bum. Do you think it will be easier to change his mind or change jobs? As to why? Google had a good story. People like good stories.
Let's be honest, good marketing works. For example, there's plenty of cargo culting on HN which is all about hype and following the pack.
We're humans. Hype, marketing and propaganda works.
Re: Google claims copyright on employee side projects
#267Oh, please. It's standard industry practice for companies to claim ownership of everything a software engineer comes up with, even "on their own time". The problem is it's extremely difficult to say, figure out when someone might have invented some super clever idea which can be pantented "on their own time". This was true when I worked for MIT, VA Linux, IBM, and Google. At VA Linux it was the VC's which insisted on…
That doesn't make it acceptable. I've never signed a contract with such clause nor will I.
When I was freelancing one of my clients tried to get me to sign a contract with a clause like this. It would have killed my business since I worked on multiple projects at once. In their case it was an oversight in using a form contract and they changed it.
Re: Google claims copyright on employee side projects
#268Re: Google claims copyright on employee side projects
#269Oh, please. It's standard industry practice for companies to claim ownership of everything a software engineer comes up with, even "on their own time". The problem is it's extremely difficult to say, figure out when someone might have invented some super clever idea which can be pantented "on their own time". This was true when I worked for MIT, VA Linux, IBM, and Google. At VA Linux it was the VC's which insisted on…
If you make a kid (on your own time, with your own equipment, and not in their office), should it also by their property?
Re: Google claims copyright on employee side projects
#270Earlier quoted context omitted.
> US copyright law is extremely friendly to individual creators at the expense of corporations. You must be joking! Yes, the "Work made for hire" requirements are convoluted, but most of the complexity applies only to independent contractors anyways. I have never heard of a US corporation be in danger because of an employee claiming copyright, yet people's personal projects and own companies constantly get screwed by…
See, for example, the entire history of IP in comics, which Disney is now using to print money.
So apparently, companies do have to go through a few hoops to make their claim on their employees' IP airtight.