Many thanks
Bernhard
supply paper and pen and sit candidate in front of a machine. ask
them to implement a bit of code to solve a typical, well-specified
'problem' in the given time (replicate something which you have done
before and are familiar with). worked for me.
Not a direct answer to your question, but it has been my experience
that Tcl can be picked up so quickly that you are better off focusing
on their general analytical smarts than "Tcl skills". If it were C++
or Java, yes, you probably want to test language specifics but for Tcl
I've had great success hiring smart programmers who had never seen Tcl
but were productive literally within a day, no exaggeration, and
completely at home within a week. Tk might have a slightly steeper
learning curve though.
If you really want specific questions to ask, you might want to browse
through wiki.tcl.tk, particularly the "Ask, and it shall be given*"
pages
/Ashok
It's customarily spelt "Tcl", not "TCL".
(Also: it's customarily pronounced "tickle", not "tee-cee-ell".)
So maybe there's your first two questions: ask them to spell it,
then ask them to pronounce it.
Beyond that, I have no useful advice.
--Arnold
After discussing general knowledge and experence, my approach has been
to have a few code samples (2 or 3) that are flawed or poorly written
(sometimes in more than one languages). I then give the applicant one
sample at a time and ask them to comment on what they see. I don't
provide any help I just listen. It's not difficult after you see a few
applicants to then decide which one you want.
tomk
I agree, pick someone with formal training and a good mind -- programing
languages should be able to be picked up by someone like that in at most two
weeks.
--
+------------------------------------------------------------------------+
| Gerald W. Lester, President, KNG Consulting LLC |
| Email: Gerald...@kng-consulting.net |
+------------------------------------------------------------------------+
But I would prefer "savoir-être" rather than "savoir-faire" ...
Luc