- Coined Domain Driven Design
- If you don't have a good abstraction, then don't use any abstract.
- The heart of software is its ability to solve domain-related problems for its user.
- It takes fastidiousness to write code that doesn’t just do the right thing but also says the right thing
- 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.
- documenting exclusively through code has some of the same basic problems as using comprehensive UML diagrams
- A document shouldn’t try to do what the code already does well.
- you may hear the UBIQUITOUS LANGUAGE changing naturally while a document is being left behind.
- Book - Domain-Driven Design: Tackling Complexity in the Heart of Software
- Book - Domain-Driven Design Reference: Definitions and Pattern Summaries