Re: Testing job applicants

[Chris.omitthisbit.Brown@arm.andthisbit.com (Chris Brown)]

In article <06mqq7.fp.ln@fenelon.com>, Pete Fenelon  <pete@fenelon.com> wrote:
>In alt.folklore.computers Ruff Records <ruffrecords@geocities.com> wrote:
>> But how to tell good from bad?  Our experience of CS qualified candidates at
>> interview was that their engineering knowledge was very poor so we abandoned
>> recruiting them.  If we knew which colleges ran the 'good' courses we could
>> only select those for interview.  Any suggestions??
>
>First, quanitify "good" -- well, I'd say courses where a systems approach
>is taken, where sound engineering judgement is rewarded and encouraged, and 
>where a high degree of intellectual rigour is needed, and where
>software and hardware aren't taught in isolation. 
>
>I'm sure there are more - they're places I've either studied and worked
>myself (York), been involved in collaborative work with (Newcastle,
>Teesside), or worked with graduates of who clearly knew how many beans 
>made five (the others).

Indeed. You might want to add Cambridge to your list, although you're
less likely to bump into graduates because most of us tend to end up
working within about 10 miles of the place after we graduate (for the
benefit of US based readers, the cambridge area , often dubbed
"Silicon Fen" is fast becoming Europe's answer to Silicon Valley,
albeit on a smaller scale at this point. The area around Cambridge is
chock full of high-tech startups, typically with a large proportion of
their employees being graduates of the University).

-- 
/*  _  */main(int k,char**n){char*i=k&1?"+L*;99,RU[,RUo+BeKAA+BECACJ+CAACA"
/* / ` */"CD+LBCACJ*":1[n],j,l=!k,m;do for(m=*i-48,j=l?m/k:m%k;m>>7?k=1<<m+
/* |   */8,!l&&puts(&l)**&l:j--;printf("  \0_/"+l));while((l^=3)||l[++i]);}
/* \_,hris Brown -- All opinions expressed are probably wrong. */