Design Patterns in Plain English | Mosh Hamedani

Mosh teaches well but his voice is so calming that it makes me sleepy.

Is this still relevant in Functional programming world?

This is not a design pattern course - it is a OOP in java course. the title is misleading.

Thanks for this clear explanation

Hi Mosh, thanks for this wonderful video. Could you please create a series on system design, if possible..

Very well done

Hello sir, I have a question for memento pattern that why we remove last state and return it to editor, I think it should return second last state from states before removal

This content is invaluable. Thank you Mosh.

Could anyone explain what is the problem with having to recompile the related classes int the project in case of tight coupling?

This is gold and free!! Thank you so so so much!!

I came to learn Design Patterns, but suddenly found myself learning how to "put the bracket on the following lane" and "inlelej BTW".
This sucks.

Every bit of information is sorted in such away that anybody who doesn't know OOP Principles or ULM notation will understand it. You are doing great. Keep Going👍 . By the way, if you watch this video and you don 't understand Java notation "+" , "#" , "~" or "-". It's normal but it is easy to understand. So, "+" means "public" , "#" means protected , "~" means package which you are using and "-" means private. That's all. Everyone has a nice day 😉 Bye.

Not worth it

Design patterns :D :D

These course actually doesn't teach you design patterns!
It's just introduction to Java and OOP then introduction to design patterns, then If you need to learn design patterns you have to pay.
Don't waste your time here if you're looking for a free course to learn design patterns, except if you want to pay so go for the paid course, as you'll learn here nice stuff except the design patterns.

This guy is save my day

thanks

Question: What is a good modern tool to generates those uml diagrams for java source code?

WAY TOO MANY ADDS. DO NOT WATCH. VERY LONG INTRO DONT WATCH!!!!!!

There's always good content to be found here, short, clear, to the point...

I came here for the patterns, but accidentally learned Java too

I just love how no matter how good is the English accent of an Iranian, you can always tell. great job by the way.

I'm sorry, but a lot of water...

Thank you Mosh for this great explanation! :-)

Hello guys, what pattern is best for implementing your own project auditing. Thanks for your replies.

Hey Mosh, Please share a code on Journal program in Csharp.

This was a fantastic lesson, Mosh. I'm a QA, but I'm always trying to understand the systems I'm working with better, and I was able to follow along - even with the more complex ideas - in a way I can't always do with other teachers. Thanks so much.
Also, I hope your fans here in the comments call themselves The Mosh Pit. 🤘

I learned more in this video than I had the whole semester thank you so much

Hey Mosh, Thanks for all your content. Was just wondering if the code for all of these patterns is available with the purchase of the Design Patterns course?

but why use setter instead of constructor,what difference

Your way of explaining all these things is absolutely amazing!!!!!

WOW WOW WOW WOW i realized i was on the wrong path on coding without those concepts you saved me from writing Agly code.Thank you MOSH

Do you have any course like this in Python?

I learned so much
Thank you mosh, keep up the good work

LEGEND . The best video on internet right now.

great crash course! I love it

iks Mosh.

Mosh Hamedani is the best Tutor there is together with that dude of Coding Train.

So I'm pretty against design patterns in the way they are taught, because most if not all of that stuff is either common sense when you encounter a specific problem or unnecessary boilerplate for a simple problem which doesn't need added complexity to be solved. I'm trying to give them a chance, but already at the Memento pattern I have a big issue with it. To use the EditorState and History classes you still have to store their instances inside Editor if you want them to be used by Editor methods, so you're basically doing the same thing as just storing a list of states inside Editor, but you've added some unnecessary boilerplate. You could also pass History to the Editor, but them you have some very unnecessary coupling with the caller of Editor.createState having to know about the History.

In the language of design patterns, I would've created a 'facade' to hide the History interaction behind a 'EditorWithHistory', but in reality that would land me at step 1 after adding two unnecessary layers of abstraction. You see what I mean?

If a system is too complex, we add abstraction which simplifies the understanding of the system with respect to some specific target (team members working on the code, integration with some other system, fitting with a specific framework, making the code easy to verify with regard to fulfilling given requirements, being easy to understand or to use by the end user, etc.) and the kind of abstraction we use will depend on that specific target we have independently of any arbitrary set of solutions chosen from the design patterns. And if abstraction isn't necessary, then we don't mention it, we don't think about it - it doesn't exist as applied to the specific problem we're working on. So just teaching this stuff in the way where developers are supposed to know the names, types, examples etc. seems backwards to me. If someone likes to work with solutions in this framework - that's fine, but I don't see why it's forced upon developers if they don't need to store a problem-solution manual in their head to solve the actual problems they encounter. That's obviously not a critique of the learning resources, but the expectation that a developer should learn this to somehow be a 'complete' developer.

always 60% through then bang give me money. not watching any more wrong way to do business.
shame it looked good but one must have principles.

You else checked uploaded year to find Mosh's age right now? LOL

Thank you❤❤

You interrupted that example what you had started to explain at the Coupling chapter. It is a bit confusing.

i'm new to this Design Patterns and after watching this tutorial ... it seems like i knew it all ^_^ i will plan to enroll his course because this is very comprehensible! ^_^

Good explanation of fundamental design patterns in Java

Thank you