Note: Please read the prerequisites carefully.
In this class, you will join Eric Evans and a small group of fellow participants to work on a real-world problem. There will be a domain expert from a complex domain. You will work with the group, lead by Eric, to interview the expert, create domain models, and design a solution. The class will simulate as closely as possible the way Eric runs design workshops with clients.
What will you learn?
Because it’s run as real world session, the outcomes are unpredictable, and there isn’t a fixed curriculum. Instead, you can expect to be immersed in solving a real problem, while observing Eric’s approach, learning his methods and heuristics for approaching problems as they arrive, seeing how he interviews experts, how he approaches knowledge crunching, and what mental tools he uses to find various solutions.
Prerequisites
This is an advanced class. You need to be deeply familiar with DDD terminology and methods.
To keep the level high, we require that the participants tick these boxes:
- You have experience working in a DDD environment and a complex domain.
- You have participated in domain modelling workshops.
- You’ve read “Domain-Driven Design” by Eric Evans
- You’ve taken a DDD class by known experts, such as “DDD Immersion” (Eric Evans), “Advanced Domain-Driven Design” (Mathias Verraes), “Domain-Driven Design Modelling Workshop” (Alberto Brandolini), "Implementing Domain-Driven Design” (Vaughn Vernon), “DDD for Messaging Architectures” (Mathias Verraes), “DDD Training” (Nick Tune).
If you are not deeply familiar with DDD terminology and methods, this class will not be a good fit for you.
Testimonials
I liked the practical approach during the workshop and the speakers did a great job working together. On the long term I plan to do more DDD professionally.
This workshop reinvigorates my interest in DDD and has given me a new perspective into how to model not just software systems but problem solving in general. I enjoyed spending time with real exercises and discussing the outcomes. Very useful to see the focus shift from high level to low level and back in the exploration of a problem domain. As a bonus we were getting insight into how Eric thinks and goes about software design.
