Strategy Design Pattern In C#

[@CodeMaze]

Thank you all for watching and for your support. ►► If you want to check out all our courses you can do that here: bit.ly/cdmz-courses

[@codewithgilly]

great stuff

[@CodeMaze]

I am glad you think that way. Thanks a lot for watching.

[@OnePieceWonPeace]

The Strategy Pattern is great when you need to, say, change a custom table column sort based on some other settings. I tend to notice, however, that The Strategy Pattern oftentimes quickly becomes The State Pattern where, in the table example, ends up with the entirety of settings data and all the different methods for sorting the table data between different states across all of the columns. I think of The State Pattern just as The Strategy Pattern on steroids, or at least just more fleshed out over time. That said, many times all you need is just The Strategy Pattern.

[@CodeMaze]

I fully agree. In software architecture so many times something that we initially meant to use as one pattern becomes something different when we are done with it. So, I would say it is the natural way of things and not in the bad way.

[@aliwa91]

Thanks

[@CodeMaze]

Welcome. Thanks for watching the video.

[@davidmares6053]

gracias :)

[@CodeMaze]

My pleasure. Thanks for watching this one.

[@NikolaGolijanin-m8s]

Hi Marinko, i use strategy pattern a lot, but i found it much easier to implement it using delegates instead of interface and concrete implementations. What you think about that approach?

[@CodeMaze]

To be honest, I don't know what to think about that because I never did it that way. I am trying to put my head around the idea of using a delegate to change a complete behavior of a class, but if it works, awesome.