51–60 of 271 posts
if you can get in touch with a director about this, and they are smart, they will probably want to fix this for everyone after about a moment's consideration.
Oh do I hate this line. But it's a two-way street. I'm very fortunate that for one of my first freelance gigs, I read the contract and specifically pointed out that I would be using personal/open sourced code snippets, and that I might want to reuse/open source some of the code I produced for them (only snippets with general interest).
They agreed without a flinch, and thanks to that experience, I'm going to hold every other employer to the same standard "I never had a problem with this request with any other employer, why would you want to refuse?"
Earlier quoted context omitted.
Would it be possible to link that discussion?
Interesting. This is from 2010, but random googling took me here: https://github.com/snapframework/snap-server/commit/5e4850d4... The situation is quite simple: - pre-existing work I contributed to this project remains under my copyright - contributions other people make to this project remain under their own copyrights - contributions I make to this project subsequent to November 2010 are under Google copyright - no…
When it comes to Amazon, you have employees sending patches upstream anonymously because the company culture is against contributing anything back to the open source community.
I'm not trying to defend gigster (broad indemnification clauses are bad news), but if someone framed those questions to me that way, I would also be hesitant to respond to them. It raises the "I'm going to be a handful" alarm. So, I understand why they were hesitant to respond and didn't want to comment on it.
I don't agree in the slightest. If anything, developers who ask questions are the ones you want most . One of the worst traits in a developer is the tendency to say yes to everything.
I didn't say that. I said that I disagree with the way he framed his questions.
Earlier quoted context omitted.
I don't agree in the slightest. If anything, developers who ask questions are the ones you want most . One of the worst traits in a developer is the tendency to say yes to everything.
Yeah, but there are thousands of devs who say yes to gigster. That's enough to make money.
I recently learned from a github discussion that if you work for Amazon, Google etc. you are also not allowed to work on any open source projects, even on your free time without their permission.
However the company does not claim copyright or patents on work-unrelated ideas and (closed-source) projects.
I do contract work a lot in the UK through recruitment agencies. I very often provide feedback like this, especially when i'm asked to opt-out of the agency regulations. I never opt out, every single time i get the a response along the lines of "In my 20+ years of recruiting we've never had any problems with the contractor not opting out of the agency regulations, you're the first person to ever do that. Can i ask wh…
My question is: Does this ever actually result in them amending the contract? If not, do you then refuse to sign (as I suppose OP did in the gigster case)? If so, what happens if you discover that everyone's contracts are similarly problematic?
Basically i dont stand for their shit, but i'm in a very privileged position of never once been desperate to accept a position, its always been very easy for me to find work. So if i need to walk away, i will. Its those who dont have this option and will agree to any terms put in front of them i feel sorry for.
I do contract work a lot in the UK through recruitment agencies. I very often provide feedback like this, especially when i'm asked to opt-out of the agency regulations. I never opt out, every single time i get the a response along the lines of "In my 20+ years of recruiting we've never had any problems with the contractor not opting out of the agency regulations, you're the first person to ever do that. Can i ask wh…
My question is: Does this ever actually result in them amending the contract? If not, do you then refuse to sign (as I suppose OP did in the gigster case)? If so, what happens if you discover that everyone's contracts are similarly problematic?
Once my lawyer and their lawyer got to the point they talked directly, contract modifications and negotiation proceeded at a brisk pace.
But many companies were offended I didn't just blindly sign the contract. Even when they clearly contained clauses that were problematic.
I was also routinely handed contracts with clauses that would have forced me to violate other contracts if I signed both. For instance, one contract would require me to disclose anyone else I worked with over a 24 month period while another contract would prevent me from disclosing anything about an engagement. (I usually signed neither.)
Thankfully my main client's contract was eminently sensible, so I mostly worked with one amazing group of engineers for awhile.
Eventually some of the annoyances of freelancing made me come around to exploring a full time position. So I am in one of those now and enjoy it actually quite a bit.
Earlier quoted context omitted.
I don't agree in the slightest. If anything, developers who ask questions are the ones you want most . One of the worst traits in a developer is the tendency to say yes to everything.
>If anything, developers who ask questions are the ones you want most. One of the worst traits in a developer is the tendency to say yes to everything. I didn't say that. I said that I disagree with the way he framed his questions.