Let me start of by publicly admitting this, I am have OCD (Obsessive-compulsive disorder) when it comes to code. My code must be clean and it must be uniform. And because I am a ReSharper lover my disorder is even more drawn out. Over the past month or so while I have been fixing bugs in our application...

In my humble opinion the worst code smell you can have is Dead Code.  I know that other smells such as large methods, large classes, overly complex logic, interwoven dependencies, etc are all smells, but nothing, I MEAN NOTHING smells worse than dead code.  Let me explain. **** BTW, I am not...

There was once a time where I did not care about compiler warnings, but times have changed.  In fact, I remember having a debate with a fellow developer some time ago about why compiler warnings were not that bad..... Oh how times have changed. In my opinion (my changed opinion) compiler warnings...

Ok, so I know this is a odd question but I am stumped. Normally when I have a private instance level variable that is exposed via a property I format my class file as such. { ..... all instance variables ..... any constructors ..... any public/private/protected methods ..... any properties } Now that...

Over on the Alt.Net mailing list ( here ) the topic of where to put your unit tests was the hot topic a few days ago. This is a topic that I have debated with various people over the past few years. With all the debates I have had, it is clear to me that there really is no right or wrong way do to this...

<disclaimer> This posting is purely my personal opinion. I am sure many of you out there will disagree, if this is the case, let me know. </disclaimer> Today, during my bug hunting I stumbled across the dreaded 'Null reference' exception. This was not the original target of my hunt...

Before I get started, I personally am a fan of using #regions in my code.  I think it cleans up everything, allowing me to only see what I want to see.  I also know that many of you disagree with me, and that is fine. Here are 2 posts that voice their disapproval for regions if you are interested...

Sorry we have interrupted your daily blog reading, but we have a special service announcement for all developers. <SpecialServiceAnnouncement> Only make properties public on an object when you KNOW they are needed. Please make all properties private by default. If you need to access the property...

Today I was refactoring some sql procs along with the corresponding .net code that called the procs. My primary focus was to implement some new business rules (ways to get totals) in the proc.  In doing so, I completely re-wrote the proc.  In the end the return values (column names) were the...

Pretty much any developer with half a brain (or any real world experience) knows that you MUST keep your source code in some sort of source code repository. There are many of them out there, VSS, Vault, TFS, CVS, SVN, the list goes on. If putting your code (C#, C++, VB, etc) into a source control system...