Quotes from 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.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“A model is a selectively simplified and consciously structured form of knowledge.”
― quote from 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.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“To communicate effectively, the code must be based on the same language used to write the requirements—the same language that the developers speak with each other and with domain experts.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“Every software program relates to some activity or interest of its user.”
― quote from 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.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“Knowledge trickles in one direction, but does not accumulate.”
― quote from 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.”
― quote from 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.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

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

“the model is not the diagram.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“The behavior of running code is unambiguous.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“documenting exclusively through code has some of the same basic problems as using comprehensive UML diagrams.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“A document shouldn’t try to do what the code already does well.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“Written documents should complement the code and the talking.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“you may hear the UBIQUITOUS LANGUAGE changing naturally while a document is being left behind.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“It takes fastidiousness to write code that doesn’t just do the right thing but also says the right thing.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“There is no need for explanatory models to be object models, and it is generally best if they are not.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“The astrolabe was a mechanical implementation of an object-oriented model of the sky.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“crucial discoveries always emerge during the design/implementation effort.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“If the design, or some central part of it, does not map to the domain model, that model is of little value, and the correctness of the software is suspect.”
― quote from 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.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

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

“The vital detail about the design is captured in the code. A well-written implementation should be transparent, revealing the model underlying it.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“there should be some learning when a domain model is discussed.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

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

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

“Simple, informal UML diagrams can anchor a discussion.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

“Any technical person contributing to the model must spend some time touching the code, whatever primary role he or she plays
on the project. Anyone responsible for changing code must learn to express a model through the code. Every developer must be involved in some level of discussion about the model and have contact with domain experts. Those who contribute in different ways must consciously engage those who touch the code in a dynamic exchange of model ideas through the UBIQUITOUS LANGUAGE”
― quote from 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.”
― quote from Domain-Driven Design: Tackling Complexity in the Heart of Software

Popular quotes

“nationalism will always produce at least one war each generation. It has done in the past, and I suppose we can rely on it to do the same in the future.”
― Aldous Huxley, quote from After Many a Summer Dies the Swan

“Every service had a price. Every object a value. If someone made you a sword, you paid him the appropriate amount or traded something of equal value with him. If a man saved your life, you either paid him the amount you considered that life worth, or you saved his in return. Until either of those things was transacted, you were in his debt. It was business. And if Balthazar believed in anything with religious fervor, it was that.”
― Seth Grahame-Smith, quote from Unholy Night

“This book tells the story of that moment in time. It is a story of high adventure set during the age of exploration—when Francis Drake, Henry Hudson, and Captain John Smith were expanding the boundaries of the world, and Shakespeare, Rembrandt, Galileo, Descartes, Mercator, Vermeer, Harvey, and Bacon were revolutionizing human thought and expression.”
― Russell Shorto, quote from The Island at the Center of the World: The Epic Story of Dutch Manhattan and the Forgotten Colony That Shaped America

“It was Hiss who won by stamping on another’s foot, and he spent the meal staring at Poppy and missing his mouth with his spoon.”
― Laini Taylor, quote from Blackbringer

“When a government becomes unjust, honor is often found among the lawless.”
― Brandon Mull, quote from Seeds of Rebellion

Interesting books

About BookQuoters

BookQuoters is a community of passionate readers who enjoy sharing the most meaningful, memorable and interesting quotes from great books. As the world communicates more and more via texts, memes and sound bytes, short but profound quotes from books have become more relevant and important. For some of us a quote becomes a mantra, a goal or a philosophy by which we live. For all of us, quotes are a great way to remember a book and to carry with us the author’s best ideas.

We thoughtfully gather quotes from our favorite books, both classic and current, and choose the ones that are most thought-provoking. Each quote represents a book that is interesting, well written and has potential to enhance the reader’s life. We also accept submissions from our visitors and will select the quotes we feel are most appealing to the BookQuoters community.

Founded in 2023, BookQuoters has quickly become a large and vibrant community of people who share an affinity for books. Books are seen by some as a throwback to a previous world; conversely, gleaning the main ideas of a book via a quote or a quick summary is typical of the Information Age but is a habit disdained by some diehard readers. We feel that we have the best of both worlds at BookQuoters; we read books cover-to-cover but offer you some of the highlights. We hope you’ll join us.