C++ Strategy Design Pattern - Part 1 of 2 - Changing Algorithmic Behavior

►Software Design and Design Patterns Playlist: • C++ Software Design an...
►Find full courses on: courses.mshah.io/
►Join as Member to Support the channel: / @mikeshah
►Lesson Description: In this lesson we talk about how to change algorithmic behavior at run-time by using inheritance for use in the strategy pattern. We typically choose to create a inheritance hierarchy when we have a family of related algorithms that could be called based on some condition at compile-time or run-time. In this video, we'll try to motivate the strategy pattern, and further understand where we may use the strategy pattern in applications. Stay tuned to the next video for an implementation!
►KZbin Channel: / mikeshah
►Please like and subscribe to help the channel!
►Join our free community: courses.mshah.io/communities/...

[@nrnjn8547]

Hell yee, I was waiting for this. I'm using your videos along with the gang of 4 book, to understand design patterns

[@MikeShah]

Awesome!

[@danielabouelezz6448]

Love your explanation, although I am still a beginner but i found it interesting to watch the whole video. I am very good with data structures now, so do you think I should be learning design pattern or what is my next step.

[@MikeShah]

Yes, next step is to give it a try to implement based on the explanation. Next video will also provide a walkthrough. Otherwise, next steps are to also consider a project (e.g. a small game) to put everything together.

[@VoidloniXaarii]

Omg, so exciting, thank you. I usually feel like sh.. When think of this stuff, so thanking of u talk about this ❤

[@MikeShah]

Cheers, enjoy!

[@Chupe_chupe]

Great video

[@MikeShah]

Cheers!

[@hoangbuihp2974]

yes sir, I have waited for this alot of time. And I want to know whether you will teach about linux in the future

[@MikeShah]

I can put something together

[@MikeShah]

Not sure on timeline -- but doing some videos on terminal is something that I am actively drafting

[@hoangbuihp2974]

thanks @@MikeShah i hope you will be knowed by more people in the future because your tutorial is extremely good

[@MikeShah]

Cheers!@@hoangbuihp2974

[@AlanMardi]

Thanks for great topic! Looking forward to part 2. I have a question: why do double check { threshold >= 16, threshold >= 64 ... } in each "else if" though they already excluded in preceding if's?

[@MikeShah]

Would want the conditional to be true if threshold is between a value 🙂

[@AlanMardi]

@@MikeShah hmm, I'm a bit confused :) I mean what is the pofit of: if (thr < 16) do_A() else if (thr >= 16 && thr < 64) // ? thr >= 16 do_B(); comparing to: if (thr < 16) do_A() else if (thr < 64) // no chance to call do_B() with (thr < 16) anyway, program will never even try to check it do_B(); I would even more likely add lower limit to check the 1st "if" entry: if (thr >=0 && thr < 16) ... but not sure why to do this for following "else if"s :)

[@MikeShah]

Ah yes, you are right that would be the equivalent, and perhaps even save some cycles. I was being a bit too explicit I suppose :)@@AlanMardi

[@AlanMardi]

@@MikeShah I see :) Really love explicit syntax, though this one is too dangerous for me as requires to change pairs of numbers to tweak thresholds. At some point I will definately miss it and change just one number, so code will compile and pass most unit tests, but still work not as expected :)