Hacker News Reader

> I’m reading Domain Driven Development and learning why so many of my projects have been tough to maintain.

Because they didn't take advice from that book or because they DID take advice from that book?

The former. I didn’t realize how few of my projects have even had an intentional architecture. So often they go from feature designs to mockups to tickets to code without any real discussion about how the pieces fit together. There’s certainly never been an attempt to create a common “language” that is shared across the org. On a project half the company might refer to a catalog item as a “product”, and their definition may or may not align with what another team refers to as an “item”. I’m starting to understand that situations like that are why everything gets so complicated.

Reply on news.ycombinator.com