Live data from Hacker News

An Email Thread Between a Developer and Gigster

andychase.me

201–210 of 271 posts

Re: An Email Thread Between a Developer and Gigster

#201
post #108

Earlier quoted context omitted.

If you are interested in collective action to combat clauses like this, follow Maciej Cejlowski.

Follow him how?

He's at 3rd and Market right now. Head on over.

(Or try here: https://twitter.com/baconmeteor )

Re: An Email Thread Between a Developer and Gigster

#202
post #200

Earlier quoted context omitted.

Damage control. They went from "lol, you're the only one with a problem, get lost!" to "hmmm, this is generating bad publicity.. now we definitely sympathize with your concerns!" real quick. As far as I'm concerned, I now know all I will ever need to know about Gigster. Your reputation is something that takes a lifetime to build and only 5 minutes to ruin permanently.

> Your reputation is something that takes a lifetime to build and only 5 minutes to ruin permanently. This is the most important takeaway from this entire sad thread. Wonderful comment!

Thanks! But let me make sure I properly credit Warren Buffett for it :)

Re: An Email Thread Between a Developer and Gigster

#203

Earlier quoted context omitted.

If this comment had been the last email response in the chain, I think that would have been great. The fact that it wasn't, that an important issue was dismissed when raised in private, speaks far more to me than this public response.

Damage control. They went from "lol, you're the only one with a problem, get lost!" to "hmmm, this is generating bad publicity.. now we definitely sympathize with your concerns!" real quick. As far as I'm concerned, I now know all I will ever need to know about Gigster. Your reputation is something that takes a lifetime to build and only 5 minutes to ruin permanently.

> Your reputation is something that takes a lifetime to build and only 5 minutes to ruin permanently.

A quote I read somewhere recently: your reputation grows like a coconut tree, but fall like a coconut.

Re: An Email Thread Between a Developer and Gigster

#204
post #46
post #11

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…

Why not draft up something to give to the company disclaiming all rights to your work? If lawyers are too expensive for the company, I'm sure they'll sign it right away! I'm guessing the HR person is just incompetent and the issue should be escalated. What exactly does a company think is going to be the outcome of saying "Oh, BTW, we might sue you for this, we might not and we're not going to give you a straight answ…

A very good reading on the subject https://www.joelonsoftware.com/2016/12/09/developers-side-pr...

Re: An Email Thread Between a Developer and Gigster

#205
post #11

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??

Yup, very common. https://www.joelonsoftware.com/2016/12/09/developers-side-pr...

Re: An Email Thread Between a Developer and Gigster

#206
post #11

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…

> That classic "well, nobody else has had a problem, so you must be the problem" response.

To anyone reading this that gets this response in a negotiation, this is the go to line for any experienced negotiator when you come to them with questions about a contract. Always. Its like negotiation 101. Do not take the response at face value. Its a canned line that doesn't mean anything on its own.

The typical response is to say that it makes a good impression on the organization that they have yet to have any contract disputes and then get back to asking about your specific issues.

Although, the harsh reality is that for them to change this contract means they need to bring a lawyer into the situation and that costs them money. So realistically you need to be in a situation where you have some kind of leverage in the situation. That is pretty rare when you are alone on the labor side as opposed to the capital side. Sometimes you have to decide between taking a risk of getting screwed or walking away. Unfortunate reality of our economic system as it currently stands. As unions learned a long time ago, labor protections via government regulation is typically more effective than private negotiation. Without that, most people just have to learn to accept they you are going to get taken advantage of and work around it.

Re: An Email Thread Between a Developer and Gigster

#207

So I hate to disappoint everyone. Such contract really cannot be viewed the way this was summarized through an email. One paragraph has to be interpreted in the context of everything else. Moreover, everyone uses this language. It is funny, but I suspect that most of Silicon Valley just recycles the same 3-4 contracts, that individual lawyers just modify slightly. I have now worked with 60+ tech companies (Looker, Gi…

Anything not enforceable shouldn't be in the contract in the first place. The only purpose of contracts is to enforce earlier promises when people don't agree anymore.

Re: An Email Thread Between a Developer and Gigster

#208
If you can clearly demonstrate that you are not competing with your employer, using their IP, working on their time, using their equipment then these types of non-competes should be null and void. And yes, I quit a job over that kind of contract. If I invent something on my time it's mine.

Re: An Email Thread Between a Developer and Gigster

#209
post #67

Earlier quoted context omitted.

I give a similar reply when being asked to remove an interest penalty clause for late payment. " We always pay our bills on time so there's no need for that! " " Great! In that case you don't have to worry about every paying it either so we'll leave it in! "

Here in France the minimal penalty rate is set by law, and it's mandatory to put it on every bill, with the payment terms now. It's part of a crackdown on big companies crushing the smaller ones with unreasonable payment times.

I wish they'd do this in Canada.

Re: An Email Thread Between a Developer and Gigster

#210

Earlier quoted context omitted.

Quitting a job is a major, life-changing event for many devs and the question is whether such a clause in the contract is worth the trouble. That said, I disagree strongly with these intellectual property clauses in dev contracts.

If you already have the job and they try to make you sign something like this, don't quit, but say no. You may not be prepared to quit over such a clause, but it's also likely that they're not prepared to fire you over it. They will probably tell you that you must sign it, or else terrible consequences will ensue. If those consequences involve the company, brush it off, because that's not your problem. If they involv…

I've been counseled that an employer cannot compel you to sign a new contract after starting a job, unless there is an incentive to offset any rights/benefits being forfeited. There's a huge gray area in terms of incentive/benefit value, but it's clearly illegal if there are no advantages offered by the new contract and it only benefits the employer.

In other words, it would be clearly illegal for an employer to say simply, "Here's the new employment contract identical to existing but with a new, more aggressive IP ownership clause; sign it or you're fired." Contracts signed under these circumstances have been struck down in court.

However, it would be legal for an employer to say, "Anyone who signs the updated employment contract (with aggressive IP changes) gets free lunches and can work from home 2 days a week." I don't understand the caselaw enough to know what would happen if they provided the incentive and added "or you're fired."

In general, I think the idea is that you have a lot of freedom with new employee agreements, but you cannot just change out an employment agreement on existing employees to strip them of rights.

*IANAL, and it may vary by state.

Post reply on HN