Date: Thu, 29 Apr 2010 01:21:26 +0000
Reply-To: toby dunn <tobydunn@HOTMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: toby dunn <tobydunn@HOTMAIL.COM>
Subject: Re: Notes from SAS Global Forum
In-Reply-To: <007701cae722$91e8fc30$b5baf490$@savian.net>
Content-Type: text/plain; charset="iso-8859-1"
Geez Alan read what I said I dont give a darn about new projects or code, its the old stuff currently in production man. EG has to be able to take the same existing code and produce the same results as DM does. Otherwise it makes management very pissy when the programmers come back and say we have to now all of a sudden have to rewrite all this existing code because the new editor wont work as theh old one does.
Toby Dunn
"Don't bail. The best gold is at the bottom of barrels of crap."
Randy Pausch
"Be prepared. Luck is where preparation meets opportunity."
Randy Pausch
> Date: Wed, 28 Apr 2010 16:31:38 -0600
> From: alan.churchill@SAVIAN.NET
> Subject: Re: Notes from SAS Global Forum
> To: SAS-L@LISTSERV.UGA.EDU
>
> How does using EG for modern projects involve code rewrites? EG is not a
> breaking change.
>
> Take a website of today and view it as a project. Websites have links all
> over them to content all over the web yet appear as 1 virtual entity.
> Nothing is different.
>
> Alan
>
> Alan Churchill
> Savian
> Work: 719-687-5954
> Cell: 719-310-4870
>
>
> -----Original Message-----
> From: toby dunn [mailto:tobydunn@HOTMAIL.COM]
> Sent: Wednesday, April 28, 2010 9:31 AM
> Subject: Re: Notes from SAS Global Forum
>
> Joe,
>
>
>
> Well one persons organization is anothers mess. Any new editor will have to
> in my opinion follow the idea of:
>
>
>
> 1.) Allow the concept of SAS programs as I can see some possible problems
> with old programs, having to rewrite old production jobs will cost
> businesses money.
>
>
>
> 2.) Allow multiple programs or projects ( depending on which one you want)
> to be run at the same time
>
>
>
> There is more than enough production code out there in use that anything
> that requires the business to have to rewrite the code wont be acepted. In
> short it would be SAS pissing in its users wheaties and then tring to force
> them to eat and like it.
>
> Toby Dunn
>
> "Don't bail. The best gold is at the bottom of barrels of crap."
> Randy Pausch
>
> "Be prepared. Luck is where preparation meets opportunity."
> Randy Pausch
>
>
>
>
> > Date: Wed, 28 Apr 2010 09:42:54 -0500
> > From: snoopy369@GMAIL.COM
> > Subject: Re: Notes from SAS Global Forum
> > To: SAS-L@LISTSERV.UGA.EDU
> >
> > I think that's a standard in the programming world nowadays... Visual
> > Studio, etc., has projects. You group your program files (and other
> > ancillary files) together in them ... makes for better organization,
> > and if there's one thing that programmers need desperately it's
> > organization :)
> >
> > -Joe
> >
> > On Wed, Apr 28, 2010 at 9:37 AM, Mary <mlhoward@avalon.net> wrote:
> >
> > > Also what's disconcerting to me is that EG insists on everything
> > > being a project; I said that I wanted to create a SAS program, but
> > > then it keeps asking me about saving the project rather than the SAS
> > > program; as a developer that's troublesome because my data often
> > > spans across multiple projects (and thus the data might not be in
> > > the directory of the project), and also there are naming schemes to
> > > folder on the local area network that must be preserved.
> > >
> > > What is the reasoning behind EG organizing things as projects and
> > > can this be overridden?
> > >
> > > -Mary
> > >
>
> _________________________________________________________________
> The New Busy is not the too busy. Combine all your e-mail accounts with
> Hotmail.
> http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID283
> 26::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3 |