My beef with "modern" design and modeling techniques is that they've become the center of attention, not in the least by their proponents. If you can't concede that it is a means to an end and that what you are modeling is more important than your petty modeling technique, than I have no use for it.
I've said it before, but I'm fascinated by how thinking in terms of Event Sourcing almost inevitably leads you to the Actor Model, and to re-evaluate what you thought you knew about OOP.
This talk is a must-watch for people in the Event-Driven space. I saw @noctovis.bsky.social giving it live at this year's DDDEU, and I truly believe that she nailed the versioning topic 👇🙂
www.youtube.com/watch?v=6TCb...
Fantastic one, indeed. Thanks for sharing!
From an engineering perspective, software wants to be decoupled. From a business value perspective, software wants to be deeply interconnected. That's the fundamental friction that software design, and Domain-Driven Design specifically, attempts to address.
