Quotes from Eric Evans

The indirectness of communication conceals the formation of schisms—different team members use terms differently but don't realize it.

By using the model-based language pervasively and not being satisfied until it flows, we approach a model that is complete and comprehensible, made up of simple elements that combine to express complex ideas.

Tightly relating the code to an underlying model gives the code meaning and makes the model relevant.

The complexity of a highly detailed interaction ends up being handled in the application layer, allowing domain knowledge to creep into the application or user interface code, where it is lost from the domain layer.

The goal is that not only can a developer understand what the code does; he or she can also understand why it does what it does and can relate that to the ongoing communication with the domain experts.

Complex object creation is a responsibility of the domain layer, yet that task does not belong to the objects that express the model.

This tight coupling of the application to the specifics of the implementation strips away most of the benefits of abstraction in the domain layer and makes continuing changes ever more expensive.