181–190 of 333 posts
Earlier quoted context omitted.
"From each according to his ability, to each according to his need" is a bad principle to run both countries and companies.
Why should we run countries like companies?
Finding something that applies to both (Or in this case something that works in neither, which makes it even clearer) is not the same as treating both as requiring the same solutions.
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…
They're not really able to attract much talent. Look through the LinkedIn of some of the GitLab people. A lot of them are very junior (this is the first "real job" for one guy I looked up), and they, rather clearly, have an amateur leadership team, as exhibited by their recent spectacular failures, their underwhelming commentary on remote team management, their naive idealistic implementation of "radical transparency…
Earlier quoted context omitted.
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…
Hi Matt, I am the recruiter at GL, I've reviewed your case, and I wanted to follow up personally. I'd like to address your concern and explain our process. Since the time of your interview, we have changed the process of discussing compensation within the first 15 minutes of a conversation to the end of a phone call. We understand it's uncomfortable and sometimes awkward to talk pay when you've just met someone. Hope…
Earlier quoted context omitted.
No - because, like discord, gitter makes it a point to make privacy very hard to set up. This is fairly deliberate and is the reason why enterprises have a hard time adopting it.
Why not use Mattermost for something like this? We ship it with GitLab Omnibus and it's open core. https://about.mattermost.com/ EDIT: Previously said open source, open core is the correct term.
Earlier quoted context omitted.
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…
Hi Matt, I am the recruiter at GL, I've reviewed your case, and I wanted to follow up personally. I'd like to address your concern and explain our process. Since the time of your interview, we have changed the process of discussing compensation within the first 15 minutes of a conversation to the end of a phone call. We understand it's uncomfortable and sometimes awkward to talk pay when you've just met someone. Hope…
It seems to me the issue is more there was a difference in expectations between what the candidate perceived was their situation and what the recruiter believed. This is of course not uncommon, however from the sounds of it the candidate was not given an opportunity to reason their position. It could be that GitLab is simply not offering competitive renumeration based on what the candidate believed they could achieve in the same market. It could also be that GitLab undervalued the particular skill sets of the candidate. Of course the opposite may also be true.
Clearly there were differences in opinions, however by asking the candidate to sign an agreement to a specific salary based on no discussion is only going to cause issues for everyone. Either the candidate agrees, goes through the interview and decides "it's not worth it, and now there's no flexibility", they disagree and a potentially good candidate is immediately lost or they agree, take the job and feel like they are not being fairly compensated, which can have all sorts of consequences.
This is usually why the discussion happens at the end of an interview process, after the candidate has had the opportunity to demonstrate their skills and experience. Then if there is still a perception of a mismatch this can be reasoned with respect to what has previously been discussed.
> Secondly, we never would ask you to agree to something that is below the calculators suggestion, however your expectations based on Level, Experience, or Location may differ from the recruiter or hiring managers' assessments.
The candidate has clearly stated they were offered less than what the calculator suggested. It was your recruiters opinion that they did not meet the parameters entered into the calculator, however clearly the candidate believed that they did. In this case the recruiter must judge the cause of the disparity through discussion with the candidate and set expectations in terms of the results of this discussion. Again, simply telling a candidate "this is our opinion, you must agree to it" is not going to benefit anyone.
Earlier quoted context omitted.
This just makes me hope you guys buy more things.
Ha! Any suggestions? ;)
Seriously, SublimeText, which is $70 closed-source.
Less seriously, macOS and iLife. I'd be ok to pay €200/year/user for an OS of that quality, as long as it's open-source.
Earlier quoted context omitted.
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…
Hi Matt, I am the recruiter at GL, I've reviewed your case, and I wanted to follow up personally. I'd like to address your concern and explain our process. Since the time of your interview, we have changed the process of discussing compensation within the first 15 minutes of a conversation to the end of a phone call. We understand it's uncomfortable and sometimes awkward to talk pay when you've just met someone. Hope…
Earlier quoted context omitted.
GitHub offers on-prem as well. Of course it's not open source and not potentially free like GitLab https://enterprise.github.com/features
I like Github's UI slightly better (though it's been about a year since I've tried Gitlab)... the recent db issue has me concerned though. That said, I think it's always worth considering using a tool because of their options for the open-source community... github, travis-ci etc have changed the way a lot of people work. GitLab might be what I reach for for self-hosting, but more likely to try the community/open edi…
They did a manual Backup before meddling with stuff so they only lost data from a really small timeframe.
CI downtime, on the other hand, is troublesome. I love using Gitlab CI and it didn't take me more than a few minutes to manually deploy what I had to, but I decided I need most of my CI to be controlled by me.
The end result is a simple refactor of my test and deploy specs to their own rake tasks (Could be Bash scriots or whatever) and I'll have Gitlab run a simple gle command, if it goes down I run the command manually...
Now some eventual downtime is not such a deal breaker anymore, and I continue having private repos and CI (Awesome CI) for even the smallest (And private) projects I work on... Not a bad deal if I do say so myself.
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'm also turned off by remote companies that do the same. I work remote and moved to a very low-cost area. That doesn't mean I want a massive pay cut.
But yeah, the outcome, remoters from Cheaptown effectively subsidizing their coworkers from Glitter City is incredibly ugly. One should at least hope that the decisionmaking processes at the employer do not completely isolate the one deciding on a hire from the cost difference, so that flyover guy could at least enjoy an increased chance of getting the job.
Earlier quoted context omitted.
I'm very glad to hear that. What are the reasons that you think will encourage others?
The biggest thing I think would encourage more projects to move is improving discoverability. On Github, I can very easily search for new projects to contribute to, and their Explore page [1] is very nice. Gitlab's, on the other hand, doesn't seem to have a way to browse by category like Github. For everything else, I like Gitlab a lot -- it seems to have the best integration of tools of any code host. [1]: https://g…