-
@Selrahcd I needed to read your thread multiple times because you shared deep ideas condensed 🤣 Breaking the component into their small components, as you show here, makes total sense. If I was building BO CRUD logic with custom CRUD tooling, then it's when it didn't make sense.Permalink On twitter.com
Mood +1 🙂
-
@Selrahcd My thread came from the thinking of what people expect from Team Management. Their expectations are Product->Commodity, but right now the Application Team Management is behaving as Custom Build. Expected I guess when you start, but it can create customer frustration.Permalink On twitter.com
-
@Selrahcd That's when I wondered if I should replace that component with one off the shelf. Indeed, there's no product available in the market to be replaced with It needs to be custom-built regardless of the product evolution properties For sure, it's a Supportive Subdomain in DDD termsPermalink On twitter.com
-
@Selrahcd Which, by DDD definition, you might need to build-it because it's not available off-the-shelf 😥Permalink On twitter.com
-
@Selrahcd So far, I found an overlapping between #DDDesign and #WardleyMapping that can be misleading. If you put Wardley Maps next to Core Domain Chart can be more obviousOn twitter.com
-
@Selrahcd If you put them all together, you can "assume" that: 👉 Core Domain can be in Genesis-Custom Build Stages 👉 Supportive can be Product Stage 👉 Generic can be Commodity StagePermalink On twitter.com
-
@Selrahcd Indeed, I went a step further once and introduced what I think it was missing. The Emerging Domain in #DDDesign learnings.aleixmorgadas.dev/p/the-emerging-domainPermalink On twitter.com
-
@Selrahcd Influenced by #WardleyMapping mainly, DDD and WM can be combined as:Permalink On twitter.com
-
@Selrahcd Oversimplification, but my current way of thinking about the topic goes in this direction. WDYT? :DPermalink On twitter.com