News for hackers. Stuff that matters.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by bobsam on Saturday April 22, 2017 @04:18PM (#14174519)
For the love of God, add some social functions to gitlab and bitbucket!! And get people to use them!

A recruiter just toss out my application to my dream job since other applicants had "more stars on their git".

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by orf on Saturday April 22, 2017 @04:36PM (#14174615)
Then that recruiter is utterly worthless and you should contact the tech lead a at the companyuestion and let them know.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by bobsam on Sunday April 23, 2017 @04:57AM (#14177236)
The recruiter was an in-house employee. This was her only job.

And the company is not your average IT sweatshop (big very sucessful company, names starts with an A).

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by orf on Sunday April 23, 2017 @05:27AM (#14177333)
It doesn't matter, you should still contact someone technical about it, especially if she actualy said "more stars on their git". Put that quote in your message!

They might be glad to know she's filtering candidates based on that, because they can talk to her about it. It could lead to you getting an interview.

What's the worst that could happen?

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by cthalupa on Sunday April 23, 2017 @02:31PM (#14179578)
Having worked at very big successful companies and being heavily involved in the hiring process: We know recruiters don't always get it right.

We need them, because creating and maintaining hiring pipelines is a full-time job, but we know (and the recruiters should also know!) that they're working on a best-understanding of the job they're recruiting for, and that best-understanding is not a complete understanding, since they don't do that job. It might have been a miss on their understanding of an explanation, it might have been a miss on whoever communicated the job requirements to them. But if you have a contact outside of the recruiter, you should 100% reach out.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by Sir_Substance on Saturday April 22, 2017 @05:46PM (#14175001)
Oh Jesus, please don't fill my professional tool with social gunk. What is this, a highschool?

As a side note, recruiters are not on your side, they're on their own side. Don't rely on them for anything, least of all securing your dream job.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by dominotw on Saturday April 22, 2017 @06:29PM (#14175213)
Its not gunk. Stars is the first thing I check for social proof before using a project in my work. Higher stars is almost a guarantee of better quality and momentum.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by scrollaway on Saturday April 22, 2017 @06:32PM (#14175229)
Higher star count is a guarantee of more visibility, that doesn't mean anything quality-wise and it doesn't mean much momentum-wise.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by dominotw on Saturday April 22, 2017 @06:42PM (#14175269)
Curious if have any examples to back up your point? I've never seen a project with high start and low momentum, I don't mean dead projects ,obviously.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by Sir_Substance on Saturday April 22, 2017 @07:12PM (#14175415)
>I've never seen a project with high start and low momentum, I don't mean dead projects ,obviously.

"I've never seen this thing, except in this obvious and common case where it happens all the time, but other than that, literally never".

Mate :/

In general, my first step in deciding whether projects are good is to google "<project name> review", and see what other developers and sysadmins have experienced with it.

I have often found that a 5 stars system contains inadequate information density to provide me with guidance on the suitability of one project over another with respect to integrating it into my companies tech stack, although I appreciate that's a personal standpoint and that you may disagree.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by stonogo on Saturday April 22, 2017 @07:45PM (#14175553)
Ah yes, you'd like examples, with the exception of the largest class of examples. Well played.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by dozzie on Saturday April 22, 2017 @06:43PM (#14175276)
I don't. I look at the documentation and at the source code. If it isn't up to par, it's junk regardless of how many stars it has.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by dominotw on Saturday April 22, 2017 @06:49PM (#14175309)
Yea ofcourse. I am just saying that stars == good correlation is really strong.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by bsder on Saturday April 22, 2017 @07:35PM (#14175508)
And we're saying, "No, it's not."

A project with lots of stars and rare commits is almost never better than one with a less stars but low-grade continuous activity.

"Date of last commit" is probably FAR higher than any "social" bullshit in terms of quality.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by Sir_Substance on Saturday April 22, 2017 @07:48PM (#14175570)
>"Date of last commit" is probably FAR higher than any "social" bullshit in terms of quality.

That's the first thing I look at when I arrive on a github page, always.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by dominotw on Saturday April 22, 2017 @07:49PM (#14175575)
I am obviously not talking about dead projects.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by stonogo on Saturday April 22, 2017 @05:28PM (#14174911)
Sure, don't treat the symptom, just demand everyone contract the disease.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by harperlee on Saturday April 22, 2017 @05:47PM (#14175005)
...or perhaps let's take care of the patients while we develop a cure? If it is a fact that recruiters look at github presence, ignoring that fact is harmful for people only sharing work on gitlab, which in turn hurts gitlab.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by Sir_Substance on Saturday April 22, 2017 @05:54PM (#14175041)
Much like the value of the US dollar, what you're saying is only real if enough people choose to believe it.

Buying into and supporting this behavior is just digging an increasingly deep hole. If you don't want github commits (and an agreement to the github terms of use) to be a mandatory part of all developers lives and CVs, then simply continue being an excellent developer without making github commits that you don't want to make.

We're in an important stage of github adoption at the moment. Some recruiters think it's a critical signaling mechanism. If we buy into that, they will seem to be correct, and the companies they recruit for will allow them to continue with their methodology. Soon, they will become correct because all career-oriented developers will feel compelled to work on github based open source projects to the exclusion of other open source projects, even if they don't actually give a shit about the projects they are working on.

However, if the companies they recruit for see high quality developers going to the competition because their recruiters are dismissing people out of hand for not being on github, those companies will eventually tell their recruiters to pull their fingers out and do some proper legwork.

The correct approach is to starve out this behavior while the cost of doing so is relatively low, not buy into it.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by CharlesW on Saturday April 22, 2017 @06:53PM (#14175331)
> The correct approach is to starve out this behavior while the cost of doing so is relatively low...

The cost is pretty high to bobsam, who didn't have a chance to interview for his dream job.

Not "playing the game" only works if all good developers stop using GitHub, no?

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by Sir_Substance on Saturday April 22, 2017 @07:02PM (#14175371)
>The cost is pretty high to bobsam, who didn't have a chance to interview for his dream job.

As I said to him in my directly reply to his post, acquiring an interview for ones dream job is a task best not left to others.

In relation to our specific discussion, ultimately one developers loss of their dream job is not a huge cost. We are looking down the barrel of a future where github can pick and choose who is employable and who is not, and therefore who makes key technical decisions at major vendors and who does not, by banning github accounts for political reasons. That has knock on effects for things like key standards decisions, and that's when the costs of refusing to conform start mounting. I basically don't trust companies with that kind of power.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by elmerland on Saturday April 22, 2017 @10:25PM (#14176114)
If I were interviewing you I would care a lot more about the job you were hired to do than about any side-projects that are not part of your job.

I'm not a fan of recruiters incentivizing "required" side-work. That's the time you dedicate to all other important things in your life (which could be a side project, but it is not in most cases)

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by bobsam on Sunday April 23, 2017 @05:11AM (#14177285)
The were two posts on Reddit about placing fakes ad for a job to see how the competition was. They were both blown away with the quality of the applications, in particular people working on a lot of important side projects.

I can only assume recruiters very much consider this when they don't know anything else about you.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by elmerland on Tuesday April 25, 2017 @12:11AM (#14190709)
All things being equal if all you know is their side projects that makes sense. Normally you would have their resume which includes work done at their job. I get how it's so tempting to look at people's side projects as a measure of proficiency. I just don't think it's fair to judge people by their ability to spend hours working outside of work.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by tpetry on Sunday April 23, 2017 @04:26PM (#14180281)
Do you still have the reddit articles? Sounds interesting.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by mrmondo on Saturday April 22, 2017 @07:37PM (#14175521)
Have you actually logged a feature request for this?

*Edit: Thanks for the downvote, but seriously - have you? If you haven't - It's more constructive to do that so civilised production direction and development discussion may take place in the official centralised forum rather than having outbursts on HN.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by dominotw on Saturday April 22, 2017 @06:27PM (#14175201)
Can you tell us which company this is. I have lots of stars and i am looking for a job.
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by j_s on Saturday April 22, 2017 @10:29PM (#14176134)
A public indication of the popularity of each project is a great way to winnow down the number of valid options.

They could whip something together just from their server-side analytics so it was more honest rather than a popularity contest.

Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by sytse on Saturday April 22, 2017 @07:56PM (#14175601)
What feature would you like to see first?
Re:GitLab 9.1 Released with Service Desk, Canary Deployments... by bobsam on Sunday April 23, 2017 @04:52AM (#14177220)
The ability to find popular devs and popular projects. Also a way to find similar projects or projects about an specific topic.

Maybe some of these are already implemented and we mostly need to get the devs to use them more frequently?