In the ever changing world of software development, there are times when you need to pick a set of standards/patterns/frameworks and just go for it, ignoring any newer developments and techniques that come along. The reason for this is that you want to establish a consistent predictable implementation that will allow for easier estimation and maintenance. If you were to adopt the latest and greatest during the development of a project you would end up with an inconsistent mess that is either difficult to understand or you would blow your timescales and costs.

Having completed one or two projects using your tried and tested standards you continue to ignore new developments and techniques in favour of predictable solutions. There is some merit in this as you can more accurately estimate the tasks associated with a given problem based on your past experience using your now standard methods.

While you work away with your standards, the world moves on adapting to the new. Eventually you realise that people around you are talking a different language with new terms and phrases. You're a dinosaur.

It's time to move on, catch up again and establish another new set of standards to use while building applications. I’ve just caught up with Domain Driven Design, using “.Net Domain-Driven Design with C#” by Tim McCarthy.