On the contrary, I agree with wkkay, and that we can sniff out bs better (faster, and more consistently) by giving a coding test and seeing how you actually try to solve the problem. e.g. Touch typist? Which code editor? Can function well in new environments? What excuses given if something's not working?

It's all in the how and what coding test you give. The downside is that this only works well more the more experienced interviewer.

"I've taken a whiteboard test that asked me to come up with an algorithm that was difficult for me. I got the job even though my solution was horribly inefficient (and I knew it), and the interviewer later told me that the point wasn't to see what algorithm I knew - it was to see if I acted like an ass when I didn't know stuff."

https://news.ycombinator.com/item?id=8333623