Discover and read the best of Twitter Threads about #madquestionasking
Most recents (4)
one way to look at it is that #domainDrivenDesign is the union of technical #objectOrientedDesign tightly coupled with subject matter expertise, business analysis and modeling. #ddd is #ood with soul. #ddDesign is #ooDesign done right
in complex systems, or enterprise development
different people/teams may have different
povs/ models/ experiences/ conceptualization/ understandings
of the subject matter or problem to be solved, and ...
👇🏾
different people/teams may have different
povs/ models/ experiences/ conceptualization/ understandings
of the subject matter or problem to be solved, and ...
👇🏾
they dont realize that there are these different povs; and even if they do,
they dont see the danger of coding to different concepts as long as it "works"; so inevitably ...
👇🏾
they dont see the danger of coding to different concepts as long as it "works"; so inevitably ...
👇🏾
whats the model in #domainModel?
the pov/ understanding/ comprehension, way of looking at the domain
the pov/ understanding/ comprehension, way of looking at the domain
whats modeling in #domainModeling?
learning about the model by way of discovery techniques like #knowledgeCrunching (like number crunching); event storming; basically asking a ton of questions #madquestionasking; and then capturing the model in some form of living documentation
learning about the model by way of discovery techniques like #knowledgeCrunching (like number crunching); event storming; basically asking a ton of questions #madquestionasking; and then capturing the model in some form of living documentation
one of the best parts of development, even more fun than solving algorithmic riddles, is
discovering and turning new or hidden concepts into objects, along with the relationships between it and other objects (pieces of data and behaviors on data)
#ddDesign
discovering and turning new or hidden concepts into objects, along with the relationships between it and other objects (pieces of data and behaviors on data)
#ddDesign
or as E.Evans put it in the blue book - making implicit concepts implicit
it's fun, but it takes effort from devs and subject matter experts collaboration to make it happen. takes a culture of patience, curiosity, flexibility to mine for these implicit concepts out of the ubiquitous language
when you first look at the model, it's a fluffy brown pillow
through the process of modeling you find out it's a hibernating grizzly
this is the importance of modeling i.e. constant refactoring of the comprehension of the domain via knowledge crunching #madquestionasking
through the process of modeling you find out it's a hibernating grizzly
this is the importance of modeling i.e. constant refactoring of the comprehension of the domain via knowledge crunching #madquestionasking
you save yourself from building a solution based on the understanding of a pillow, when what the customer really needed was ... whatever you safely handle hibernating bears with?
a good understanding of what youre supposed to code for i.e. the model
1) captures core concepts of the subject matter
2) discards the irrelevant fluff
we achieve it thru asking a lot of questions, having many convos with subject matter experts
why? to produce better code
1) captures core concepts of the subject matter
2) discards the irrelevant fluff
we achieve it thru asking a lot of questions, having many convos with subject matter experts
why? to produce better code
