Live data from Hacker News

An Email Thread Between a Developer and Gigster

andychase.me

11–20 of 271 posts

Re: An Email Thread Between a Developer and Gigster

#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 end of the project and decided to consult our workplace to find out how strict they were on this. The conversation with HR went something like this:

> Us: Oh hey there, can you clarify clauses X/Y/Z in our contracts regarding ownership of code. We are working on a project we are planning on monetising at some stage and we need to know if the company is going to do anything about this. Our project has no conflicts of interest and we haven't stolen any IP of the company.

> HR: Oh... We've never had a question like this before... We can't say exactly. We'd have to consult our lawyers.

> Us: Cool - can you consult them and let us know what they say, please?

> HR: Sorry, we can't consult them as they charge by the minute and it's too expensive to warrant a conversation with them.

> Us: So... you're not going to answer our question.

> HR: Exactly. You'll have to do it at your own risk.

Re: An Email Thread Between a Developer and Gigster

#12
So, Gigster expects developers to sign an overly broad contract and yet they're not willing to answer any questions about that contract???

At best, that is a terrible way to treat developers. At worst, they just effectively guaranteed that only the most ignorant developers sign up with them. After all, the first thing I learned was to ask questions about every single ambiguous term in a contract.

If this doesn't change, I don't see anything good in Gigster's future. Smart talent will leave, jobs will dry up and the whole platform will disappear.

Re: An Email Thread Between a Developer and Gigster

#13
post #2

This is especially troubling since it appears that Gigster is directly aimed at software development, not generally connecting people with contract jobs. I wonder if they even have a lawyer familiar with software development on-board.

>I wonder if they even have a lawyer familiar with software development on-board.

I imagine they do, specifically so that they can own their developers to the greatest extent possible - see Uber etc. (and I am referring to Uber drivers, not developers.)

Re: An Email Thread Between a Developer and Gigster

#14

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.

It's true. Because with tens of thousands of employed engineers sometimes employees actually go "hey, I can improve this open source ad network search engine whose mission statement is to take business from google", and that is why they can't have nice things without getting a quick approval first.

Re: An Email Thread Between a Developer and Gigster

#16

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.

My company has a policy of allowing you to work on open source after getting approval from legal. It also seems that all emails to legal are routed to /dev/null . I wouldn't be surprised if other companies act the same way.

Re: An Email Thread Between a Developer and Gigster

#17

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.

Would it be possible to link that discussion?

sure no problem with that. Learned it here: https://github.com/tekezo/Karabiner/issues/660#issuecomment-... then googled about it (what irony) and then found out this is common practice at big tech companies in USA.

Re: An Email Thread Between a Developer and Gigster

#18
I interviewed to be a Gigster about a year and a half ago, and was accepted, but the more I considered it and saw how gigs were distributed (at that time mostly via Slack messages) I got a bad feeling, like I was a dog in a pack, fighting over meat scraps. It was then I realized the gig economy is not all sunshine and roses. All that to say, this doesn't surprise me, that Gigster doesn't have its workers best interest at heart, anymore than Uber has its drivers best interest at heart.

Re: An Email Thread Between a Developer and Gigster

#19

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.

This is obviously untrue, as evidenced by the multitude of people here on HN and at PyCon and other conferences who work at Google and routinely work on open source projects.

edit: I see - I initially misread parent. Yes, some Googlers are work-for-hire.

Re: An Email Thread Between a Developer and Gigster

#20

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.

Yes, basically. For open-source projects where google retains the copyright you don't need special permission (it is part of your job, basically). For personal stuff or where you wish to retain the copyright then you will need it assigned to you.
Post reply on HN