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)
• Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
• Android Architecture with Jorge Ortiz-Fuentes (Online Course on 22nd - 24th February 2021)
• Accelerated Software eXchange Forum (Online Conference on 18th February 2021)
• μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
• Evolutionary Architecture (SkillsCast recorded in January 2021)
• What an Architect Can Learn from Retrospective Failures (SkillsCast recorded in December 2020)