Great talk. Thank you for making it a consumable topic for non-engineers. These talks are often focused on helping lead engineers to the water and so they use jargon that others don't understand. This is something I can send anyone.
The water thing was probably a good lesson for Nick. The "lack of clarity" criticism is invalid and seems like the person wants to someone else to tell them exactly how to break apart their domain. Most other comments seem good.
Talk was awesome. For people annoyed with the speaker sipping water, I have some questions... What content are you sharing? What conferences have you spoken at? Stop critiquing people that are in the game helping others while you are consistently on the sideline just talking and not contributing value to others. In other words, show me your conference talk that he should learn from. Then you have the right to criticize.
@@JamesSmith-cm7sg I don't agree to that. Criticism is one of the key terms in improving ones skills, e.g. way of teachings. Then the speaker must be humble enough to learn new perspectives, based on the audience. As a speaker you should speak in a way that makes more sense for all of them then only just some of them. A teachers responsibility is to clarify a complex stuff into manageable and graspable concepts, which I think he is doing just great. And the best improvement of one self if exactly from feedback, whether it is good or bad. But sipping water is to tripping xD (but trivial), and I would also love to have another example. But all over he has done a good job. Thumbs up
@@nugzari939 The point is not about criticizing, but what is critiqued. Zipping water to keep on talking for 45 minutes should be an non factor for the audience. If you can not stand this little annoyance, how can you work in a team with people mumbling while coding, or having allergies or anything. People who criticize water zipping should ask themselves if they are a bit neurotic.
Hey Nick, thank you very much for the presentation. Though at the start it felt like you were a little condescending and all that water drinking was distracting, eventually the presentation felt much better. That's my 2 cents, thanks again.
Purism. He's the inventor of DDD and holds a pure view on it. Others like Nick have taken his teachings and adapted them to their own experiences. Perfectly natural.
I am. not sure if I understand your take on bounded context, almost like the ideas were still forming in your brain while you were giving this talk. There was too much back and forth between what was hoped out of listeners. Also, the idea of going with the flow is not bounded context. Bounded context is what makes sense at a given point in time w.r.t. what needs to be done, not what is going on everywhere else. So, the point of organizational structures and overstepping teams seems like a suggestion where something is being developed where only the dev teams want that thing and not the organization. Such software should not be developed To me, bounded context is enough "encapsulation" where one entity can independently take decisions (including override) without worrying about other aspects of a system. And yeah, water drinking is disturbing and not recommended.
I don't know what is wrong with this guy. Why is he drinking constantly during the presentation? May be he got a lot of alcohol yesterday. Annoying guy.
Great talk. Thank you for making it a consumable topic for non-engineers. These talks are often focused on helping lead engineers to the water and so they use jargon that others don't understand. This is something I can send anyone.
Ignore the negative comments, this was a practical explanation of bounded contexts Good presentation.
The water thing was probably a good lesson for Nick. The "lack of clarity" criticism is invalid and seems like the person wants to someone else to tell them exactly how to break apart their domain. Most other comments seem good.
One of the most useful talks about software design I've listened so far !
One of the best talks on bounded contexts.
Conway's Law. 100% agree that bounded contexts should be optimized for team autonomy and removing bottlenecks to deployment.
Talk was awesome.
For people annoyed with the speaker sipping water, I have some questions...
What content are you sharing?
What conferences have you spoken at?
Stop critiquing people that are in the game helping others while you are consistently on the sideline just talking and not contributing value to others.
In other words, show me your conference talk that he should learn from. Then you have the right to criticize.
So the only people who can criticize are those who make content themselves and not the receivers?
@@Orestis125
He's just saying it's easy to criticize - but most people who criticize don't bring anything else to the table.
@@JamesSmith-cm7sg I don't agree to that. Criticism is one of the key terms in improving ones skills, e.g. way of teachings. Then the speaker must be humble enough to learn new perspectives, based on the audience. As a speaker you should speak in a way that makes more sense for all of them then only just some of them. A teachers responsibility is to clarify a complex stuff into manageable and graspable concepts, which I think he is doing just great. And the best improvement of one self if exactly from feedback, whether it is good or bad. But sipping water is to tripping xD (but trivial), and I would also love to have another example. But all over he has done a good job. Thumbs up
@@nugzari939 The point is not about criticizing, but what is critiqued. Zipping water to keep on talking for 45 minutes should be an non factor for the audience. If you can not stand this little annoyance, how can you work in a team with people mumbling while coding, or having allergies or anything. People who criticize water zipping should ask themselves if they are a bit neurotic.
Nick Tune is a genius!
one the most sensible talks on DDD, pragmatic!
The man if bounded to the glass of water
Hey Nick, thank you very much for the presentation. Though at the start it felt like you were a little condescending and all that water drinking was distracting, eventually the presentation felt much better. That's my 2 cents, thanks again.
One of the most dehydrated talks about software design I've listened so far.
I paused this video to see if I could find any comments about this annoying sipping that kept me from focusing on the merits of the case
Those water sips are so annoying, i could only focus on waiting fpr him to take a sip.
You try to give a talk and have anxiety cause you cotton mouth while you are struggling to speak. Ungrateful man.
Great talk!
Good talk. For people who are complaining about the water sipping - I just put a poster note on the left to cover his face - problem solved!
I really wish we knew why Eric Evans doesn't agree with the primary hypothesis.
Purism. He's the inventor of DDD and holds a pure view on it. Others like Nick have taken his teachings and adapted them to their own experiences. Perfectly natural.
The guy should drink full 3 glasses of water before his next presentation :). Other than that, it was great.
that is a bottomless glass of water
Just what I thought! That slurping sound was so distracting!
Awesome lessons. Thank you!
this mush is like a posh chav, I love it
Lovely talk. Drop the water
Thanks, really helpful
The presenter is a bit annoying, comes off as arrogant, but the content of this talk was very good. I learned some new things, so thank you.
is there the keynotes of this lesson?
Nice talk
19:58 die einzige Sache bei der es um bounded contexte geht.
21:25 DDD = model Hypothesis
40:30
Awesome
Thanks but you could have used a better example..this one was dry not very common app example
I just can't pay attention to this talk while this guy drinks more water than he speaks
Nice talk, but I needed to stop as the constant water drinking was simply to annoying.
Either you drink water or talk... Please don't do both, it feels rude.
Im trying to cope with your 'water sipping' but EISH... 😥, worst part, im listening to this on the headphones.
Is that a water fountain never ends
What's with Water sipping?
People can't talk one hour without sipping water? Are you like 80 years old?
I am. not sure if I understand your take on bounded context, almost like the ideas were still forming in your brain while you were giving this talk. There was too much back and forth between what was hoped out of listeners.
Also, the idea of going with the flow is not bounded context. Bounded context is what makes sense at a given point in time w.r.t. what needs to be done, not what is going on everywhere else. So, the point of organizational structures and overstepping teams seems like a suggestion where something is being developed where only the dev teams want that thing and not the organization. Such software should not be developed
To me, bounded context is enough "encapsulation" where one entity can independently take decisions (including override) without worrying about other aspects of a system.
And yeah, water drinking is disturbing and not recommended.
Stop making noise when drinking water! Its annoying
stop making stupid comments ...
I don't know what is wrong with this guy. Why is he drinking constantly during the presentation? May be he got a lot of alcohol yesterday. Annoying guy.
stupid comment
I could not take him sipping water every min, was so annoying. Finally had to stop watching this video.