But a genius at what? I don't need a genius who can't TYPE, can't grasp the highly visual/visceral, "flow" aspects of good programming, or can't quickly read someone else's code, or spends 2 hours debugging because he can't see the difference between 0 and O.
The qualities I'm testing are more relevant to good programming than intellectual, but ineffectual, brilliance.
@BD: Yes, I'd often do a fourth test, if I was concerned with team integration, and that was to send the applicant to an Industrial Psychologist for a "personality profile" test. It wasn't good at the "positives" but was remarkably good at the "negatives", such as warning me that a person couldn't take criticism, would try to force his way, would perceive someone else's advancement as a personal insult, etc.
When I became a Vice President of one particular company, I read my own profile. That was interesting reading, and I have to say, very accurate, even on the negative qualities.
Last edited by Taylor514ce; 08-04-2008 at 02:14 PM.
|