Link Dump #213

I know I do not have to convince you to read but remember that reading improves your focus and memory :)

Core, Supporting, Generic – How to Stop Treating All Domains the Same

Most businesses require knowledge from multiple domains to be successful. Some are essential due to the nature of the business itself, others are mandated by legal regulations and compliance obligations, and some exist simply to meet specific operational requirements.

After the last series of articles, you already know how to identify those domains. But what comes next? Once we define all domains, it’s worth categorizing them. This exercise helps us later make better software architecture decisions and organize teams more effectively.

Link Dump #212

I've got enough reading - said no one ever.

The Hidden Architecture of Words — Ubiquitous Language Uncovered

Over the past weeks, I’ve been diving into one of the cornerstones of Domain-Driven Design — Ubiquitous Language. It’s not just about naming things right. It’s about creating a shared language that bridges business and technology, reduces misunderstandings, and makes complex systems easier to reason about.

To make the idea practical, I’ve prepared a short series that walks through it step by step — from understanding what Ubiquitous Language really is, to finding it in your domain, and finally applying it in action.

Link Dump #211

Another Friday, another coffee, and more articles to read. Routine does not have to be boring:

Ubiquitous Language in Action: Boundaries Made of Words

You already know what the Ubiquitous Language is and how to define its boundaries. Equipped with that knowledge, let’s return to the Training Center example and clarify what domains and corresponding ubiquitous languages we have.

Link Dump #210

Friday is the perfect day for the reading mood: