Very good explaining, but i have a question: can't we link the client directly to the adapter, because in the video i can't quite see the necessity to use the Client Interface? For example, a Button (+switch() ) and a Lamp (+turnOn() and +turnOff() ), if we want to add a Kettle with the same functionalities, we can simply add an adapter Ibutton and the Lamp and Kettle classes can implement the interface Ibutton.
This intermediate object(adapter) can also be used to provide a stable interface for similar components with different interfaces. But I guess that's a combination of the polymorphism and adapter patterns.
your videos are good, but at certain point I felt there is no breather. I had to pause the video to go over some details. Another point I miss is when to use which pattern. I feel sometimes there could be multiple ways of moving forward but which pattern to chose for simplicity ? is there some kind of rule that explains that ?
Thanks! You know I always try to work on that, but it is so hard to pick a pace that suits everyone!! Concerning the "when" to use each pattern, I try to always start my videos with an example and then transform it using the pattern in question, kind of a before-after experience thought this might help, and yes you are right most of the time there are multiple patterns you can use and apply in a situation :)
The best design patterns series i have ever found online . thank you so much for this masterpiece
Wow! Thank you so much :) Glad you liked it!
A gem of a video. Thanks!
Your methodology is flawless man! Keep it up
Thanks for the support :) Will do!
I really liked your Design Patterns series. You talk super fast. Following you is little difficult but content is top notch.
1st time -Watch video -> Ayeein 2nd time watch video -> Clearly understands the concept
Good stuff I liked the real life example
Glad you liked it :)
Hidden gem. liked and subscribed
Very good explaining, but i have a question: can't we link the client directly to the adapter, because in the video i can't quite see the necessity to use the Client Interface? For example, a Button (+switch() ) and a Lamp (+turnOn() and +turnOff() ), if we want to add a Kettle with the same functionalities, we can simply add an adapter Ibutton and the Lamp and Kettle classes can implement the interface Ibutton.
simple and perfect
This intermediate object(adapter) can also be used to provide a stable interface for similar components with different interfaces. But I guess that's a combination of the polymorphism and adapter patterns.
Hi, i think in 2:54 you should write: new FancyUIServiceAdapter(fancyUIService); With FancyUIService instance in constructor argument.
Hello! check 2:49 (the whole point is to not do that)!
I'm confused, how you will be test it in your unit tests? With DI you can mock FancyUIService, and test only adapter logic.
Thank You!
I hope this video is not sponsored by Zomato ? - An Indian. 😀
Wish it was xD
your videos are good, but at certain point I felt there is no breather. I had to pause the video to go over some details.
Another point I miss is when to use which pattern. I feel sometimes there could be multiple ways of moving forward but which pattern to chose for simplicity ? is there some kind of rule that explains that ?
Thanks! You know I always try to work on that, but it is so hard to pick a pace that suits everyone!!
Concerning the "when" to use each pattern, I try to always start my videos with an example and then transform it using the pattern in question, kind of a before-after experience thought this might help, and yes you are right most of the time there are multiple patterns you can use and apply in a situation :)
I swear to God, you saved my ass so well that I am convinced you are the second coming of Christ