Thanks for the inputs and the link. While I agree some people can not bring the best during the interview I think the reading code is much simpler that actual writing. You see how fluent the candidate is in the language when writing and you can distinguish superman who can talk about everything and can't write a line of code. That's why the exercises are so simple and not some bubble/quick/... sort algorithms or similar stuff. In the end, you don't pay the programmer only for reading and debugging but also for writing the code.
I believe any programmer should be able to write for-loop and if-condition wrapped in a function. No matter how stressful the interview is for him/her :) And if it is too easy for the candidate I can always harden the requirements ;) During the interview it's more a pair programming than live coding and it can lower the stress significantly.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the inputs and the link. While I agree some people can not bring the best during the interview I think the reading code is much simpler that actual writing. You see how fluent the candidate is in the language when writing and you can distinguish superman who can talk about everything and can't write a line of code. That's why the exercises are so simple and not some bubble/quick/... sort algorithms or similar stuff. In the end, you don't pay the programmer only for reading and debugging but also for writing the code.
I believe any programmer should be able to write for-loop and if-condition wrapped in a function. No matter how stressful the interview is for him/her :) And if it is too easy for the candidate I can always harden the requirements ;) During the interview it's more a pair programming than live coding and it can lower the stress significantly.