Well, until SOX, we did not separate them. I always felt that combining the two functions was much more effective. Using file resizing as an example, how would a programmer, who has been tasked with speeding up a particular process, be able to check for overflow? If you are both a Database Admin and a Programmer, you can easily determine if the culprit is overflow, file type, indexing, bad code, whatever. I agree however, there are some serious security and accountability issues here.
On another note, I'm really sorry to hear that overseas companies have to deal with SOX. Or as I call it, "The Great Productivity Reduction Act of 2002." Charlie Rubeor Unix/Database Administrator Wiremold/Legrand 60 Woodlawn Street West Hartford, CT 06110 Tel: 860.233.6251 x3498 Fax: 860.523.3690 Email: [EMAIL PROTECTED] Internet: www.wiremold.com [EMAIL PROTECTED] wrote on 12/09/2005 09:27:50 AM: > You mean you don't separate them? Absolutely there needs to be a division > of labor here. As a developer I have no time to keep up with mundane > tasks as password verification, file resizing and maintenance, upgrades, > etc... That doesn't even touch on the security and accountability issues. > > In a small shop (< 50 users) you might be able to get away with combining > the two roles. But in any shop larger than that, I don't see how you > could effectively do both jobs. > > > Gordon J. Glorfield > Sr. Applications Developer > MAMSI (A UnitedHealth Company) > 301-360-8839 [demime 1.01d removed an attachment of type image/jpeg] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
