<ju**********@yahoo.co.in> wrote in message
news:11**********************@g10g2000cwb.googlegr oups.com...
Hi guys,
I want to have your opinion on how a candidate should be judged for
his programming
skills in C ? Should he be checked for his programming basics or should
he be asked to
write a program for some problem (like sorting or searching ) ?
The problem with all testing methodologies is that people have weaknesses in
different areas. When you develop a test, you "discriminate," intentionally
or not, against certain skills and types of intellect. If you test for
intricate knowledge of simple language details, as Heathfield and Thompson
suggested, you may end up with a programmer whose code is correct, but who
struggles to solve bigger problems. If you test for problem solving
ability, you may end up with a programmer who can solve problems elegantly,
but who struggles to implement the code correctly. The programmer may be
strong in one or more of string processing, or databases, or numerical
computation, or DSP algorithms, microcontrollers, but at the same time be
weak in the other areas.
You need to define what your business needs are for that person. What areas
of coding is your business involved in? If you're in finance, do you want
someone who is strong in string processing or databases? You'd probably
want someone strong with numerical computations...
Rod Pemberton