RE: .Net and security

"Michael Silk" <[email protected]> Thu, 25 Nov 2004 09:29:25 +1100
Newsgroups gmane.comp.security.programming
Message-ID <22342395A9909442AF5AF5E2ED850CF7EC04E6@mercury.internal.phg.com.au>
Hi,

	That is not the way it is here ... My co-worker is consistently
telling me "but Microsoft does it this way ..." and refuses to discuss
alternatives. The problem being the environment in MS is totally
different from our own so most of the development strategies are not
appropriate.

-- Michael 

-----Original Message-----
From: Damhuis Anton [mailto:[email protected]] 
Sent: Wednesday, 24 November 2004 4:57 PM
To: [email protected]
Subject: RE: .Net and security


Hi Craig

From your email
> >I find that many programmers blame their bad coding practices on
Microsoft.


Why would you say "blame their bad coding practices on Microsoft"?

If referring to the "best practice"
Surely, one should not blindly follow any "best practices", but rather
analyze why it is a best practice, understand it and then only implement
it. And make a note where the best practice was not adhered to.

But if blaming it on MS, it sounds more like not wanting to take
ownership of a problem. (I am speaking in very general terms)

Also the lead programmer / team leader / technical architect should
review the code and make recommendations.

Regards
  Anton

Confidentiality Warning
=======================
The contents of this e-mail and any accompanying documentation are
confidential and any use thereof, in what ever form, by anyone other
than the addressee is strictly prohibited.




**********************************************************************
This email message and accompanying data may contain information that is confidential and/or subject to legal privilege. If you are not the intended recipient, you are notified that any use, dissemination, distribution or copying of this message or data is prohibited. If you have received this email message in error, please notify us immediately and erase all copies of this message and attachments.

This email is for your convenience only, you should not rely on any information contained herein for contractual or legal purposes. You should only rely on information and/or instructions in writing and on company letterhead signed by authorised persons.
**********************************************************************