Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!hellgate.utah.edu!dog.ee.lbl.gov!ucbvax!tut.cis.ohio-state.edu!n8emr!uncle!basho!john From: john@basho.uucp (John Lacey) Newsgroups: comp.object Subject: Re: Object oriented software engineers Message-ID: <1991Apr22.061146.861@basho.uucp> Date: 22 Apr 91 06:11:46 GMT References: <1899:Apr1206:12:4991@kramden.acf.nyu.edu> <1991Apr17.215418.26300@visix.com> <1991Apr19.182919.26229@dg-rtp.dg.com> Organization: Sportsware Lines: 39 cole@farmhand.rtp.dg.com (Bill Cole) writes: >This may sound naive (it seems to when I say it): What do you consider a >non-trivial sample? And how closely do you inspect it? In the years >I've been doing this, I've never asked -- or been asked -- to see anyone's >code. It's an interesting idea, though. I think so, too. Given that I feel writing software (especially in the age of user interfaces) is very akin to design, I always though job applicants should have portfolios. If not of source code, at least demos of programs they have written (of the actual thing, under a give-it-back NDA). >How about this alternative (since not all candidates will be using the >language I may choose): Given a problem, let the candidate work out the >solution method on the wall with you. One, it gives you a clue to how >the individual attacks problems and, two, how they work in a small group. I like that idea, too. You reason for it is terrible though. If I can't read Pascal, C, C++, Ada, BASIC, Fortran, etc., what am I doing thinking I have the expertise to hire a programmer? Talk about throwing darts blind-folded! 1/2 :-) >Or this: Given a piece of code, explain what it does and how it could be >changed. For what it's worth, I have seen Bill Gates claim in several places (the most accessible in-print version appears in _Programmers At Work_, by Susan Lammers, Microsoft Press) that this is his standard hiring procedure. In addition to deciphering what the program did, the applicant was expected to be enthusiastic about it. :-} >/Bill Toodles and cheers. -- John Lacey 614 436 3773 73730,2250 john@basho.uucp or basho!john@cis.ohio-state.edu