4 ms·
I'll put it out there. "No programming test these days is valid without full access to Google." This is the opposite to conventional wisdom which says that pr
by andrewstuart 10y ago
I'll put it out there.
"No programming test these days is valid without full access to Google."
This is the opposite to conventional wisdom which says that programming tests must be done in an isolated environment without access to the web "please deposit your mobile phone at the testing room door".
No programming is done in isolation so the only way to effectively and realistically test someone is to see what results they get in a real world environment, which means full web access.
Don't get me wrong - I am very much against the idea that "I don't need to understand fundamentals cause I can Google everything" - only the misguided think that. What I do think is that recruiting needs to be about measuring real world results - that means full access to Google and StackOverflow.
THE most critical skill that is almost NEVER meaured - and in fact is generally avoided measuring - is the programmers skills in Googling to solve unfamiliar problems. The best programmers ride Google and StackOverflow like racehorse jockeys ride the ponies.
- pkaye 10y agoShould one need Google access to do a fizz buzz type of programs?
- andrewstuart 10y agoThe whole point is that if you are properly testing candidates then it is an open test and there's no point in theoretical tests like fizzbuzz when it is open book. The correct solution to fizzbuzz in an open book test is to search Google for "optimal fizzbuzz solution in language X". It forces the employer to create a test that is more real world and thus is a closer reflection of the actual work being done at that company. Unless of course your company is doing alot of real world fizzbuzz.
- flukus 10y agoThat would defeat the point of fizzbuzz in the first place. It's to see if they can translate rules into code, to see if they understand the very basics of programming. If they google "optimal fizzbuzz solution in language X" then you're seeing if they can copy and paste code. There is plenty of room for more open tests, but fizzbuzz doesn't require it.
- freework 10y ago> then you're seeing if they can copy and paste code. Thats the job though. Most jobs include a lot of googling + copy/paste.
- flukus 10y agoIt's not the job. If that was the job they'd hire kids out of high school to do it.
- andrewstuart 10y ago>> That would defeat the point of fizzbuzz in the first place. That's precisely my point. If your selection process includes fizzbuzz then your selection process is ineffective.
- flukus 10y agoSo how do you filter out people that manage to have successful software careers despite not being able to code?
- freework 10y agoThe same way all other industries do it, by asking the candidates questions and judging their capability based on how they answer said questions. How do hospitals hire doctors? How do law firms hire lawyers? How do insurance companies hire insurance salesmen?
- deleted 10y ago[deleted]
- flukus 10y ago> How do hospitals hire doctors? How do law firms hire lawyers? Both of those examples have rigorous training requirements before it's even legal to call yourself one and even then they still have some level of fraud. Anyone can call themselves a programmer and the only real world requirement is being able to program.
- donw 10y agoI suspect that you are thinking of FizzBuzz differently than it was originally intended. FizzBuzz is not designed as a test of real-world programming skills; rather, it is a deliberately easy test to ensure that a candidate can solve an elementary programming problem from scratch. The idea being, that somebody that can not solve a trivial problem is in no shape to tackle a harder problem. Many companies overthink this. They add TDD, or try and test if a candidate can implement Dijkstra's Shortest-Path Algorithm, or any number of other complications. But that all misses the point of what FizzBuzz does. FizzBuzz is a first-stage filter, and exists only to screen out copy-pasta programmers that, while their resumes might look good on paper, can't actually code. There are a lot of those programmers out there, even today. FizzBuzz should take a candidate no more than five minutes in a language they are familiar with. It really should be that level of simple. After FizzBuzz is when you can dive into the real-world problems, because the candidate has demonstrated that they can write code. Now, admittedly, I have moved past FizzBuzz, and now prefer doing a simple pairing exercise over-the-phone, but FizzBuzz is still a useful tool in the interviewing toolbox for companies that don't use pair programming. If you do use FizzBuzz, I do recommend changing it up. Don't just copy Atwood's FizzBuzz problem. Change the numbers, mix the conditionals around, that sort of thing. But keep it just as simple.
- vacri 10y ago> FizzBuzz is a first-stage filter, and exists only to screen out copy-pasta programmers that, while their resumes might look good on paper, can't actually code. I said recently in another thread that the lead tech at my company was complaining during one round of interviews for a senior position, that some of the candidates couldn't even conceptually 'get' FizzBuzz, let alone code it. > FizzBuzz should take a candidate no more than five minutes in a language they are familiar with I'll go a step further and say that if you're the kind of person that takes FizzBuzz as a personal insult, then you should be able to write it out in 60 seconds max, and move on with the interview. FizzBuzz is not for 'you', it's for the people who claim to be as good as 'you', so take it easy and move on. Complaining about FizzBuzz is like complaining about having a police check done, even though you don't have a criminal record. The check isn't for 'you', the innocent person.
- pkaye 10y agoThere is some base level of knowledge I expect of a candidate without having to search Google.
- jimjimjim 10y agoI was with you until the "The best programmers..." line. They are the best programmers for whatever reasons were important in whatever it was that they were doing. When I have asked interviewees to do anything on a whiteboard I've generally said 'pseudo-code is fine or whatever language your comfortable in or even diagram it'. What I'm looking for is an awareness of high-level concepts and ideas. People may not google for something if they don't know to google for it.
- deleted 10y ago[deleted]
- packetslave 10y agoIf you can't write FizzBuzz in the language of your choice without access to Google, I don't want to hire you. Period. In fact, I will campaign actively against you being hired. Note that I said Fizzbuzz, not an actual in-depth programming question. FizzBuzz (and similar) questions tell me nothing whatsoever about your programming ability, but they can tell me everything about your lack of it.
- mafro 10y agoI completely agree with you - being unable to write FizzBuzz is a red flag. However, finishing FizzBuzz under interview conditions does not really prove very much at all about a candidate's likely success on the job. In the limited time I want to spend interviewing, an hour on FizzBuzz is a massive waste of everyone's time.
- x1798DE 10y ago> In the limited time I want to spend interviewing, an hour on FizzBuzz is a massive waste of everyone's time. How could it possibly take an hour to write fizzbuzz for anyone of reasonable ability?
- efaref 10y agoFizzBuzz should take 5 minutes for a senior dev (where the python example in the article is essentially the "correct" answer). If it takes a candidate an hour, something is wrong.
- flukus 10y agoIt should take 5 minutes for an entry level dev.
- dTal 10y ago...an hour? Man, if they couldn't do it in less than 15 minutes I'd stop the interview right there, thus saving everyone's time.
- mafro 10y ago