2 ms·
> if the terminology in your code is different than the terminology of your domain that it’s a code/design smell. Hence the idea/label of Domain Driven Design
by Terr_ 7y ago
> if the terminology in your code is different than the terminology of your domain that it’s a code/design smell.
Hence the idea/label of Domain Driven Design [0].
IMO like unit-testing it's valuable but you can't hope for 100%. There will always be some concepts that are unique to how the data is being packaged or calculated which aren't part of the business-domain, but hopefully they'll be safely locked down beneath domain-centered abstractions.
[0] https://en.wikipedia.org/wiki/Domain-driven_design https://en.wikipedia.org/wiki/Domain-driven_design