Essentially we covered these things outside the question part Ron. The
code/style is so important to this client that I know I must hand over a
product where every program has a similar look and feel, so questions
regarding the "imposition" of coding standards were very important. The
written program was a little less important as its a small market here
and I tended to know most of the people, but I did get one chap to bring
some code, it was difficult though as his code was fine, but he hadn't
really worked with SAS as a large scale development tool, more as a
simple report writer.
Thanks, I think this thread has actually spun out a number of
intervierwing techniques that are useful, as well as showing that
interviewing technique seems to be a surprisingly emotional issue.
Personally I think the interview changes for each project, and to some
extent for each interviewee and client.
"Fehd, Ronald J." wrote:
> Great thread, Don.
> Thanks for inititiating it
> and wading thru the swamp of tangential replies. :-Q
> Now that the dust has settled
> I'd like to add these possible items to the interview:
> * Show me a program you've written and polished
> and consider reusable.
> * Show me your/the Style Sheet you follow.
> Just couldn't resist the opportunity for a plug:
> SUGI 25: 2000 Indianapolis IN
> App Dev 38 Writing for Reading SAS Style Sheet
> The Writing for Reading SAS R Style Sheet:
> Tricks, Traps & Tips from SAS-L's Macro Maven
> Note: My New&Improved version will be presented this fall
> at both SESUG and NESUG.
> And this will be a chapter in my forthcoming book on macro usage.
> Ron Fehd the macro maven CDC Atlanta GA USA RJF2@cdc.gov
Don Stanley, B.SC, Dip O.R.S, MNZCS
EMAIL:: firstname.lastname@example.org, email@example.com
Author:: Beyond the obvious with SAS Screen Control Language.
Author:: Solutions for your GUI Applications Development Using SAS/AF
http://www.sysware.co.nz , http://homepages.rootsweb.com/~ashluke