DDD Europe 2019: Putting it all together

Slides from my presentation at DDDEurope 2019. The slides mostly acted as visual support so do NOT expect anything of it.

Transcript

1. Putting it all together
2. !
3. Where to start?
5. 1 minute List 3 things that would keep you from putting it to work on Monday
6. "
7. Domain Tech People
8. Domain should be the primary focus
9. #$%&
10. No expert
11. '
14. Feature: Buy ticket As a consumer I want to buy a ticket online In order to gain access to an event Scenario: Sufficient tickets available Given tickets are on sale for an event When I order two tickets by entering information in the reservation form Then two tickets should have been reserved And the amount payable should have been charged on my creditcard Scenario: Insufficient tickets available Given tickets are on sale for an event But all tickets have been reserved When I order two tickets by entering information in the reservation form Then I should see a message that tickets are no longer available
17. Whatever you do, it’s about the idea behind the form
18. "
19. Embrace Change
21. Tactical patterns Strategic design
22. (
23. class Currency {} class Amount {} class Money { construct ( Currency c, Amount a ) {} }
24. ( ♻
26. <insert promo for IDE and refactoring> <add discount code here>
28. Missing Concept
29. Emergent Boundaries
30. Conceptual Contours
31. Evolving Order
32. Beware of overstructuring
33. *
35. Domain should be the primary focus
36. '
37. Every decision should be in service of domain focus
38. + Log your decisions in a non-boring format
39. + Clarify the goal
40. Do NOT get stuck in your “approach” of doing things
41. + Reflect often
42. Domain-Driven Design principles should be used to tackle complexity where it matters
43. + What is your core domain?
44. The process isn’t linear
45. + Cultivate some chaos in your process
46. Thank you, Marijn Huizendveld marijn.huizendveld.com