GitLab acquires Gitter, will open-source the code • Hacker News Board

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

#331

Post by franksli » Mon, Mar 27, 2017, 4:43 PM UTC

nico wrote: post #247

Up until this week I was in love with Gitlab. We've been using it at work for over a year as our main repo, code review tool and CI (tried self-hosted first, then moved to gitlab.com). However, the service (gitlab.com) is constantly having issues, most of them not reported on their status page or on their twitter status account. For the last week it's been practically unusable, to the point where our whole dev team c…

You mentioned that you tried and failed to move onto the AWS developer tools. What problems or issues did you run into?

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

#332

Post by jospoortvliet » Mon, Mar 27, 2017, 6:16 PM UTC

developer2 wrote: post #282

Perihelion wrote: post #281

Earlier quoted context omitted.

Since the first part of your comment is addressed to Sasha I'll let her reply to it, but to address the second part: There are multiple people involved in the hiring process here at GitLab, specifically several people who handle phone screens and resumes. The responsibility of vetting doesn't rest solely on one person and is actually a pretty collaborative process in my experience. As an example, I was able to vet ev…

With all due respect, the parent to my comment - an apparent employee at GitLab - said "I am the recruiter at GL". " The recruiter", not " a recruiter" How else is that to be interpreted? With whom does the candidate discuss compensation? This one single recruiter, or the manager of the team with whom the employee would be placed? Why does GitLab have a "recruiter", rather than an "HR employee" or "hiring manager"? T…

I'd LOVE to hear what red flags are in the comment from the recruiter or the other person - whom I guess is a manager. I've re-read it a few times but I see nothing but reasonableness. Then again, I'm neither a developer myself (does that make a difference) nor a recruiter...

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

#333

Post by jospoortvliet » Mon, Mar 27, 2017, 6:42 PM UTC

stephenr wrote: post #330

storafrid wrote: post #329

Earlier quoted context omitted.

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.

True. Still, I think most companies will take cost of living in the area where the potential employee lives into account. When thinking about it it seems odd, indeed. I guess it is kind of normal and expected. But entirely rational it is not.