Domain-Driven Design Quotes

“They show design constraints, but they are not design specifications in every detail. They represent the skeletons of ideas.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“Diagrams are a means of communication and explanation, and they facilitate brainstorming. They serve these ends best if they are minimal.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“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.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“The effort of translation prevents the interplay of knowledge and ideas that lead to deep model insights.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“The indirectness of communication conceals the formation of schisms—different team members use terms differently but don’t realize it.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“Translation muddles model concepts, which leads to destructive refactoring of code.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“Business activities and rules are as central to a domain as are the entities involved; any domain will have various categories of concepts.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“The kind of knowledge captured in a model such as the PCB example goes beyond “find the nouns.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“The domain experts had learned more and had clarified the goal of the application.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“When we set out to write software, we never know enough.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“That shallowness of knowledge produces software that does a basic job but lacks a deep connection to the domain expert’s way of thinking.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“Knowledge trickles in one direction, but does not accumulate.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“In the old waterfall method, the business experts talk to the analysts, and analysts digest and abstract and pass the result along to the programmers, who code the software. This approach fails because it completely lacks feedback.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“Every software program relates to some activity or interest of its user.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“The heart of software is its ability to solve domain-related problems for its user. All other features, vital though they may be, support this basic purpose. When the domain is complex, this is a difficult task, calling for the concentrated effort of talented and skilled people. Developers have to steep themselves in the domain to build up knowledge of the business. They must hone their modeling skills and master domain design. Yet these are not the priorities on most software projects. Most talented developers do not have much interest in learning about the specific domain in which they are working, much less making a major commitment to expand their domain-modeling skills. Technical people enjoy quantifiable problems that exercise their technical skills. Domain work is messy and demands a lot of complicated new knowledge that doesn’t seem to add to a computer scientist’s capabilities. Instead, the technical talent goes to work on elaborate frameworks, trying to solve domain problems with technology. Learning about and modeling the domain is left to others. Complexity in the heart of software has to be tackled head-on. To do otherwise is to risk irrelevance.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

“Success comes in an emerging set of abstract concepts that makes sense of all the detail. This distillation is a rigorous expression of the particular knowledge that has been found most relevant.”
― Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software