Live data from Hacker News

GitLab Strategy

about.gitlab.com

61–70 of 77 posts

Re: GitLab Strategy

#61
post #35

Earlier quoted context omitted.

What rate do you think is off? For example our rate for an intermediate developer in San Francisco is $160k a year and options. See https://about.gitlab.com/job-families/engineering/backend-en... If you mean we pay local rates please see https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/

I'd highly recommend doing an internal, anonymous, survey to see if employees are happy with their compensation. Literally every GitLab employee I've talked to is extremely unsatisfied and tends to agree with the sentiment about being underpaid relative to other companies for those not in SF, and a very common theme I've heard is being heavily low balled when reaching the offer stage. Somewhat anecdotal but still mor…

Salaries at GitLab were increased (at least for engineers) towards the end of 2018. This meant that at least my salary went from so-so to something I am actually really happy about (this was combined with some other adjustments, such as my experience level), and something that is hard to beat here in The Netherlands.

In other words, the opinion will vary from person to person.

Re: GitLab Strategy

#62

Earlier quoted context omitted.

GitLab employee, this is somewhat of a drawback to how transparent we are about our issues. I know this might seem like I'm just trying to PR spin it, but it's a real phenomenon. We post about any little problem we have, and 99% percent of our Issues are public, so it probably seems like we have a lot of downtime and problems because of how often we talk about them

Unfortunately the perception was earned a few years ago created not by running “more openly” but real user experience and breaking people of that experience over several months is a long uphill battle for GitLab. I’m involved with a large group of Python developers that echos the same feeling, even though generally speaking many of us find GitLab (performance and reliability aside) a better and more comprehensive pro…

That's definitely fair, and warrented. We haven't really had the resources for (relatively) long to put into performance when we were still in early stages. However we've constantly been improving that, to the point where I truly doubt you'd find that we suffer disproportionately from performance issues more than any competitor.

Before I worked here, I was on a team that evaluated different devops tools, and I felt the same apprehension about the uptime. But we eventually chose gitlab, and the only real downtime we experienced was during the 2017 outage. And we liked having the option to switch to self-hosted if it became too much of an issue

Re: GitLab Strategy

#63
post #35

Earlier quoted context omitted.

What rate do you think is off? For example our rate for an intermediate developer in San Francisco is $160k a year and options. See https://about.gitlab.com/job-families/engineering/backend-en... If you mean we pay local rates please see https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/

I'd highly recommend doing an internal, anonymous, survey to see if employees are happy with their compensation. Literally every GitLab employee I've talked to is extremely unsatisfied and tends to agree with the sentiment about being underpaid relative to other companies for those not in SF, and a very common theme I've heard is being heavily low balled when reaching the offer stage. Somewhat anecdotal but still mor…

GitLab employee here, who have you been talking to? Because that has 100% not been my experience working here. I live in a pretty middle-tier area, and I was offered a salary that was pretty much on-par with I was making at the company I worked for locally. My draw to GitLab wasn't the idea that I'd be making a SF level salary, it was (primarily, for me) the ability to work remotely. I couldn't really care less that I'm getting paid less than my colleagues in SF, because the ability to get paid the same amount that I would at a local company while working remotely was already worth it.

Re: GitLab Strategy

#64

Earlier quoted context omitted.

Unfortunately the perception was earned a few years ago created not by running “more openly” but real user experience and breaking people of that experience over several months is a long uphill battle for GitLab. I’m involved with a large group of Python developers that echos the same feeling, even though generally speaking many of us find GitLab (performance and reliability aside) a better and more comprehensive pro…

That's definitely fair, and warrented. We haven't really had the resources for (relatively) long to put into performance when we were still in early stages. However we've constantly been improving that, to the point where I truly doubt you'd find that we suffer disproportionately from performance issues more than any competitor. Before I worked here, I was on a team that evaluated different devops tools, and I felt t…

There’s a pretty vocal group that favors GitLab, I campaigned for it internally at a few companies as well - having so much of the tooling in once place is pretty nice. It’s obvious that GitLab is making quick improvements consistently.

The project boards are better than most others, the CI is phenomenal, and I have noticed the review process is being worked on.

Keep up the good work, we need options in the space!

Re: GitLab Strategy

#65

I feel bad for GitLab. It's better than GitHub in almost every way. And yet GitHub is more popular both in open-source and enterprise. And in enterprise we are usually left with unholy combination of GitHub and JIRA because GitHub project management is a joke and they haven't done anything useful in that space for years. But for some reason pushing for anything other than GitHub is always an uphill battle. And the we…

