"Don’t introduce a 'deeper model' that you couldn’t convince a domain expert to use, no matter how elegant it seems." - Eric Evans

“Large Bounded Contexts risk model fragmentation. Breaking into ever-smaller Contexts risks losing valuable integration and coherency.”

"We are always fighting cognitive overload" Supple Design - pp246 DDD Quotes

“[Many small small improvements from refactors] fight entropy, and they are the frontline protection against a fossilized legacy.”

When creation of an object or Aggregate becomes complicated or reveals too much of the internal structure, Factories provide encapsulation.

“Versatility, simplicity, and explanatory power come from a model that is truly in tune with the domain.” — Eric Evans

“One feature [powerful] models almost always have is a simple, though possibly abstract, language that the business experts like to use.”

A deep model expresses lucidly the primary concerns of the domain experts' relevant knowledge while it sloughs off the superficial aspects.

A deep model usually has abstract elements, but it may well have concrete elements where those cut to the heart of the problem. —Eric Evans

“The Shared Kernel cannot be changed as freely as other parts of the design. Decisions involve consultation with another team.”

“If everyone makes decisions in a consistent way, the design will be more comprehensible. That's worth modest trade-offs on design choices.”

“Some of the most important insights come abruptly and send a shock through the project.”

Fight temptation to build frameworks and regiment the implementation of the large-scale structure. Structural rules should make dev easier.

The industry is shaking off excessive up-front design. Some see large-scale structure as a throwback to waterfall architecture. 1/2

But the only way to find useful structure is from deep domain insight. The practical way there is an iterative development process. 2/2

“Fearlessly rethink large-scale structure throughout the project. Don't settle early on, when you didn't understand the domain or reqs.”

Large-scale structures help teams to independently make harmonious decisions. They're loose conceptual guidelines and require discipline.

6 Essentials for Strategic Design Decision Making 1. Decisions must reach the entire team 2. The decision process must absorb feedback (...)

(...) 3. The plan must allow for evolution 4. Architecture teams must not siphon off all the best and brightest (...)

(...) 5. Strategic design requires minimalism and humility 6. Objects are specialists; developers are generalists