Date: Thu, 4 Mar 1999 22:57:14 +0000
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Paul Gill <paulgill@JPS.NET>
Subject: Re: SAS Book recommendation
Content-Type: text/plain; charset=us-ascii
>>>> is the posting by "Lambert, Bob" <Bob_Lambert@AFCC.COM
>>> Hey Paul,
>>> I reviewed your book at www.sas.com. ("The Next Step: Integrating
>>>(the Software Lifecycle with SAS Programming" -pbg) It seems like a very
>>>good book. And the sample code you've supplied is interesting and well documented.
>>>Some of this code I can use immediately. When I do so, I will reference
>>>your book so others within the company know the true source. I'm assuming
>>this is not a copyright infringement. If I'm wrong on this, please advise.
Absolutely feel free to use any code in the book
>>> Will this book be on display at SUGI?
Yes it will. (the front of the book cover is gold)
>>>I have a friend who is attending
>>>and I would like to have him look through it and get his opinion. I'm
>>>thinking of buying it but I don't have the "Professional SAS Programming
>>>Secrets...." book and there have been many postings recommending this book.
>>>So I'll have to make a decision as to which one to buy.
The theme and content of the two books is completely different Which to
buy? I must confess "Professional SAS Programming Secrets" is an
OUTSTANDING book. Their book is concerned with techniques, tips,
tricks and traps. "The Next Step: Integrating the Software Lifecycle
with SAS Programming" has a completely different slant. The idea is to
walk the user through each phase of the software lifecycle: analysis,
design, coding, testing, debugging, documentation and user acceptance.
I tried to cover many topics in this book that have NOT been covered in
other SAS books such as:
How to test SAS programs using whitebox and blackbox techniques
How to debug your programs
How do you know if you have chosen effective variable names
When to use and when not to use macros
How to make the program more readable
Whether GOTO is ever considered an acceptable construct
Measuring the mathematical complexity of your program and how to reduce
What are good and bad SAS constructs,
How to write modules from scratch
How to write robust code without using "hard codes"
How to estimate the number of bugs still remaining in a program or
Analysis tools to help your organize your thoughts
The book is also sprinkled with humor to keep the tone light and fun. I
guess that reflects my personality.
Hopefully, you can convince your boss that you MUST have both books or
you can't think clearly! I think Edgar Allan Poe went mad over a similar
>>> Also, my response below apparently pushed a button and I apologize for
>>>that. I'm not sure where the high and almighty inference came from....maybe
>>>there's a history there or something. Or maybe it was the delete statement.
>>>I know these statements can have unpredictable effects on other programmers
>>>sometime. This is known as Post Traumatic Delete Syndrome. A guy I use to
>>>work with was always deleting things on impulse and then trying to find a
>>>way of recovering them (this did result in his finding the -altlog option
>>>which I never knew about). I think he did it half the time just to get to
>>>me. I almost removed his delete key from his keyboard but decided not to.
Actually, no offense taken (nor was I trying to offend), I was trying to
inject my (subtle?) sense of humor with the "high and almighty" phrase.
By the way, I enjoyed your coding construct. It gave me a chance to
jump into the fray. Anyway, I don't take things too seriously. I just
read along and try to have fun.
Thanks for the input Bob and keep the postings rolling!
Author of "The Next Step: Integrating the Software Lifecycle with SAS
Director of Bioclinical Data Services Inc.