Date:         Wed, 24 Jan 2007 13:25:36 -0500
Reply-To:     Ken Borowiak <EvilPettingZoo97@AOL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Ken Borowiak <EvilPettingZoo97@AOL.COM>
Subject:      Re: Development Processes of the Consummate SAS Developer

On Wed, 24 Jan 2007 10:09:41 -0700, Michael Murff <mysasbox@GMAIL.COM> wrote:

>Hi guys,
>
>I would like to get some feedback about coding and development best
>practices. I have been using SAS professionally for several years. I have
>tons of books on the subject. Most are syntax related with a one exception,
>Paul Gill's, "The Next Step" (now out of print?). I would like to get a
>better view of tips and best practices from others in the SAS user
>community. Basically, I would like to collect information to the effect of:
>"Common practices and attributes of the consummate SAS developer?". I am
>less interested in syntax, and more interested in process. I am sure that if
>I were to spend a few days watching some of the masters build applications I
>could arrive a more efficient list. But since I don't have an outstanding
>dinner appointment with Ian, Richard, or David (this list could be much
>longer) I will settle for some responses to my thread.
>
>Here are some starters:
>
>1. Monitor SAS-L
>2. Search SUGI papers
>3. A recent post by Alan C. mentioned that he uses Regexbuddy to develop
>Regular Expressions (great tip!)
>.

>
>I would like to build this list out with the hopes that K >> 3 :-)
>
>Best,
>
>Mike Murff

4. Attend user groups conferences and get involved with a local user group (LUG)

5. Effectively comment your code. Explaining WHAT a piece of code is doing
is good, but explaining WHY the code exists provides a bigger picture and is
potentially much more useful.

Regards,
Ken