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.
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.
[ reply ]