3 ms·
> What I'm most surprised by in this thread is the toxicness. As of right now there are only two threads that I can see, one that is slamming Gitlab's salaries
by koolba 9y ago
> What I'm most surprised by in this thread is the toxicness. As of right now there are only two threads that I can see, one that is slamming Gitlab's salaries and one that is slamming their reliability.
After many year on the internet, it's not that surprising. It's best summed up as, "Haters gonna hate.".
The jabs at the cloud offerring's reliability are valid. That includes both uptime and the horrendous data loss event they had earlier this year. I don't recall anything major after though not knowing about internals, can't tell if they learned from it or have just gotten lucky.
As a CE user I love GitLab. It does what it says on the tin and for the most part I don't have to think about it. The UI changes every other release are bit haphazard but not enough for me to truly care.
I've always thought that slamming their open comp policy is hilarious. They're one of the most open companies about how they handle comp and the result is they get insulted for it. I'm not saying I agree with the formulas (in particular the non-NYC COLA adjustments are out of whack) or the general approach, but to say they're worse than the voodoo guesswork that goes into figuring out how much a company is going to pay you is disingenuous. Especially if it's after a number of interviews only to find out they're going to low ball you.
At least in GitLab's case I know, at the current comp levels, I'd never work there or even interview there. And that's beyond fair for the worker. Plus it seems to be working fine because they've got a bunch of people that are happy to work there.
- matteeyah 9y ago> The jabs at the cloud offerring's reliability are valid. That includes both uptime and the horrendous data loss event they had earlier this year. I don't recall anything major after though not knowing about internals, can't tell if they learned from it or have just gotten lucky. We have a very detailed post-mortem of the database incident we had in January, along with a list of precautions (every one with an issue) we took to make sure it doesn't happen again in https://about.gitlab.com/2017/02/10/postmortem-of-database-outage-of-january-31/ https://about.gitlab.com/2017/02/10/postmortem-of-database-o... We're also actively working on improving our reliability; you can check up on all ongoing efforts in https://gitlab.com/gitlab-com/infrastructure/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=availability https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...
- StavrosK 9y agoI regularly slam them about their reliability on Twitter, but I keep using them, because I love how integrated the product is. I really have no complaints about either gitlab.com or the EE version, which I pushed that we migrate to at work. If they can reduce the service problems, it'll be a great service.
- naturalgradient 9y agoA possible interpretation is that Gitlab chooses to not pay for top-tier distributed systems talent and will thus never reach the service quality they want. Everything comes at a price.
- dxhdr 9y ago> I've always thought that slamming their open comp policy is hilarious. They're one of the most open companies about how they handle comp and the result is they get insulted for it. Well, they openly discriminate based on zipcode. It's their right as a business but it runs counter to the internet age remote-work utopia everyone wants. Kudos to them for even running a remote-work business, though. We need more of them.
- unethical_ban 9y agoIs there any company with a household name that doesn't? That I could get paid SF wages for a dev job in Biloxi?