Keynote: Getting to DDD: Pragmatic or Principled?

Please log in to watch this conference skillscast.

Domain-Driven Design is a vast topic. There are so many wonderful concepts, philosophies, patterns, practices and techniques to learn and benefit from. Some of the best minds in the industry have been tuning these practices for years to ensure developers are able to implement proven, successful approaches to software design.

Domain modeling in particular is very specific with guidance on designing and coordinating the dance between the myriad moving parts in our system. Yet learning the principals of DDD can be daunting for developers who are new to DDD.

To encourage and enable more developers to get on the path of DDD, is it reasonable to allow a more pragmatic approach over a principled approach of adhering strictly to DDD guidelines?

Should developers be encouraged to start with low hanging fruit which they can quickly benefit from in their software projects while they continue to learn, to gain a deeper understanding of Domain-Driven Design in order to evolve and adapt their practices as they move closer and closer to the beauty we all know that can be achieved with DDD.

YOU MAY ALSO LIKE:

• Keynote: A Hitchhikers Guide to Growing Your Tech Skills (SkillsCast recorded in September 2017)
• Domain Models in Practice: DDD, CQRS & Event Sourcing with Marco Heimeshoff (Online Course on 30th November - 4th December 2020)
• Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 7th - 8th December 2020)
• Lightning Talk: Specification as a Library (SkillsCast recorded in October 2020)
• Implementing Microservices: Nobody Told Me About That (SkillsCast recorded in October 2020)