@syedameen6044
This vedio is seriously underrated. Thanks for such a lovely content❤❤❤
@chandrababu1680
Nice explanation bro! Keep it up. Bro small comment on Singleton design pattern! Sinlgeton design pattern can also be broken using cloning concept as cloning will always create a copy of object :).
@manivasuppalamarthi6948
Great effort from you. Keep rocking. All the very best. Thanks for all your videos.
@inthedark-e4l
Respect for the effort !!!
@codecraftV
At 2:01:15 the interface Amount has a method withdraw but account responsibility is not to withdraw right? It's violating Single Responsibility principle ? I think we should put that in seperate Transaction interface , please correct me if i am wrong?
@RiskyRishy
Using Enum to prevent the breaking of Singleton design pattern , we have sacrificed the ability to initiate object creation on demand, instead it will be created at the application start and take the memory of app
@manishagarwal4601
@Daily Code Buffer, In the Given example of SerializableSington Class, you have define the object is null of SerializableSingleton at the time of class loading. and when call the getInstance method then it is creating the object of that class. In this case the same hashcode will not come. Please suggest in this case
@This_Origami
I felt flyweight design pattern to be similar to prototype design pattern. Is there a way for distinction or use case to prefer one over another.
@LarryStone-q6r
You're an excellent teacher. Thank you.
@4Biddenn
are you using drawing pad? if yes which one?
@JayaJayaJayaJayaHey
Great video. One question - For Abstract Factory pattern - you have taken Application application = new Application(new MacUIFactory()); But if we use some string like new Application("mac"); and write the logic inside application. That way the work is simple for end user as he doesn't need to write java syntax like 'new and constructors()'. But again this has another disadvantage - we need to hardcode the application class like - if "mac" { return new MacUIFactory(); } and that violates 'Open/Closed principle'. so a hybrid solution is to use a list and dynamically add / fetch the UI factories based on the string passed like "mac". This way we follow principles like Dependency Inversion, open closed, in general all the Solid principles.