LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (May 2006, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 9 May 2006 21:14:08 -0400
Reply-To:     "jakeboot@gmail.com" <jakeboot@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "jakeboot@gmail.com" <jakeboot@GMAIL.COM>
Subject:      Re: OT: Lines of code per day...
Comments: To: Charles Harbour <charles.harbour@pearson.com>
In-Reply-To:  <200605092049.k49KhKDx027931@mailgw.cc.uga.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Don't want to get into this too much, as I spent a lot of time for the DOD trying to create metrics for SLOCs, CLOCs, etc. As I understand the work that was requested is still a WIP (and by the way, there are working groups on this). But what perplexed me from the start, was how to weigh a Source Line Of Code done in assembler vs pascal vs fortran... Still find it interesting that so much time is wasted on this, but as for the aforementioned dept. and perhaps for some bean counters, I suspect hidden agendum -- but I've said too much, and will listen, but dare not say anymore. Love the response from CH

On 5/9/06, Charles Harbour <charles.harbour@pearson.com> wrote: > > When interviewing folks for programming positions, I provide a complex > problem, and ask them to define how they would approach it. You usually > get a response that is indicative of their programming 'level'--depth of > experience and level of thoughtfulness. > > But, for what it's worth, it kinda depends on what you want. Do you want > somebody right out of school, who's great at cutting and pasting, who > maybe > doesn't produce the most 'mature' code, but can bang out jobs by the dozen > with little regard to efficiency (either coding or system), or do you want > somebody who takes 3 weeks to produce some of the most beautiful, > reusable, > robust code that delivers the same results that the rookie could have > banged out in an afternoon (albeit with less robustness, no comments, > etc)? What is the nature of the work presented? Do you have complex > problems that need sophisticated solutions? Or do you need somebody who > can whip things out quickly and not-so-cleanly? Should both programmers > be > measured by the same yardstick? > > My 2 cents. > CH >

-- Jake --------------------- The scholar is early acquainted with every department of the impossible. John Ruskin


Back to: Top of message | Previous page | Main SAS-L page