If you have been following DDD for some time you are probably familiar with the common obstacles that keep many from implementing the practices that Eric Evans made famous. It's not that the benefits of this development pattern are not inherently obvious. I've had more than my share of conversations with other developers who admire what Eric Evans laid out in his classic book Domain-Driven Design: Tackling Complexity in the Heart of Software. Yet so many ask themselves, where do I begin? How do I get my manager, boss, client, etc to agree to adopt these practices? What will this mean for my legacy code?
Vaughn Vernon is currently traveling the world delivering the answers to these very questions. In fact that is the very topic of his recently released book, Implementing Domain-Driven Design. If you haven't yet checked this book out you should.
|Implementing Domain-Driven Design By Vaughn Vernon|
As I have been presenting to various groups in the past year, developers must make a commitment to raise our level of work. In the never ending quest to sharpen our skills as developers, it is important to exercise our curiosity. By learning to implement Domain-Driven Design, we can take our development to a higher level.
If you are developer, what are you doing to demonstrate your commitment to make continued progress as a programmer?