#ddDesign

Domain-Driven Design continues to gain in popularity, and for good reason. Learn the fundamentals of this approach to software development in this popular Pluralsight course: #dddesign

After a few months of work, I finally managed to publish the first version of my new project - a *real* #Modular #Monolith system using the #DDDesign approach. Check it! #softwarearchitecture #softwaredesign #dotnet #dotnetcore #desginpatterns

When learning about Value Objects in Domain-Driven Design, I often turn to the .NET DateTime type as an example most developers have used. #DDDesign #dotnet

Struggling with splitting user stories? Here’s a printable ref guide for #DDDesign teams

Together with the rest of DDD Crew we put together a "Domain-Driven Design Starter Modelling Process". If you are not sure how to apply #DDDesign at your own company, then it's a resource that will help you start! Feedback and PRs welcome!

So @ddd_eu published my lightning talk "No, you don't need to access my data" from last year edition, and I look like an angry castaway. But maybe I had something to say! It's 7 minutes. #DDDesign #CQRS

I may be writing a book on #DDDesign. Which topics that perhaps aren’t already well covered by @ericevans0, @VaughnVernon, @ScottWlaschin, @ScottMillett, @ntcoding, @Zimareff, @JimmyNilsson, @martinfowler, @mathiasverraes, et al, would you like me to cover? RT appreciated! 🙏🏼

No, Strategic Design is not the use of the Strategy design pattern. And, no, DDD is not an architecture style even if someone with a bazillion followers says it is. #dddesign

I must be the only person doing #DDDesign who doesn't really care about Aggregates. Beginners often get stuck on this concept instead of enjoying the more accessible and powerful concepts of contextualized languages and value types.

Learn #DDDesign directly from it’s creator @ericevans0’ in his new video series

🖼️Domain-Driven GraphQL Schema Design (in 6 tweets)👇 #graphQL #eventstorming #dddesign

A Bounded Context is not a purely logical (language consistency, unity of purpose) or physical (code separation, deployment unit) concept. It's an obligation to maintain integrity between those views. #DDDesign

Blogged: "DDD is expensive" is a myth #dddesign #programming #coding

For software development to be more successful, communication is critical. Yet, I now use *dialogue* instead. Communication can be oneway: giving instructions such as "Command and Control." Dialogue is explicitly collaborative. Communicate collaboratively with dialogue. #DDDesign

One of the worst mistakes that people make is trying to get approval for using #dddesign. If you are doing it right, you shouldn't have to ask permission or get backing for #dddesign. Really. Most enterprise software could make major strides forward just by replacing the primitive obsession (many extraneous attributes or properties) in entities. That is, compose value objects with attributes that belong together: String streetAddress1; String streetAddress2; String city; String stateOrProvince; String postalCode; Blah blah; Refactor these into a whole value: public final class PostalAddress { ... } Now you can test PostalAddress and you can test what uses PostalAddress. And when something changes in PostalAddress, you replace the whole PostalAddress--even when changing just one attribute. Seriously, who would possibly complain about that? Okay, someone will definitely complain, but it doesn't mean they are smart, reasonable, or correct. This baby step--one entity at a time--will greatly raise the quality of your code and increase team knowledge. Is this "full-blown DDD"? No, but it is iterative improvements. Once your quality and knowledge increases, take the next small step. Again, if you are doing it right, you don't even refer to what you are doing as #DDD. Just ask people who know what attributes belong to the same concept, and test/refactor/test. Many such decisions can be determined by using your own gray matter. You can even study the existing source code to understand what changes together. If 2+ attributes change together, they are probably related and belong in the same value type. (Except for the 35+ attributes that are all set together in a saveSomeHugeEntity() application service method). Another but different place to start is in modularizing code per business concept cohesion. The primary point is, the less people that you tell the better. Just do it and tell them later when you can prove that it worked and that your team benefitted.

Blogged: DDD is not programming #dddesign #developers #programming

A curated list of #DDDesign resources:

#dotnet developers thinking they're abstracting their data access with IQueryable... #DDDesign

#dotnet developers thinking they're abstracting their data access with IQueryable... #DDDesign

New tale in which we deal with organising Grandma's birthday. What is a named space? What does "1" mean? Why information is mean? #dotnet #dddesign #SoftwareEngineering #SoftwareDevelopment #java #typescript #Software