Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab acquires Gitter, will open-source the code

venturebeat.com

Post reply on HN
Print view View original

321–330 of 333 posts

Re: GitLab acquires Gitter, will open-source the code

#321

Post by anonymous_green »

sytse wrote: post #133
hamandcheese wrote: post #110

Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area. I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalize…

Mmm, that is pretty far off. If I understand correctly you're a developer intern in Orlando. In most countries interns are paid less than juniors. Maybe that is not the case in the US currently? BTW Our compensation principles can be found at https://about.gitlab.com/handbook/people-operations/global-c...

Seriously? BTW! I just checked the calculator again and the time I was offered a job, there was no calculator then. The calculator pretty much offers the same amount that I asked for but still Gitlab decided to waste by time by saying we expect to pay 70-80k max. The range is clearly 115-120k and I don't think you understand the concept of remote teams when this range can be quite different than US which I explained to your HR as well.

Re: GitLab acquires Gitter, will open-source the code

#322

Post by jobvandervoort »

therealmarv wrote: post #320
jobvandervoort wrote: post #114

Earlier quoted context omitted.

You can find some public monitoring regarding CI on GitLab.com here [0]. I agree that we should have some status on CI as well, made an issue [1]. [0]: http://monitor.gitlab.net/dashboard/db/ci [1]: https://gitlab.com/gitlab-com/infrastructure/issues/1360

Wow that gitlab monitor on [0] looks really great. Thanks! Can I ask which software that is? :)

It's Grafana [0], backed by Prometheus [1].

[0]: https://grafana.com/

[1]: https://prometheus.io/

Re: GitLab acquires Gitter, will open-source the code

#323

Post by moosingin3space »

sudoscript wrote: post #190
moosingin3space wrote: post #154

Earlier quoted context omitted.

The biggest thing I think would encourage more projects to move is improving discoverability. On Github, I can very easily search for new projects to contribute to, and their Explore page [1] is very nice. Gitlab's, on the other hand, doesn't seem to have a way to browse by category like Github. For everything else, I like Gitlab a lot -- it seems to have the best integration of tools of any code host. [1]: https://g…

I completely agree. Actually, I think Github could do a better job with discovery too. The Explore page is a decent start, but why don't I get personalized recommendations for new projects?

Yes, that would be nice -- look at the languages my code is written in or the categories my code is, it makes sense to suggest new projects based on that.

Re: GitLab acquires Gitter, will open-source the code

#324

Post by developer2 »

bartread wrote: post #317
developer2 wrote: post #279

Earlier quoted context omitted.

Holy crap, you've just done your company - or if you are an external recruiter, your client - a huge disservice by posting this reply. You've done nothing to assuage future candidates' concerns. You've merely confirmed that your compensation offers, and likely the entire hiring process, is driven by undesirable corporate metrics. This makes GitLab sounds seem like a company that only knows how to regurgitate HR 101 t…

Speaking from the candidate's perspective, I tend to avoid companies where money is discussed upfront. I want to be able to demonstrate the value I can add, and then have a negotiation about remuneration based on that value. Bluntly, yes, it does put the candidate in a much stronger negotiating position but, hey, if you really want to hire good people then I'm afraid it's hard cheese. Conversely talking about remuner…

The discussion of compensation is an extremely simple concept: you wait for the candidate to bring it up, and you discuss it only at that point in time. The interviewer should never bring up compensation before the candidate does, unless the potential employee is so shy that they are waiting for the employer to do so first. The moment an employer tries to pre-emptively bring up the topic of money before it makes sense, it shows their true colors - they care far too much about the money rather than the talent they are hiring.

It really is that basic. When the company cares more about the money than what the employee can bring, they've shown their company cares more about their internal politics then they do about their future success. Simple as that.

Re: GitLab acquires Gitter, will open-source the code

#325

Post by storafrid »

stephenr wrote: post #309
59nadir wrote: post #303

Earlier quoted context omitted.

I think he simply read that as "Do they pay less (for living)?" and not that they pay less for software. No one could seriously think that you pay less for software based on your location, compared to other people in the same region/country.

S/He quoted the whole thing: > > Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York? > Yes?

Yes, he did, unfortunately. Gasp. The humanity. Now get over it. You understand that he meant paying less for a flat, not for an OS. So stop pretending and go on with replying that you still think it's wrong to base the compensation on the location's living expenses, for whatever other new reason that you now need to come up with.

Re: GitLab acquires Gitter, will open-source the code

#326

