Business Logic Is a Magnet for Complexity

While our code has to implement the necessary complexity, it can often be even more complex due to our decisions about how the logic gets implemented. For example, we may choose to manage user accounts in another application and make API calls to it. We didn’t have to do that, and our domain doesn’t require it, but it might be just the way we ended up building it. This kind of complexity is called accidental or unnecessary complexity.

We can never avoid all accidental complexity, but the distinction to necessary ...