I follow SOLID, I code to interfaces, I loosely couple things, I write tests, and I feel good. But when it comes to maintaining things, when things go bump and I need to figure out stuff, I feel betrayed. <- Has this happened to you?

My code is domain driven, I use BDD, I'm a Moq ninja, I know by heart what Windsor Facilities are. But hang on - why do I get the feeling that I'm going through the motions? Is all my code just boilerplate? And when I try to make sense of what's going on, why do I find myself in a reflection induced coma? <- Has this happened to you?

Many practices we have are inherited. Our view of what's good is given to us by those we look up to. We learn some methodologies, and techniques, and then try to apply them in other scenarios. Techniques applied in inappropriate scenarios cause more issues than they solve.

In this session, I'll put forward some of these "best practices", and show common misuses. We'll cover some high level things like DDD, bounded contexts, and Value Objects. We'll also look at code - when to code to interfaces, when to mock/stub/fake, and again Value Objects.

Disclaimer: This session may make you question your loyalty to certain sacred cows.