5 ms·
well you better have something to show then such as a public github repo.
by chaostheory 13y ago
well you better have something to show then such as a public github repo.
- taopao 13y agoIf this approach became popular enough, it seems like this method could be easily gamed via outsourcing.
- chaostheory 13y agoGood point but it's better than nothing. Besides asking the supposed author about their work could probably uncover whether or not they actually wrote it. If they worked on a big open source project, it'll probably be less likely that they were faking.
- scottshea 13y agoA good github repo does go a long way. I have one project I did as an interview 'test' that I leave up there simply because it shows my thought process etc. It was not a proprietary thing so no sensitive information is in it.
- toomuchtodo 13y agoPass. I spend enough time at the office writing code that I can't show to the world because my employer owns it. I don't need to justify my six figure salary to my next employer by writing even more code on my off time just to prove I can write said code.
- chaostheory 13y agoWell then how am I going to figure out whether or not you can code? The only thing I can think of is an expensive two week trial period which doesn't make sense since I feel that most programmers will either submit work or submit to a pop quiz.
- toomuchtodo 13y agoGood developers cost, what, $120K-150K/year? If a two week trial period is "expensive" to you, you don't have the budget for someone in that pay range.
- mikeash 13y agoIt's expensive in other ways though. A programmers who is currently employed but thinking about moving on probably won't agree to a two-week trial period because of the substantial risk that they get rejected afterwards and end up unemployed. That makes the trial period expensive to him. In turn, it makes it expensive to the employer as well, because you'll filter out good people.
- toomuchtodo 13y agoCan they not do this two-week project after hours? Must it be in your office, on your schedule? Where you code, the hours you code, these do not matter. The code is what matters.
- mikeash 13y agoSure, but now it's not going to get full time dedication, maybe half that if you're lucky. So it's more like four weeks. And maybe they don't even have that much free time, so it's even longer.
- chaostheory 13y agoTime is an expensive resource for even teams in large corporations. Most often you'll be spending a week or two going over the context and rationale of existing stuff. This gets worse the larger and older the company.
- acuozzo 13y ago> Well then how am I going to figure out whether or not you can code? Provide the candidate with a PC representative of what you'd give to him/her during the course of his/her's employment and assign an ~one-hour-long programming assignment to complete while you sit nearby. If the candidate needs a particular program (e.g., "I don't like Vim. I prefer to write my code in VILE!"), then give it to 'em.
- lamp344 13y agoIt's funny, I have a very well developed github account and a couple of public web application side projects. I'm always curious where employers think that code came from when they reject me for not being able to do fizzbuzz on a white board in front of 5 people.
- matwood 13y agoYour example shows that even within IT there are segments of people. There are people who are algorithm/book smart. They can code fizzbuzz, b-trees, etc... all day long on the white board. But those same people may not be able to ship something. There are other people who don't even care what a b-tree is until they come across some problem they are researching on SO because their shipped app is broken. Each of those people are important to have depending on the companies situation and that's why no one interview process works for all programming positions.