re: /400 skills test

[Gwecnal@xxxxxxx]

In a message dated 5/18/2000 11:26:19 AM EST, boothm@earth.Goddard.edu writes:

> No one else has even mentioned looking at actual code as a means of
> evaluating a programmer.  Why not?

This is a good point - it would be valuable to know what the applicant 
thought was good code.  Even if I could not know that the applicant wrote it, 
I would know that the applicant (geez, I wish English had a gender-netural 
pronoun!) at least thought it was worth stealing.  That could be very 
revealing.  If it is full of uncommented tricky-tricky stunts, that would 
tell me something worth knowing.  That and maybe a 'find the program that 
contains this string and tell me what it does' kind of hands-on test.  We 
shall see.  Thanks, Lance
+---
| 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
+---