And we are not talking about meeting your political family, or that moment of hesitation before writing the first test of a class. I am talking about deployment to a whole new different environment. I am talking about the pressure of the client to show everyone and their cat why they had spent so much money to replace an existing working system. I am talking about deployment to the live environment.
This one caught me by surprise (again).
Type equality should be easy, right? I pointed to the rules before. But add implicit conversion magic and you are ready for trouble. Let's visit some pieces of the advice when implementing .Equals():
Today I was working in getting some information out of custom attributes which decorated enumeration values. It turns out that those values are nothing more than fields (Nay!! go on reading). And since getting information out of an attribute uses reflection techniques and we all have been told millions of times since it was invented that "reflection is slow" and being a relatively high-frequency used feature, I jumped onto adding caching to it.