Live data from Hacker News

GitLab Direction

about.gitlab.com

31–40 of 137 posts

Re: GitLab Direction

#31
post #3

GitLab should, frankly, focus on performance/ux/bug-fix releases every other release. And probably for the next 2-3 releases to get some of the warts under control. This constant push for project management features, frankly, is at the expense of the core product. I'd rather use a combination of GitHub and JIRA over Gitlab.

You could look at other products too.

Gitea has been very close to core Github Features IMO and Gogs (the original fork) has some neat other features separate from Github.

There is also Bitbucket which does integrate neatly into JIRA in my experience.

There is a lot of choice, Gitlab is great if you need a "everything in one box" solution for every problem or demand you might encounter during development.

Other Git-Webapps solve other problems or problem spaces.

Re: GitLab Direction

#32
post #5

GitLab is like the average kid in class that everybody makes fun of for constantly asking questions, but the joke's on them because "a little bit of slope makes up for a lot of y-intercept." While GitLab may have warts, I feel that they're very earnestly working to make the product better, bit by bit, day by day, and will one day surpass GitHub.

Thanks! Incremental progress in the form of iteration is one of our core values https://about.gitlab.com/handbook/values/#iteration

I have some questions to ask of you.

1. Why does gitlab have so many tiers? It would be better if you guys could repackage the features into fewer categories.

2. Why is the Gitlab UI so ugly? IMO, bitbucket and github are leaps and bounds ahead of you guys when it comes to design.

3. Can we get a dark mode for us night owls?

4. Finally, the morality question, You guys proudly associate yourselves with open-source and get help from loads of opensource devs, yet you greedily restrict simple features like epics, burndown charts, roadmaps, configurable issue boards etc. from the core/free categories. Looks like your key core goal is to make money... how are you any different from microsoft or google?

Re: GitLab Direction

#33
post #5

Earlier quoted context omitted.

Thanks! Incremental progress in the form of iteration is one of our core values https://about.gitlab.com/handbook/values/#iteration

I have some questions to ask of you. 1. Why does gitlab have so many tiers? It would be better if you guys could repackage the features into fewer categories. 2. Why is the Gitlab UI so ugly? IMO, bitbucket and github are leaps and bounds ahead of you guys when it comes to design. 3. Can we get a dark mode for us night owls? 4. Finally, the morality question, You guys proudly associate yourselves with open-source and…

Asking questions antagonistically rarely elicits a response.

Re: GitLab Direction

#34
A few years ago I really wanted to join GitHub as a software engineer. I was living in San Francisco and visited their office for some events, and I thought it would be an awesome place to work. I tried reaching out to a few people who worked there, but I could never get my foot in the door.

There were a lot of things I would have loved to build at GitHub, and they were all the same things that GitLab is doing now. I felt that there was so much potential to build things like CI, DevOps, and eventually a PaaS to compete with Heroku. I really think they should have acquired something like TravisCI or CircleCI and made that part of their platform, but it seems like they haven't really done anything significant in the last 5 years.

I'm a very happy user of GitLab now, and the product is awesome. But I don't think I would ever join the company. First of all, they don't pay competitive salaries for remote workers (cost-of-living adjustments). I also don't think they have a very good company culture, and to be honest, it still feels a bit sketchy that they ripped off GitHub and undercut them on pricing. But I'm sure I'll get over that eventually.

Re: GitLab Direction

#35

A few years ago I really wanted to join GitHub as a software engineer. I was living in San Francisco and visited their office for some events, and I thought it would be an awesome place to work. I tried reaching out to a few people who worked there, but I could never get my foot in the door. There were a lot of things I would have loved to build at GitHub, and they were all the same things that GitLab is doing now. I…

Could you elaborate about the salaries for remote workers? I'm a frontend developer in southern Europe and I'd love to work for Gitlab because I love the product.

Re: GitLab Direction

#36
People tends to compare GitLab to Github, to me it seems more they compete with VSTS or Atlassian.

CI, project management (epics and roadmaps), monitoring...

