51–60 of 135 posts
I disagree with this article completely. I'm a woman and a software developer and I think my Github is very valuable as a portfolio to me. Before I used Github, if I wanted some of my code to get shown off, I would make a blog post about it and call out specific chunks while linking to a ZIP of the whole thing. If a potential employer wanted to see samples of my code, they'd have to find my blog and dig through its a…
"OSS as a hiring filter biases your selection process toward white men"... not sure what to say. But I do find it funny that they don't think that Github should be used as a resumé but their "conferencing", tweets, books about diversifying and podcasts should do. Talkers or Makers? I write OSS on my free time because I feel like other alternatives might not be good enough. I spend a couple of hours in the morning, we…
OSS as a hiring filter biases your selection process toward people who are either paid to do it at their current job, or who have few enough prior commitments in the rest of their life to be able to afford to do it outside of work.
I'm not sure whether it biases towards white men or not, but I'm pretty sure it biases towards younger people and against people who are in enterprisey companies (or who work on private contracts).
Earlier quoted context omitted.
Yes, all the complaints about how you can't tell a story with your github profile seems to completely ignore gh-pages, a phenomenal service that does let you tell a story. Maybe your github profile isn't a good portfolio by default, but it's an excellent service for creating your portfolio. On top of that, even a poor github profile provides more signal than most CVs I've read.
> Yes, all the complaints about how you can't tell a story with your github profile seems to completely ignore gh-pages Yeah... that's not what they mean, and you know it.
I just threw that together quickly a while back and haven't updated it, but github whould make a fantastic site for a portfolio.
Earlier quoted context omitted.
You either missed the point, or do not think it's a problem. > determine if a candidate cares enough to code on their own Which he is arguing that you are not a bad developer for doing other things outside of work. The vast majority of people need to not code to regenerate. I can use myself as anecdotal evidence: I'm the goto guy when it's particular difficult to solve a bug, when it's a new framework, or when the te…
This. While I understand that many people enjoy writing code and do so for fun, there are a large number of fantastic engineers that don't (myself included). Just as I wouldn't give someone preference for a robust profile, I'm not going to penalize someone for lack thereof. There is only so much time in the day and if they can do ten hours worth of work in eight hours and choose to spend their off time with their fam…
We don't contribute to FOSS because we are hobbyists or good Samaritans, we do it because we need the features or fixes. We do it because in the long term it is cheaper and more efficient than maintaining a fork or developing a closed source component.
Earlier quoted context omitted.
> The article does not say that conference talks, tweets, books, etc. should be used for hiring decisions and only GitHub should not. It says (right there at the end), that hiring is hard and any shortcut to try and get around that fact is wrong. It just so happens that "don't send us your resume, tell us your GitHub username" just happens to be the shortcut of the moment. Actually, Ashe has that on the Hire Me Page.…
> I understand this is a fact, but how this can be used against Github as a resumé or against OSS on your free time, I have a hard time seeing that. It comes off as incredibly stupid. I really don't think anyone is saying not to do OSS on your free time. That there is a greater lack of diversity in OSS than in software engineering as a profession suggests that whatever it is that keeps minorities out of software engi…
There's many good things about it, and reasonably few downsides to trade off against, but overall if you've got a GitHub I'd be more interested in seeing that than knowing what grades you got at school 15 years ago.
What the fuck am I reading? Is this asshole author trying to inject racism into something that is inherently race-, age-, gender-, wealth- and location-agnostic? Github doesn't care who you are, what you code or in what language you code it. And yet here we are with a dumbfuck author who, for the sake of clicks, just absolutely needs to shit on white men, that have been the bane of all tech-interested non-white men since the dawn of time.
When I hire I ask for code samples first and the person's name last. Shit, I'd hire the person based purely on code, put up anywhere on the net, and an anonymous chat, conducted fucking anywhere, and only require their name and social security number when signing the contract.
Shit I'm pissed off now. Some people just can't accept that technology is the ultimate equalizer and instead have to project their white guilt into everything.
Ashe Dryden's original post has merit, I'm not contesting that. James' post however, is wrong on so many levels. It's worth noting that James is a UK based developer. Most of his points may be completely valid in the US but they are completely at odds with the UK climate. I've worked with an inordinate amount of tech companies in the UK and consulted with many more and I've yet to come across any that hire based prim…
The problem with this is that you can't really make a logical decision when the code (on Github/bitbucket) is removed from its context. Maybe none of the code follows best practice, but there is a compelling reason why this is so. If your decision on whether to pursue a candidate or not does not include a discussion with the candidate about their available code, you are missing an integral piece of the puzzle.
Honestly, those skills are very valuable indicators and do not require someone to be giving up their nights and weekends to OSS.
1) Motion detection algorithms for security cameras in outdoor environments with a lot of ambient noise that needed to be ignored.
2) Medical informatics data model with a recommendation engine component for predicting which ICD/CPT/SNOMED code to use for optimal chance of insurance coverage.
3) R&D, implementation, and deployment of an EAV/CR [2] open schema based analytics platform using the neo4j graph database for persistence
So far I've had the luxury of only using meatspace networking to find interesting jobs to work at, but I stress over suddenly finding myself unemployed in the future and having to face the modern interviewing process with social networking activity used as a screen.
Can anyone describe how one's GitHub is used in an interview? Is a candidate with an interesting, non-trivial personal project on GitHub considered, or are candidates judged on their contribution to others' projects?
[1]Started working on a neo4j data science project involving gathering, refining, and translating film, actor, and director data into a graph data model for efficiently answering deeply recursive queries.
[2]http://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%...