home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!pmafire!news.dell.com!natinst.com!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!spool.mu.edu!agate!linus!progress!leary
- From: leary@progress.COM (James Leary)
- Subject: Re: How to test a programmer
- Message-ID: <1992Dec18.160907.20052@progress.com>
- Sender: usenet@progress.com (Mr. Usenet)
- Nntp-Posting-Host: misseq
- Organization: Progress Software Corp.
- References: <1992Dec15.180712.845@ksvltd.fi> <1992Dec17.220330.15818@microware.com>
- Date: Fri, 18 Dec 1992 16:09:07 GMT
- Lines: 30
-
- troyf@microware.com (Troy Frericks) writes:
-
- >This is getting old! There is more to being a programmer
- >than, as others have pointed out, C trivia. Why not simply
- >check references, and ask for a sample of the person's
- >code. If somebody has a BSCS from a school that uses
- >C, that's another plus.
-
- >You should also find out if this person can work as part
- >of a team, if he/she can read and write, if their social
- >skills are ok (did they wash their hair this month?), can
- >they communicate, will they fit in with your organization.
-
- I totally agree with Troy. To give someone a test that would measure
- one's knowledge of obscure C functions and workings misses the point.
- Technical ability and experience certainly *do* play an important role
- in determining a "fit", but social skills and professional attitude are
- equally important.
-
- Another question: does one fail the interview if the test conditions are
- not satisfied? Having hired Programmers in the past, the steps they took
- to try any solve the problem or answer the question are *much* more important
- that the actual ability to solve the problem (Kobiashi Maru, anyone?).
-
-
- --
- ------------------------------------------------------------------------------
- Jim Leary | My opinions are mine and do not reflect the opinions
- Progress Software | of my employer.
- ------------------------------------------------------------------------------
-