Status Updates From Implementing Domain-Driven ...

funny enough, the first 100 pages of this book describe the exact modeling scenario i’m dealing with at work 💀 the author is dead on!

kms

he usado toda mi capacidad neuronal para aguantar 10 paginas mas

ugggggggggggg

Me quede aqui la ultima vez q leí..... Sacadme de aqui

"Scrum was not meant only as a means to keep Gantt chart enthusiasts happy. Yet, it
has become that in so many cases."
JAJJJJ

"I made a conscious deci-
sion to use Java instead.
First of all, and sad to say, I think there has been a general abandonment
of good design and development practices in the Java community. These days
it may be difficult to find a clean, explicit domain model in most Java-based
projects. It seems to me that Scrum and other agile techniques are being used
as substitutes for careful modeling,"
es cierto.

Quite dry and repetitive so far.

The book is written in a way that just doesn’t work for me and I believe for many others. It decided to start with the opposite approach of the blue book. Namely by putting the tactical patterns at the end. That would be ok if the author would teach the reader about the yet unknown topics

In chapter 7 about services he plain simple says “If you’re confused about the difference, compare with Application (14)”

Written in a lengthy style often with marvel cowboy logic. I recommend reading the DDD, compact instead.

Pbbt

Honestly, it’s kind of condescending

hard to read, especially with the cowboy logic.

The DDD compact is a smaller and better approach. Use the Implementation as reference for additional details.

Well organized and interesting to read. Offers many points that can be put into practice immediately. Examples are well designed and concise. Clarified many unanswered questions I still have after reading the other book Patterns, Principles, and Practices of Domain-Driven Design.

Like!

Not technically finished; but up through Appendix A.

Awesome. Every serious developer should read this.

Event Sourcing makes me giddy.

Strong argument to be made that a properly implemented MVC is just another Hexagonal architecture.

Doubled back. But made some progress.

Got some catching up to do with the book club.

Got some catching up to do with the book club.

Awesome book so far.

It's like walking in the mud up to your knees

I found the introductory material very engaging, and the focus on finding a common language between the business and technical sides rings true. However, I found the later parts of the book were less generally applicable. I think the details of how to implement DDD in a given environment and tech stack could vary quite a bit.

The unfortunate side of DDD literacy is that it is very heavy and thus slow to read.

Third chapter gave a little better understanding of Context Maps. But is definitely a chapter I need to read again.

Second chapter was a very good explanation of how to look at your Domain, and how to split everything into smaller separated Subdomains. And great timing, I can definitely use this already this weekend :)

First chapter is a great introduction to DDD, when, where and why to use it. Looking forward to reading on.

The unfortunate side of DDD literacy is that it is very heavy and thus slow to read.