Date:         Tue, 26 May 1998 10:11:45 -0400
Reply-To:     Diana Noble <diana.noble@PRUDENTIAL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Diana Noble <diana.noble@PRUDENTIAL.COM>
Subject:      Re: DATA TEST
Content-Type: text/plain; charset=us-ascii

I'd say both the 7 P's and KISS are very useful.  The 7P's for starting
large projects (and even deciding programmatically how much time to spend
on planning or even NOT to plan are results of '7P' planning)... and KISS
for code modules and documentation both work well.
 
Best of luck,
 
Diana
 
 
<<Hello Wiiliam and sas-l !
 
I would have to disagree.  The 7P's is a good way start thinking about the
problem to determine the amount of planning needed. In my case, many
solutions have to come on the fly or close to it.  I must admit sometimes a
bit more planning is good in many cases but the cost of delaying the
solution can sometimes be much greater than the performance gain.  In our
environment, we also try to emphasize that we don't write code once for
every instance, but add to a library, which is continuously under
development as new projects roll in the door so much code is touched more
than once.
 
Magnus
 
-----Original Message-----
From:   William W. Viergever [SMTP:wwvierg@IBM.NET]
Sent:    den 22 maj 1998 19:10
To:     SAS-L@UGA.CC.UGA.EDU
Subject:        Re: data test; Can you help me 2?
 
Is KISS related to the Seven P's? (Proper prior planning prevents piss poor
perfomrance)
 
 
Later <<g>.>>