We can't make every developer constantly aware of the project as a whole, but we can make the decisions very clear and the structure very intuitive to use through the establishment of a common language that is shared inside the project. A developer who looks at a piece of unfamiliar code should be able to figure out what it does and where it belongs in the system's context as a whole, if they are familiar with the language used throughout the project. Even as a project grows in a domain and the language of the sub-domain becomes more pronounced and starts to focus more on the specific parts of the sub-domain it is used in, it is important to keep an overall structure in place. As a developer of one sub-domain, I should not feel lost looking at a separate sub-domain as the language of the overarching domain maintains a global context for me to follow.

We have been building a common language so far by taking words from the business domain and using them in the application...