Date:         Mon, 7 Oct 2002 11:01:37 -0400
Reply-To:     Ian Whitlock <WHITLOI1@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Ian Whitlock <WHITLOI1@WESTAT.COM>
Subject:      Can SAS be dangerous to your job?
Content-Type: text/plain; charset="iso-8859-1"

Shortly before NESUG I received a message containing:

>>>>>>>>>
I used to try to write SAS code (I had the only copy in the company) to try
to cleanup and identify problems but upper management decided I was not a
team player and layed me off.
<<<<<<<<<

I showed the message to someone else who quickly replied pointing to the
above sentence.

>>>>>>>>>
  I did exactly that -- used SAS to identify problems when we were building
the XXXX (data entry and editing system) for YYYY.  I also got laid off.
hmmmm....
<<<<<<<<<

The juxtapositon of the two statements got me to wondering about others.
Perhaps one should not blame the tool.  On the other hand, placing SAS in
the hands of a curious programmer is a little like giving a child a loaded
gun.

Any comments or anecdotes?

IanWhitlock@westat.com

---------------------------------------------------------------------
The contents of this message is the work of the
author and does not necessarily represent the
opinions, recommendations, or practices of
Westat.
---------------------------------------------------------------------