31–40 of 271 posts
That classic "well, nobody else has had a problem, so you must be the problem" response. I remember at one of my first jobs, myself and another programmer were working on a side project (outside of work hours, not using company resources in any way) that were considering monetising. Our contracts stated that the company we worked for owned all of our code produced in and out of working hours. We got to the business e…
My response is always something like "Thank you for acknowledging my contribution to the innovation to the recruitment industry, i'm very proud to be a pioneer in this field, being first is a great honour. One thing to note, i'm not opting in, i'm refusing to opt out, i dont need to opt-in to the law. I've chosen to do this because theres no reason to and the law specifically protects me from you forcing me to do so. Also, since your client has already decided to hire me, even if i was to opt out, it wouldnt be recognised in court as the opt out paperwork must be signed before i ever meet the client."
For this point on the agency regulations, i do it primarily just to make the recruiters work for their exorbitant markup on my day rate. However i do also question source code and copyright clauses like the author did, almost always, i'm looked at with dumbfoundment that i even bothered to read the contract.
If anyone wants to know the regulations i'm referring to, heres a link: http://www.contractoruk.com/agencies/5158.html
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.
That classic "well, nobody else has had a problem, so you must be the problem" response. I remember at one of my first jobs, myself and another programmer were working on a side project (outside of work hours, not using company resources in any way) that were considering monetising. Our contracts stated that the company we worked for owned all of our code produced in and out of working hours. We got to the business e…
The probability keeps getting lower as new members join :|
That classic "well, nobody else has had a problem, so you must be the problem" response. I remember at one of my first jobs, myself and another programmer were working on a side project (outside of work hours, not using company resources in any way) that were considering monetising. Our contracts stated that the company we worked for owned all of our code produced in and out of working hours. We got to the business e…
Is this common in contracts??
My first thought: WTF is gigster?
Remember, if it's in the contract, it's what's happening. Let no amount of promises persuade you.
That classic "well, nobody else has had a problem, so you must be the problem" response. I remember at one of my first jobs, myself and another programmer were working on a side project (outside of work hours, not using company resources in any way) that were considering monetising. Our contracts stated that the company we worked for owned all of our code produced in and out of working hours. We got to the business e…