Re: not enough real programmers? (was Re: Byte Magazine: 18 Vintage issues, 1985-1986)

[prs@gol.com (Peter Stephenson)]

On Thu, 5 Aug 1999 19:12:46 -0400, "Ian St. John"
<istjohn@spamcop.net> wrote:

>
>Downsizing, and outsourcing are other factors, creating a demand for
>documentation as proof of specific skill. More effort is spent on
>'personnel searches', and less 'personal evaluation' is made. When the
>person turns out to have the experience, but not the skill, it just
>forces higher 'minimal qualifications'.
>
All true.  It can be difficult recruiting good programmers, though.  I
mean, how the hell do you find out whether they can code in an
interview?

I've resorted in the past to making them sit written papers (one on C,
one on business knowledge).  That weeded out a *lot* of people who's
CVs (resumes) looked very good.  Of course it would also weed out
excellent programmers without current C knowledge  - written papers
inevitably focus on the more obscure corners of the language.  That
shows that they have the interest and skill to really understand a
language - but, as I said.

After that we'd have them in to see if (a) we liked them (weirdness
and eccentricity no obstacle), and (b) to give them some simple but
interesting  programming problem to talk around and investigate, again
using C.

I'm sure we missed some good people that way, but what other way is
there?  

Suggestions welcome!