[pydry]

^^ These are the kinds of questions DDD has very vague answers to IME. It handwaves about all of the most critical aspects of software development.

It's very specific that, for instance, your domain model "should only be created by factories", though.

It's all a bit bikesheddy.

[rapnie]

DDD provides insights to understanding how a business works for people who are not domain experts themself, and are tasked to translate business requirements to code. This insight helps make appropriate decisions about those "most critical aspects of software development", nothing more, nothing less. Whether you use factories or not is a much lower-level technical decision far removed from the essence and rationale of 'doing DDD'.

[pydry]

>Whether you use factories or not is a much lower-level technical decision far removed from the essence and rationale of 'doing DDD'.

shrug maybe im reading all the wrong things but IME most DDD discussions, blog posts and books sound more like this:

https://stackoverflow.com/questions/555241/domain-driven-des...

And few delve into the real "essence" as you put it.

Event storming is one of few times, but it doesn't seem to be a core part of DDD and i found the outcome to be underwhelming.

[rapnie]

That SO article if from '09 when 'big OOP' was all the hype. Hyping things to bigger proportions than they should be are a problem in IT. We just saw it for 'Microservices', for instance. These hypes serve to overpromise what you'll get, and sow confusion for years to come. In that regard I hope that DDD will not climb the hype cycle again, and we'll stay calm and just use what works.

I think most important to realize that DDD is just another tool in your toolbox, and can be used alongside all / most of the other tools you already use. Event storming can be a nice way to quickly kick off the elaboration process, should the method appeal to you.