In the previous Chapter 1, Why Domain-Driven Design, we discussed the importance of language briefly. In the software industry, we developed this naive perception that the only languages that matter are programming languages. This is why too often we speak complete gibberish and our colleagues from other departments, or our customers, are having a hard time understanding what we are trying to say. This issue is mutual because many lines of business have developed their own jargon, which other people might not completely understand.

In this chapter, we are going to go deeper into the importance of language and go through several examples of mockups and code. We will also get into the concept of language in a context and introduce the ubiquitous language, one of the most critical aspects of Domain-Driven Design (DDD).

In this chapter we will go deeper into the following topics:

• Why language is important
• Making implicit explicit
• Ubiquitous language
• Language in context
• Expressing the behavior