Quotes About Domain

The room you are about to enter," the Eagle said, setting up Nicole's wheelchair, "is the largest single room in this domain. It is half a kilometer across at its widest point. Inside currently is a model of the Milky Way Galaxy.

Real genius is nothing else but the supernatural virtue of humility in the domain of thought.

Experts'] knowledge is not simply a list of facts and formulas that are relevant to their domain; instead, their knowledge is organized around core concepts or 'big ideas' that guide their thinking about their domains,

They seem to have forgotten that, and are back saying the only purpose of P2P networks is for illegal trading of owned goods. We claim part of the reason for P2P is for legal trading of what ought to be in public domain. And what is in public domain in many cases.

Humour is the only domain of creative activity where a stimulus on a high level of complexity produces a massive and sharply defined response on the level of physiological reflexes.

The heart of software is its ability to solve domain-related problems for its user.

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.

there should be some learning when a domain model is discussed.

Listen to the language the domain experts use. Are there terms that succinctly state something complicated? Are they correcting your word choice (perhaps diplomatically)? Do the puzzled looks on their faces go away when you use a particular phrase? These are hints of a concept that might benefit the model.

That shallowness of knowledge produces software that does a basic job but lacks a deep connection to the domain expert's way of thinking.

In general, don't fight your frameworks. Seek ways to keep the fundamentals of domain-driven design and let go of the specifics when the framework is antagonistic.

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.

The domain model will typically derive from the domain experts' own jargon but will have been "cleaned up," to have sharper, narrower definitions.

Persistent use of the UBIQUITOUS LANGUAGE will force the model's weaknesses into the open. The team will experiment and find alternatives to awkward terms or combinations. As gaps are found in the language, new words will enter the discussion. These changes to the language will be recognized as changes in the domain model and will lead the team to update class diagrams and rename classes and methods in the code, or even change behavior, when the meaning of a term changes.

The domain experts had learned more and had clarified the goal of the application.

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.

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

Because the domain experts are feeding into it, it reflects deep knowledge of the business and those abstractions are true business principles.

Business activities and rules are as central to a domain as are the entities involved; any domain will have various categories of concepts.

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.

People often ask me if my parents helped me. My mother did lend me $10 to register the domain name.