Github introduces really few features but seems to make them right, or really limited, but never “bad”.

Gitlab on the opposite, works more with super-fast and open iterations, without hesitating to roll-back if it just doesn’t work.

Re: GitLab Direction

#37
post #35

A few years ago I really wanted to join GitHub as a software engineer. I was living in San Francisco and visited their office for some events, and I thought it would be an awesome place to work. I tried reaching out to a few people who worked there, but I could never get my foot in the door. There were a lot of things I would have loved to build at GitHub, and they were all the same things that GitLab is doing now. I…

Could you elaborate about the salaries for remote workers? I'm a frontend developer in southern Europe and I'd love to work for Gitlab because I love the product.

You can read everything about it here: https://about.gitlab.com/handbook/people-operations/global-c...

They once had a online calculator where you put in your location (basically only SF, non-SF US, and outside US) and position but apparently they switched to another model that includes employee performance and other factors.

Re: GitLab Direction

#38

A few years ago I really wanted to join GitHub as a software engineer. I was living in San Francisco and visited their office for some events, and I thought it would be an awesome place to work. I tried reaching out to a few people who worked there, but I could never get my foot in the door. There were a lot of things I would have loved to build at GitHub, and they were all the same things that GitLab is doing now. I…

I could not agree more with you that Github should have acquired a CI tool and worked on PaaS. Big missed opportunity for them and for their customers. I do expect Azure to become well supported on Github at some point, but Github had the opportunity to build something truly awesome and cloud vendor neutral. Very sad and weird they sold out, but it is theoretically possible Microsoft will do a better job moving Github forward.

Gitlab seems fine but it's just not as smooth / good looking as Github. Github is one of the best websites ever made in my opinion. I do like the fact Gitlab is more aggressive in adding CI features. Maybe I'll check them out...

Re: GitLab Direction

#39
post #35

A few years ago I really wanted to join GitHub as a software engineer. I was living in San Francisco and visited their office for some events, and I thought it would be an awesome place to work. I tried reaching out to a few people who worked there, but I could never get my foot in the door. There were a lot of things I would have loved to build at GitHub, and they were all the same things that GitLab is doing now. I…

Could you elaborate about the salaries for remote workers? I'm a frontend developer in southern Europe and I'd love to work for Gitlab because I love the product.

Example: https://about.gitlab.com/job-families/engineering/developer/...

Full details are here: https://about.gitlab.com/handbook/people-operations/global-c...

Re: GitLab Direction

#40
post #35

A few years ago I really wanted to join GitHub as a software engineer. I was living in San Francisco and visited their office for some events, and I thought it would be an awesome place to work. I tried reaching out to a few people who worked there, but I could never get my foot in the door. There were a lot of things I would have loved to build at GitHub, and they were all the same things that GitLab is doing now. I…

Could you elaborate about the salaries for remote workers? I'm a frontend developer in southern Europe and I'd love to work for Gitlab because I love the product.

I don't have any first-hand experience, and I'm sure there are exceptions. I've heard that GitLab will pay around $80k for a remote software engineer in a country with a low cost-of-living. That engineer could be earning $150k-$250k at a different company (e.g. Basecamp, GitHub, etc.)

I realize that $80k is a lot of money for Europe/UK/Asia/South America/rest of the US. But if you're a top engineer, you could double or triple your income by working for a different company (or as a consultant.)

I should mention that I don't have any problem with GitLab's compensation, and I think it's actually pretty fair. But fair doesn't really matter. A top engineer will just go to the company that pays more. I'm sure GitLab has a lot of great engineers, but just based on their compensation, I'm pretty sure it's not one of the best engineering teams in the world.

Here's a few references/articles/job boards:

* https://news.ycombinator.com/item?id=10924957

* https://dev.to/sam_ferree/why-i-think-cost-of-living-pay-for... (see some of the comments in there)

* https://m.signalvnoise.com/basecamp-doesnt-employ-anyone-in-...

* https://weworkremotely.com

* https://remoteok.io

Post reply on HN