But as the project proceeded, any of us could take terms straight out of the model, organize them into sentences consistent with the structure of the model, and be unambiguously understood without translation. (link)
Creating a lucid model that cuts through that complexity is exciting. (link)
This book will show that domain development holds opportunities to cultivate very sophisticated design skills. (link)
Domain work is messy and demands a lot of complicated new knowledge that doesn’t seem to add to a computer scientist’s capabilities. (link)
Developers have to steep themselves in the domain to build up knowledge of the business. (link)
The heart of software is its ability to solve domain-related problems for its user. (link)
It is not just the knowledge in a domain expert’s head; it is a rigorously organized and selective abstraction of that knowledge. (link)
A model is a selectively simplified and consciously structured form of knowledge. An appropriate model makes sense of information and focuses it on a problem (link)
And although fear of unanticipated requirements often leads to overengineering, the attempt to avoid overengineering can develop into another fear: a fear of doing any deep design thinking at all. (link)
When complexity gets out of hand, developers can no longer understand the software well enough to change or extend it easily and safely. (link)