Re: Series: Coding Contentions: Naming Conventions

I was just talking about coding style with a few friends over the weekend, so you're defintiely not the only one thinking about.

These are the styles I use. I have no idea where I picked them up, but they're probably a mix of what was used at the various companies I've worked at, and what I find most intuitive.

I use camel case for variable names, with a prefix for the datatype. (ie, strUserName, iUserID etc).
Class-level variables are prefixed with an underscore (ie, _strConnectionString).
Interface class names are prefixed with an 'I' (ie, IUserRepository). We had a bit of a debate about whether this made any sense, but I've just gotten so used to it that I can't remember the original reasons I started. I do like being able to tell from the class name though whether or not it's an interface.

As far as syntax, I vastly prefer to have braces on separate lines. I know there's a name for that style, I just can never remember it.
if (null != user)
{
//do something
}
as opposed to
if (null != user ) {
//do something
}

The main reason I prefer this is that when scanning down a code listing I find it much easier to break up the code into logic units (ie, control flow paths).