I meant that it's quite impossible to have a single coding standard that everyone sticks to. So it's everyone's responsibility to write code that's predictable in their own way. I think that's the message the OP's article wants to tell. For example in C# naming member variables is usually done by prefixing them with an underscore. If you don't like that then fine, but don't mix different prefixes around in different places of your program.

I was also a big advocate of strict coding stadards. I was nit-picking on every single curly brace and intendation and totally missing the big picture. Then I got into same realization as the blog's writer that the most important thing is to be consistent and get something delivered to the customer! Now I'm much happier without having to worry about the semicolon placements and all. I know that my teammates will do a good job :cool:

First of all I want to say I don't like the current "modern UI" trend that's going on. Everything seems to be getting too simplified and flat (and hard to use with a PC). But the new look for CP looks quite ok (after the first shock). I think it's the use of colors and non-flat icons from the previous theme. I think the old UI was a bit outdated and really needed to be changed. What I would do now is darken the background (my eyes are burning right now) and reduce the font size (who reads CP from a tablet anyway). Also the main page list of articles is very hard to read because there are no alternating list backgound color. But anyways, I think this is a good start for a better CP :thumbsup:

It's not "wiped out", it's just not set yet because the page is still loading. The asp.net events are a bit of a mess. You should try to get the books in the Load or LoadComplete events. And you should also check if you have EnableViewState set to false.