Let’s imagine your typical code.

We all want to experiment on the latest thing, technology or OSs. Often times we move to another flavor of operating system because we get bored or just want a new shiny view.

Imagine you have a todo project. You have this in your code to get a todo and check if it’s due today:

In Domain-Driven Design, an entity’s constructor is a sacred thing. It really means a new domain object. For example: When the Employee class is initialized, it’s tagged as newbie automatically to protect our invariants and avoid invalid state for this domain. Here, we can be sure that calling the constructor...

It’s about modeling the domain to reflect the intent of the business without the complexity of technical solutions. DDD is not all about how to write or implement and use design patterns in your code, it’s more on solving domain problem in an explicit sense that all stakeholders can understand...