5 ms·
Just today I interviewed someone for a programming position. I asked him if any of his code is publicly available (a open source project, a small library, anyth
by CWIZO 16y ago
Just today I interviewed someone for a programming position. I asked him if any of his code is publicly available (a open source project, a small library, anything) and unfortunately he said no. So now I have to bring him in for a coding interview.
It really saves a lot of time if you have something out there. Just make sure that the first thing one finds is something you want them to see (not some crappy code you wrote two years ago).
- scrrr 16y agoA friend was recently asked the same, also said no, and was declined the interview. He is a very capable software developer. It seems like being active on GitHub is slowly becoming almost a requirement in order to land a good job. I wonder if that is a good thing.
- chrisbroadfoot 16y agoBeing active with open source communities is definitely a huge advantage, but I wouldn't go as far as to say that you need to be active on GitHub. There are other ways to contribute open code :)
- jrockway 16y agoThe ideal candidate will do both. It's fine if you just hack other code, and it's fine if everything you make is 100% your own. But the best programmers do both.
- CWIZO 16y agoI'd never reject someone on that point alone. I'm guilty of not having anything (at least not something I'd like to show) out there too (thou I am working on it).
- dataguy 16y agoI like your last sentence. I am also sceptical if this is a good thing. And with reason: If you are working as a skilled software architect - and you work on projects under NDA or other laws/contracts for a long time, it could definitely come to the result that you do not have "current code" somewhere out there on github and such sites. And not everybody has the time or the reason to contribute or start an open source project. That even becomes more critical if you want to do other things in your non-working time than coding. If you have the chance to work for a company where you are allowed and instructed to work on open source projects and technology, then you are lucky. But I doubt that the major of software designers does so.
- jonpaul 16y agoYa but I think you're missing an important point. Having an active Github can demonstrate a developer with passion instead of one who just sees it as a job.
- Retric 16y agoI know way to many passionate, articulate, and terrible programmers to think passion a good thing. I also know plenty of really great programmers who don't find coding a challenge after all these years. On average I think passion speaks more to youth than the ability to get things done.
- jrockway 16y agoWhat does he do with the other 16 hours of his day? If I can hire someone who spends 41 hours a week programming, with 1 hour of work that I can actually see, that is going to be a big advantage over someone who claims they are a super-genius architect. Because the first person has documented proof of ability, but the second person just says he's really good. Don't worry, though. I work with "C++ experts" who don't realize you have to allocate memory before writing to it. Knowing how to program is not a prerequisite to all programming jobs.
- dalore 16y agoOnly 41 hours a week? Where do they work and are they hiring?
- jrockway 16y agoAnywhere? I've never had a job that required more than 40 hours a week.
- billybob 16y agoSome jobs don't "require" more than 40, but when your fellow developers are always there earlier and later than you are, and when your performance reviews go from bad to good after you ratchet up your number of working hours, and when your assignment list keeps growing longer and more urgent, you get the message.
- fender 16y agoIt happened to me but I was given a chance to prove my worth to them. It was a small company (basically a start up) , To cut the whole thing short I ended up with a job and worked with them for 2 years.
- cperciva 16y agoIt seems like being active on GitHub is slowly becoming almost a requirement in order to land a good job. You know, there is open source software which isn't on GitHub. Personally I'm far more impressed with someone who has a commit bit on a project like FreeBSD, because it shows an ability to work together with other people. Having code on GitHub just shows that you're able to fork someone else's work.
- xiongchiamiov 16y agoThere are of course large projects on GitHub, but your point still stands.
- nickelplate 16y ago"A friend was recently asked the same, also said no, and was declined the interview." I think that's retarded. There are more effective ways to filter out bad apples. Candidates could be asked to solve a puzzle and attach their solution to their application, for example. Most of the really good developers I know stopped coding in their free time after accumulating about 5-8 years of experience. They have other commitments (wife, kids...) and their day job is challenging enough as it is.