From: Richard <legalize at xmission.com>
---snip---
I didn't get mad, I just 'dug in' as you
say. But I didn't get the
"trick" to the puzzle so it just sat there unfinished. Basically I
felt it was a waste of precious interview time because while I might
often get stuck on this little trick puzzles, I very rarely get stuck
while writing software and even then I don't stay stuck for very long.
This becomes evident when coding with me or looking at code I've done,
but its not evident by shoving random brain teasers in front of me and
demanding I solve them in 10 minutes. I'm not a seal in a circus act.
Hi
I often ask questions I don't expect the person to be able to answer.
What I want to find out is vary valuable to me. I want to know
how that person thinks about problems. I don't reject them because
they don't get the answer nor does it mean that much if they get
the wrong answer. It is how they approach the problem that
I'm most interested in finding out.
They can always learn what they'll need to know once they start
working. I don't have enough time to teach people how to think.
Dwight