RE: /400 skills test (actual coding)

Many companies these days have been burned by giving references, to the
point where it's against company policy to do it.  My former employer's
policy is that all reference requests must be referred to Human Resources.
The only information HR will give out is start date and termination date.
The company doesn't even like employees to give out personal references.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Rob Berendt [mailto:rob@dekko.com]
> Sent: Thursday, May 18, 2000 5:33 PM
> To: MIDRANGE-L@midrange.com
> Subject: Re: /400 skills test (actual coding)
> 
> 
> Can anyone expect reasonable answers from a former employer?  I 
> wonder what they would say for fear of lawsuit?  For example if I 
> was to say that employee X was a good programmer/analyst but had 
> more excuses than Max Klinger for missing work would that get me 
> in trouble?
> 
> 
> 
> 
> 
> MacWheel99@aol.com on 05/18/2000 04:19:06 PM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To:   MIDRANGE-L@midrange.com@Internet
> cc:    
> Fax to:       
> Subject:      Re: /400 skills test (actual coding)
> 
> >  From:    boothm@earth.Goddard.edu
> 
> >  No one else has even mentioned looking at actual code as a 
> means of 
> >  evaluating a programmer.  Why not?
> >  
> >  It interests me that no one has yet mentioned a portfolio 
> of code as a 
> >  means of evaluating a programmer.  I have a selection of 
> code that I feel 
> >  represents my abilities and that I feel should be of more 
> interest than a 
> >  written test. 
> 
> I have done this in the past, but I recognize that it is 
> extremely unethical 
> if not illegal.  The source code that I wrote for employer-X 
> is the property 
> of employer-X.  
> 
> For me to walk off with a copy of that source code to use as 
> reference when 
> applying for a job with some other employer is a form of 
> theft.  There is no 
> way the old employer is going to give permission for a copy 
> for this purpose. 
>  There is the risk that the new employer staff will copy some 
> stuff, in which 
> the original code was based on derivative code from some 
> licensed software 
> package.
> 
> I recognize that potential employers might want this information from 
> potential hires but would not want former employees doing it.
> 
> Why did you leave your former job, or want to leave?   ... 
> ask prospect
> Why did you part company with this employee?  ... ask former employer
> Compare answers
> 
> If they have in fact left ... ask former employer ... would 
> you seriously 
> consider re-hiring this person ... was the problem with their 
> skills or with 
> personality conflicts
> 
> An HR person who does not know the technical topics can 
> filter down to 
> candidates who are technically competent & have reputations 
> for honesty & 
> integrity, based on such checking of references & former 
> employers, to filter 
> out who the technical people should do the technical interviews with.
> 
> Al Macintyre  ? ?
> http://www.cen-elec.com MIS Manager Programmer & Computer Janitor
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---