tag:blogger.com,1999:blog-9537945.post2868759326224856948..comments2007-09-13T13:52:42.421-05:00Christopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9537945.post-89537941763996144892007-09-13T13:45:00.000-05:002007-09-13T13:45:00.000-05:00Ah the age old ethics discussion.<BR/><BR/>I couldn't agree more with your stance on this. Eons ago when I was in school, a CS professor brought up a very valid point in that he said, "...Even though there are no official licensing/certification required for software engineers and the like, doesn't mean we cannot hold ourselves to high ethics.."<BR/><BR/>Heck I've walked away from a job because I just couldn't do what upper management asked of me.Davyhttp://www.allscm.comnoreply@blogger.comtag:blogger.com,1999:blog-9537945.post-84703238833840561842007-09-13T09:34:00.000-05:002007-09-13T09:34:00.000-05:00Hear, hear!<BR/>I try to use my own experience as an end user as a general rule of thumb. I'm a pretty savvy computer user, so I don't like applications taking liberties with my machine that I didn't specifically authorize (or even know about). So when writing our setup kits, I try not to do anything that would piss me off if it were done to me by a kit I was running at home. It's a good rule of thumb for overall design, too.<BR/><BR/>Anyway, great food for thought, as alwaysSairennoreply@blogger.com