alecodes/personal-page
2
0
Fork 0
Code Issues 17 Pull requests Projects 1 Releases Packages 1 Wiki Activity Actions

chore: add files from master-wiki repo

Browse source
This commit is contained in:
Alexander Navarro 2024-11-20 20:00:35 -03:00
parent f99a9ae2ac
commit 1847f6bf28
315 changed files with 1047341 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

28
_master_wiki/Readwise/02. Strategy Pattern.md Normal file
View file

@ -0,0 +1,28 @@
# 02. Strategy Pattern
![rw-book-cover](https://i.ytimg.com/vi/pPKBbQoxDHQ/maxresdefault.jpg)
## Metadata
- Author: [[Coding with Yalco]]
- Full Title: 02. Strategy Pattern
- Category: #articles
- Document Tags: [[dev]] [[dev/design-patterns]]
- URL: https://www.youtube.com/watch?v=pPKBbQoxDHQ
- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=02.%20Strategy%20Pattern
> [!tldr]
> #OODP #ObjectOrientedDesignPattern #ObjectOriented
The Strategy pattern is a pattern that allows you to switch between several specific operation methods as needed. It creates several 'modes', each performing a given function, and allows you to choose which one to use. For example, shopping carts at a large supermarket's checkout counter perform the 'payment' function in various ways.
This is illustrated in an example of implementing the Strategy pattern, creating an interface called 'PaymentStrategy', and creating two classes that implement it, 'CreditCardPayment' and 'PayPalPayment'. These two classes fall into the 'PaymentStrategy' category, each implementing a 'pay' method. The important point here is that objects of the two classes can take the place of the 'PaymentStrategy' and execute the 'pay' method.
Also, the 'ShoppingCart' class has a 'PaymentStrategy' field, and the 'pay' method of the selected strategy is executed when calculating. In this way, the strategy pattern allows not only to change the a...
## Highlights
The second pattern we're going to  look into is the Strategy Pattern.  This pattern sets up several methods, or  'strategies', for performing a particular task,  and allows them to be 'interchanged' as needed [View Highlight](https://read.readwise.io/read/01jabhkm7ahb492vecg2wj8241))
This pattern separates several algorithms that  
perform specific functions  into individual capsules,  thus allowing them to be switched out  at any point during code execution.  If a new method needs to be added, you can  easily extend by creating another strategy class,  and it also becomes possible  to reuse them in other places. [View Highlight](https://read.readwise.io/read/01jabhv9ynysj0crf1jh3xc5r9))
This would be code that adheres to the  'Open/Closed Principle' we learned from SOLID. [View Highlight](https://read.readwise.io/read/01jabhvz49eamfzcf85qg4y1q8))