Things that make me not use gitlab (some of them are super shallow, stupid and relatively unfounded):

1. They used to use Azure, so even though I know Azure is actually an awesome cloud platform, I get this mental image of "Microsoft MVPs" constructing gitlab using VBScript macros because I come from the M$ era.

2. the very public data loss that happened a few years ago, that sounded like a mess, gives the lasting impression that repos are not lasting if they are in gitlab.

3. I never knew gitlab didn't just look like bitbucket, which I hate. In fact, I never would have looked at all if I wasn't writing this response, so I guess to get me they would have to lead with "Nothing like bitbucket!!"

4. I've spent so much time in github, that anything even slightly different pisses me off.

5. The logo looks like firefox porygon edition. GitLab is such a cool name, it could have a better logo, like the word "Git" followed by a chemistry beaker / "potion" thing.

6. The only marketing that would ever work on me would be "has an interface identical to github, does all the things github does, plus these 30 other things". Most of their marketing leads with the "30 other things", so I click away before I bother to read it.

7. If GitLab or anyone tried to do something innovative like writing an extended version of git that adds comments and pull requests to the underlying CLI, and bakes them into the repo itself in some way so we can just stay in CLI world all day, I'd be absolutely onboard, but no one does that for some reason even though that would be a huge differentiator. A similar strategy worked for Heroku if you think about it.

8. Every single open source project I use or contribute to uses github. If GitLab were to, say, add a github integration that lets me work with all the github repos I care about, but using Gitlab's UI, I would be intrigued.

Re: GitLab Strategy

#67
post #3

Inspiring how open Gitlab is in how they run things. Their handbook is a fantastic resource for distributed companies (but also for non-distributed companies). https://about.gitlab.com/handbook/ e.g. here is how they do CEO shadowing: https://about.gitlab.com/handbook/ceo/shadow/

> Inspiring how open Gitlab is in how they run things

Are they profitable? If not, they aren't inspiring me

Re: GitLab Strategy

#68
post #65

I feel bad for GitLab. It's better than GitHub in almost every way. And yet GitHub is more popular both in open-source and enterprise. And in enterprise we are usually left with unholy combination of GitHub and JIRA because GitHub project management is a joke and they haven't done anything useful in that space for years. But for some reason pushing for anything other than GitHub is always an uphill battle. And the we…

Things that make me not use gitlab (some of them are super shallow, stupid and relatively unfounded): 1. They used to use Azure, so even though I know Azure is actually an awesome cloud platform, I get this mental image of "Microsoft MVPs" constructing gitlab using VBScript macros because I come from the M$ era. 2. the very public data loss that happened a few years ago, that sounded like a mess, gives the lasting im…

> 8. Every single open source project I use or contribute to uses github. If GitLab were to, say, add a github integration that lets me work with all the github repos I care about, but using Gitlab's UI, I would be intrigued.

This does exist: https://docs.gitlab.com/ee/user/project/import/github.html#m...

Re: GitLab Strategy

#69
post #67
post #3

Inspiring how open Gitlab is in how they run things. Their handbook is a fantastic resource for distributed companies (but also for non-distributed companies). https://about.gitlab.com/handbook/ e.g. here is how they do CEO shadowing: https://about.gitlab.com/handbook/ceo/shadow/

> Inspiring how open Gitlab is in how they run things Are they profitable? If not, they aren't inspiring me

> Are they profitable?

The goal is to go public by November 18, 2020. You can read all about it here: https://about.gitlab.com/company/strategy/

We have an MR open to mention our long term profitability target for Q4FY25 here: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

Re: GitLab Strategy

#70

Earlier quoted context omitted.

As a person from a third world country, I don't think paying local rates makes sense for an employee. I worked in both Vietnam and Bay Area. The salary difference is ~10x. In Bay Area, I easily save $100K or more per year (earning >~$300K a year). Even earning a top local rates in Vietnam would have a hard time accumulating $100K in savings. I could go back to Vietnam now and earn like $5K USD a month top. Living in…

Is working for Gitlab remotely in Vietnam on a localised salary as good or better than most local job opportunities? If so, isn't it still good for the employees?

> Is working for Gitlab remotely in Vietnam on a localised salary as good or better than most local job opportunities?

I think Gitlab aims to pay top rates on the local market if I'm not wrong.

What I'm saying is that, even with the top rate in Vietnam, it's still small compared to being an average engineer in Bay Area in terms of saving performance.

Post reply on HN