Post by stephenr »

storafrid wrote: post #325
stephenr wrote: post #309

Earlier quoted context omitted.

S/He quoted the whole thing: > > Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York? > Yes?

Yes, he did, unfortunately. Gasp. The humanity. Now get over it. You understand that he meant paying less for a flat, not for an OS. So stop pretending and go on with replying that you still think it's wrong to base the compensation on the location's living expenses, for whatever other new reason that you now need to come up with.

> You understand that he meant paying less for a flat

No. If I understood that, I wouldn't have replied as I did, would I now?

> go on with replying that you still think it's wrong to base the compensation on the location's living expenses

But why is it a location's living expenses? If a company is paying people to work remotely, location should have zero impact on remuneration: they aren't asking you to live anywhere specific, so there is no business reason to use location as a cost factor.

Re: GitLab acquires Gitter, will open-source the code

#327

Post by storafrid »

stephenr wrote: post #326
storafrid wrote: post #325

Earlier quoted context omitted.

Yes, he did, unfortunately. Gasp. The humanity. Now get over it. You understand that he meant paying less for a flat, not for an OS. So stop pretending and go on with replying that you still think it's wrong to base the compensation on the location's living expenses, for whatever other new reason that you now need to come up with.

> You understand that he meant paying less for a flat No. If I understood that, I wouldn't have replied as I did, would I now? > go on with replying that you still think it's wrong to base the compensation on the location's living expenses But why is it a location 's living expenses? If a company is paying people to work remotely, location should have zero impact on remuneration: they aren't asking you to live anywhe…

I'm not hearing a counter-argument. The company needs to get good people to work for them. And this is a way of getting someone from a high-cost location to work for them. If the location's higher living expenses aren't covered for, the person would be unable to take the job. I don't know if you mean that the company should adjust their lowest pay according to the world's most expensive location, but that would probably not sustain the business.

Re: GitLab acquires Gitter, will open-source the code

#328

Post by stephenr »

storafrid wrote: post #327
stephenr wrote: post #326

Earlier quoted context omitted.

> You understand that he meant paying less for a flat No. If I understood that, I wouldn't have replied as I did, would I now? > go on with replying that you still think it's wrong to base the compensation on the location's living expenses But why is it a location 's living expenses? If a company is paying people to work remotely, location should have zero impact on remuneration: they aren't asking you to live anywhe…

I'm not hearing a counter-argument. The company needs to get good people to work for them. And this is a way of getting someone from a high-cost location to work for them. If the location's higher living expenses aren't covered for, the person would be unable to take the job. I don't know if you mean that the company should adjust their lowest pay according to the world's most expensive location, but that would proba…

> this is a way of getting someone from a high-cost location to work for them

Why is that a requirement? Do you somehow think the Bay Area has a monopoly on good developers?

Re: GitLab acquires Gitter, will open-source the code

#329

Post by storafrid »

stephenr wrote: post #328
storafrid wrote: post #327

Earlier quoted context omitted.

I'm not hearing a counter-argument. The company needs to get good people to work for them. And this is a way of getting someone from a high-cost location to work for them. If the location's higher living expenses aren't covered for, the person would be unable to take the job. I don't know if you mean that the company should adjust their lowest pay according to the world's most expensive location, but that would proba…

> this is a way of getting someone from a high-cost location to work for them Why is that a requirement? Do you somehow think the Bay Area has a monopoly on good developers?

If the company finds a person that they want to recruit, and that person happen to live in a high-cost location, they will need to pay up in order for the recruitment to happen. The only alternative would be to offer relocation to a lower-cost region. It doesn't have anything to do with any requirement. It's just a result from the way the world works.

Re: GitLab acquires Gitter, will open-source the code

#330

Post by stephenr »

storafrid wrote: post #329
stephenr wrote: post #328

Earlier quoted context omitted.

> this is a way of getting someone from a high-cost location to work for them Why is that a requirement? Do you somehow think the Bay Area has a monopoly on good developers?

If the company finds a person that they want to recruit, and that person happen to live in a high-cost location, they will need to pay up in order for the recruitment to happen. The only alternative would be to offer relocation to a lower-cost region. It doesn't have anything to do with any requirement. It's just a result from the way the world works.

Given that most people aren't hired that way, it's more like:

If a person wants to work for the company but their offered salary isn't high enough to sustain a high cost of living environment, the person will need to either move or find another job.

The company has literally the entire world to find staff - that's the whole point of remote workers.

Post reply on HN