LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (September 2000, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 7 Sep 2000 13:22:49 -0600
Reply-To:     Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
Subject:      Re: What do well-rounded SAS programmers need to know??
Comments: To: rjf2@cdc.gov
Content-Type: text/plain; charset=us-ascii

"Fehd, Ronald J." <rjf2@cdc.gov> wrote:

>> From: Jack Hamilton [mailto:JackHamilton@FIRSTHEALTH.COM] >> "Mike Harris" <mikeh@AMGEN.COM> wrote: >> >> >In my experience, many SAS >> >programmers are clueless about the application of a >> documented software >> >development life cycle to SAS programming. Without that, it >> is impossible to build valid SAS systems. >> >> More difficult, perhaps, but not impossible. > >'more difficult' to figure out, and maintain, >but there are some -- of us -- who like their version of job security.

Well, yes, but what I meant is that it is possible to create usefully documented SAS programs without using a "documented software development life cycle". It's also possible (and perhaps not even uncommon) to create useless documentation using a "documented software development life cycle".

-- JackHamilton@FirstHealth.com Development Manager, Technical Group METRICS Department, First Health West Sacramento, California USA


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