What is DDD - Eric Evans - DDD Europe 2019 

Pmy no uno menh

Many thanks mate.

Thanks man, + nice indentation

many thanks!

best comment in youtube technical talks. Your indentation was genius. 😻😻💌💌💘💘💝💝💖💖💗💗💓💓

What is the fuss about? Some uml-modeling and a little "philosophy" ?

@Oscar Bardrick such mundane things that many (most?) developers don’t really get?

It was a great talk.

Thanks!

Xxx

because DDD is a useless fad, what you guys used is common sense.

@@debasishraychawdhuri I don't think it's a fad. It's just one of many methods/techniques to build software better.

@@debasishraychawdhuri Any tool can be abused.

@@debasishraychawdhuri looks like you haven't built anything outside simple REST application during the time of your comment.

Exact case for me

Good call.

@@MaximilianBerkmann l

2x

So I just lost half an hour of my life because I didn't came down here before start watching hahaha.

@@ezp721 I recommend installing Video Speed Controller extension. It allows finer control over what RU-vid offers. I generally watch videos at 3x speed, this one I watched at 2.5x because I wanted to focus on it.

I think you got the concept behind the examples so he made his purpose. The probe of that is you are right and for his purpose realism is a distraction like he said.

I also missed the part where Stop and Leg had different properties so I was very confused about their interchangeability not being equal.

Itinerary is the object that has the legs or the stops, and itinerary is a synonym of "route"

@@GammaStrobe Although it is tempting to use synonyms, using itinerary is better, if that is what people in the domain are used to. Leg/Stop are different from route. Leg is a part of route and stop is technically not part of route. There might be some business process between each unload and load at a stop. Depends on what problem you are trying to solve as he says :)

You are using at a very reductionist description of what DDD proposes, but I get how it's "actionable" insights can be interpreted just as that. Have in mind that DDD is a set of guiding principles that presents tools since the code level (you may have heard about value objects) up to a strategical level (when designing teams around bounded contexts) - and doing all that by focusing on the core domain and having a shared view of the problem space with the domain experts. The usefulness of this might not be apparent for a simple CRUD system, but its invaluable when dealing with other complex ones.

seidenada I was expecting that this Video talks about Bounded Contexts, Value Objects, Aggregates etc. But I got this information now from somewhere else, thanks!

@@sticksen DDD is not about value objects, aggregates … It is domain model which is architectural business pattern. But there are next patterns which can be used in relation with DDD. DDD is about naming, bounded context, vocabulary. It is more than programming technique. It is development philosophy.

ZefekKa of course it is also about the things I mentioned. It’s the Tactical Design.

Closer than it sounds. I think this Is a great place to start, towards feeling like you really "get" DDD :)

What's gd?

@@DurgaswaroopPerla God damn

how's it going 🤣

Nops, the counter of likes is just hidden.

Nothing is wrong with either solution. And probably there even might be a better solution if I asked you to think really hard you might come up with something like a route or itinerary. It's not even that point he's trying to make. The point is we need to speak a common language to prevent us from creating software that doesn't fit the problems and scenario's of it's users . We need to carefully and thus not carelessly compass potential future requirements without overcomplicating and overspecifieing so we can always keep on building software ;). And in order to do that we might use DDD and create a lot of models and shared definitions instead of inventing new. Having proper business alignment is great. And event storming is also a very good way to involve domain experts in the proces of defining possible solutions and spotting it's shortcomings upfront.

In the text he encourages fleshing out these nuances in language to find deeper insight into the problem. Work hard to achieve clarity in the language used between teams, and all of the sudden a developer knows exactly what a domain expert is explaining, or vice versa, with less or minimal ambiguity. If some thing or part of the language is unclear or inconsistent, work to make it clear and consistent. As a result, you will gain valuable perspective on what needs to (or could) interact with something else to provide a rich and meaningful experience to the user. The benefit of this is, as a developer, you become very good at distilling down information and abstracting out the patterns - an invaluable skill regardless of the domain. It might seem futile and pedantic, but this skill of effective abstraction is transferrable across every single domain. Its difficult to abstract a pattern out of something you don't understand, but with effective language, the domain experts can help you bridge that gap.

How are your kids? shower some love, focus on technology...