I found the original book to be rather dry and difficult to read. Like most books on software design. It’s full of hand waving and folk tales.

However I think there are some good nuggets in it that are worth taking away and using. The idea of ubiquitous language is useful. The best software teams I’ve worked on were great at talking with business users and customers. A ubiquitous language helped us avoid “programmer speak,” where we talked using names for things nobody had heard of but us and nouns and concepts nobody else understands. It allowed us to communicate more precisely and avoid mistakes throughout the process.

Good article. There’s always going to be counter-points and folks who prefer one way over another. I think there are some useful nuggets in this one too.