[Web4lib] test ideas for web job candidates

[Ross Singer]

On 10/14/06, Eric Hellman <eric at openly.com> wrote:
> When I hire people to do programming I look for an aesthetic sense
> and for pride of craftsmanship. I don't give people stupid tests, I
> look at things they've done and want to show me. I avoid candidates
> with resumes full of lists of technologies, I look for people who are
> engrossed in problems and their solutions.

I can't begin to express how wise I think this approach is.  I see all
too often departments try to quiz the specific skills of an
individual, or develop elaborate tests to see the programming
knowledge of a person -- and this is really missing the point.
Incredibly strong in a language does not make a good developer; Eric
mentions the aesthetics and I would like to add vision to the pile.
These skills are /much, much/ more important than clean code, because
experience will lead to cleaner code, vision to see a larger picture
cannot.  Just the communication piece of the interview should let you
know if this is a person you want solving your development problems.

Besides, my guess is that you can't pay enough to get a person that
would test well and have the aesthetic element, honestly.

-Ross.