From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,bdc41aa5ff8e1d93
X-Google-Attributes: gid103376,public
From: frank@bigdog.engr.arizona.edu (Frank Manning)
Subject: Re: Programmers -> Engineers; Engineers -> Programmers
Date: 1996/08/13
Message-ID: <4uol55$mhq@news.ccit.arizona.edu>#1/1
X-Deja-AN: 173807947
references: <1996Aug8.115630.4568@relay.nswc.navy.mil>
 <4uic1j$fg0@news-e2d.gnn.com>
organization: College of Engineering and Mines, University of Arizona
newsgroups: comp.lang.ada
Date: 1996-08-13T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <4uic1j$fg0@news-e2d.gnn.com> ajaskey@gnn.com (Andy Askey)
writes:

>       [...]
> 3)  Hire based on the interview and not on previous job history.  I
> have found that many people kick around the industry for 10 years,
> never really accomplishing anything except to conpile a long list of
> projects to add to their resume.  Some awfully average people have
> some awsome looking resumes.  [...]  

Sounds like good advice to me. One question, though -- how do you decide
who to interview, if you can't rely on resumes, which are mostly job
histories? Especially if you're hiring an Ada programmer (to make this
thread somewhat relevant to cla)?

-- Frank Manning
-- Chair, AIAA-Tucson Section