This document discusses patterns in software development, explaining that patterns encapsulate best practices, provide reusable solutions to problems, and form a vocabulary for architecture. It acknowledges that patterns can be misunderstood and misused, causing confusion. The document provides steps for using patterns effectively, and explains the strategy pattern in particular, giving examples of strategies like plugins, providers, and state objects. It concludes with an example of using strategies for password validation.

1. The Nature of PatternsA Strategy Moving Forward

2. Why PatternsEncapsulates Best Practices and Lessons Learned Reusable Solutions to Recurring ProblemsForms a Vocabulary for Describing Architecture

3. What is Wrong With PatternsOften Not Well UnderstoodOften MisusedOften Causes Confusion Instead of ClarityOnce Done Poorly Everyone is Inclined to Avoid Future Opportunities

4. Steps for Using Patterns EffectivelyRefactor To PatternsRefactor Towards PatternsRefactor From PatternsTRAIN TRAINTRAINTRAINStudy Patterns in ContextStudy Patterns Outside of a Project Before Using

5. Strategy PatternEncapsulate Related Algorithms Behind a Common InterfaceMultiple Types Implement the Common InterfaceSwitch Implementations by Switching TypesBecause Each Type Implements the Common Interface, Each Type can be Treated the Same

6. Sample StrategiesPlug-insProvider PatternsAmortization Schedules in a Mortgage CalculatorMultiple Views to a Single PresenterState Object for State Specific Business Logic Logic

7. Strategy CodePassword Complexity ValidationEach Class Will Define a Validation TestDriver Process Will Loop Through the Configured Tests and Evaluate the Results

8. Code Demo