Sam,
if its for your use only I guess I agree. But if it becomes public
domain then a higher (stricter?) standard should be made *UNLESS*
(IMO) a statement is made that the output is should not be depended
on and the statement should be either at the the top or of the report
or somewhere plain that you can see (even thats a maybe IMO)).
Ed
On Nov 19, 2012, at 1:20 PM, Sam Golob wrote:
Hi Folks,
Just for the record, I have to say one thing. If you are
writing some program that you're selling for money, it has to be
(at least with your best effort) 100 percent airtight. When you
have the responsibility for keeping a data center up, you have to
take that responsibility seriously. Usually a "for pay" product
comes with some sort of written warranty, and therefore you can't
risk any loss of money for the data center, or for yourself. (This
really goes without saying, but obviously I have to say it, because
of the above discussion thread.) Notwithstanding, people still
find it useful to write "quick and dirty" programs for themselves,
or even "quick, but clean and careful" programs. (And this is
obvious to all of us).
So with that said, I wish you all the best of everything.....
Thanks for your feedback.
Sam
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
