Live data from Hacker News

GitLab acquires Gitter, will open-source the code

venturebeat.com

141–150 of 333 posts

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

#141
post #129

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…

Senior Backend Engineer shows 85-95k in Chicago, which is below average. It shows 45-55k for Fayetteville -- most junior guys/gals start around 75k in Fayetteville at mediocre companies.

Yep, this seems to be a major flaw in their compensation calculator. If you don't live in a high rent, hot bed, you end up with a compensation package that is very (i.e. laughably) low.

A lead (maximum seniority), with high (maximum) experience, in Fayetteville, AR makes less than most junior developers (60k-68k)...

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

#142
post #133

Earlier quoted context omitted.

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...

Definitely not an intern anymore ;) Edit: and yeah, I've read a lot about your company including that link. I understand your approach, it just excludes me.

I must have found a different person, sorry. Can you please email ernst@gitlab.com with your case? If the calculator is so far off we would love to add that data point. The most heard criticism seems to be that for low rent parts of the US the calculator is too low. Before our last change the biggest problem was that for hot cities (Phoenix and Austin) it was too low, we now fixed that.

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

#143

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…

Agreed. I actually had a good time interviewing with them. I'm not sure if it was normal, but it was essentially a 2 week email thread with a few GitLab devs asking me to explain various architectural parts of their system. I had fun diving into their system and getting to know it, including a few of their Go projects like workhorse, but I stopped the process after being told I couldn't ask for more than $60,000 for the position. Cool company, but the pay is just too low.

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

#144

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…

I had an interesting interview with one of their recruiters in which within the first 5 minutes I was asked to agree to compensation below what their calculator (which was a part of the job posting) indicated was their pay scale for my location and that position. I was told my resume wouldn't be passed to an engineering lead until I had (in writing) agreed to the lower salary range. Liiike why even... Edit: Didn't in…

That all sounds kinda weird and sketchy, like the recruiter had a strange hidden motive.

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

#145
post #142

Earlier quoted context omitted.

Definitely not an intern anymore ;) Edit: and yeah, I've read a lot about your company including that link. I understand your approach, it just excludes me.

I must have found a different person, sorry. Can you please email ernst@gitlab.com with your case? If the calculator is so far off we would love to add that data point. The most heard criticism seems to be that for low rent parts of the US the calculator is too low. Before our last change the biggest problem was that for hot cities (Phoenix and Austin) it was too low, we now fixed that.

No, you found the right person, it's just dated information :) I was an intern ~2 years ago.

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

#146
post #85
post #75

Earlier quoted context omitted.

Performance of repos on GitLab.com https://about.gitlab.com/gitlab-com/

We hear you and agree, GitLab.com is too slow. We're working on multiple things to improve it https://gitlab.com/gitlab-com/infrastructure/issues/947 GitLab 9.1 will have lots of performance improvements for database queries. The GItaly team is working hard to move git commands to the fileservers to reduce latency, that will happen in about a month from now.

As a thought for the performance diagnosis part of things, if your network switches have the option to enable NetFlow (also known as IPFIX), it can be extremely useful.

It does need to be paired with something that can capture and display the NetFlow data well. But with that, you can literally see what data is going where in your network, accurate to the byte. And with a good visualisation solution, you have the data historically too, so you can (easily) match things up time wise.

eg a developer writes a bad query which pulls 1/2 the database over the network to the front end server for filtering results there, instead of filtering them in the database. You can see that on the network fairly easily, and let the developer self-educate (if given access to the tools). ;)

As an aside, the gold standard used to be a commercial product called "NetFlow Tracker". It was amazing (fond memories), but the company behind it (Fluke Networks) didn't seem to know anything about software sales. So, it's now discontinued. :(

Hopefully there's a modern version of that somewhere. :)

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

#147

Earlier quoted context omitted.

A cross platform GUI git client that doesn't suck!

This is a pretty great idea. For what I often deal with, the GitHub desktop client is okay (though obviously tied to GitHub), but then I was sad to also realize they don't offer it on Linux. (Maybe they assume Linux nerds don't need GUIs?) I tried Tower when it was in beta for Windows, but the cost is too steep to justify it for me. But it seemed to be a lot more full featured than the GitHub client which isn't good…

> (though obviously tied to GitHub)

You can actually use GitHub Desktop with any repo: https://help.github.com/desktop/faq/articles/do-you-support-... (Although it looks like you have to clone it first?)

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

#148
post #25

next, I hope to see some "content" offer attached to gitlab's ecosystem, for instance a strong collaboration with stackoverflow/OSQA

I guess you can remove OSQA from that list. It's now abandoned, with no new commits and the developers strongly encouraging to use their commercial offering... I'm currently in the processor of migrating an OSQA site to AskBot, which seems currently maintained.

too bad, thanks for the heads up

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

#149

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…

I had an interesting interview with one of their recruiters in which within the first 5 minutes I was asked to agree to compensation below what their calculator (which was a part of the job posting) indicated was their pay scale for my location and that position. I was told my resume wouldn't be passed to an engineering lead until I had (in writing) agreed to the lower salary range. Liiike why even... Edit: Didn't in…

Sorry this happened to you, I’ve brought it up with our PeopleOps team and we’re looking into it. Something like this absolutely shouldn’t be happening.

If you have any more information you can share, it'd be great if you could send it to peopleops at gitlab.com.

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

#150
post #25

next, I hope to see some "content" offer attached to gitlab's ecosystem, for instance a strong collaboration with stackoverflow/OSQA

Gitter has been working on a content system called Topics. https://gitter.im/gitterHQ/topics . It's still in Beta, but Q&A and structured content is definitely something that - in addition to chat - we think is important. (edit: typo)

very interesting, the UI throws me off though, for instance are topics somehow correlated to the channels I have open (i.e. the list on the left)? Can I access Topics from the desktop client?

Looking forward to updates, thanks!

Post reply on HN