Your video is probably one of the best I have found in how to use design patterns in C++. It is really clear, and the fact that you show in real time what you are doing really helps follow the content.

Thank you for explaining these patterns so clearly and for keeping it simple. Other sources I tried made them seem very complicated and I almost gave up.. thankfully I came across your channel! I can't thank you enough.

amazing. I'm so lucky to have the chance to watch your videos!!!!!

Thank you Mike, best explanation.

Understood fully..loved this :)

Man i just got the understanding of Factory Design pattern after watching it so easily Thanks a lot 🙏

amazing as always = thank you so much Dr. Mike

info vtbl was really cool. thank you.

Absolutely loved your teaching style! 🙌 Thanks for the cool tip: --tui

Thanks for the clear explanation and great content. According to refactoring guru, the design pattern "factory method" would have a creator, concrete creators, product, and concrete products. In the example you provided, MakeGameObjectFactory seems to be an object creation function that abstracts away the object creation process and provides an easier way to create objects. I'm wondering if this is a simplified variation of the factory method, or if this still aligns well with the standard factory method? Thanks.

_thank you thank you thank you_ for the clear explanation

thanks a lot for this explanation

Curious, Is there any reason to use shared_ptr? in general, by default people use unique_ptr.

Quality content

Does this pattern have to use heap allocation to work

Can we keep factory method as static class method and keep class constructor private? so only from factory method we can create instance of class.

Great video!

isn't it, same as command pattern ?