What programming or naming conventions have you come across that really rub you the wrong way?
For those that aren't aware, in C# we can wrap blocks of code with a #region directive, which allows you to collapse these blocks in Visual Studio for readability.
So the convention on this team is to wrap all combinations of access modifier in their own region. Every time I open a file I'm presented with something like:
+ #region private constants + #region private members + #region private statics + #region public properties + #region static constructor + #region private constructor + #region public properties + #region protected overridden methods + #region internal methods + #region private methods
Well that's great, but where's the method that maps the message response onto our object? Is it an internal method, or a public one? Why does the private members region only have one member, turning one line of code into three? Why add a region to describe something that is self descriptive?
Maybe I'm just having a bad day...