AMAbhinandan Mishrainabhinandanmishra1.hashnode.dev·Jun 12 · 4 min readDesign Patterns #4: Builder PatternBefore learning Builder Pattern, let's first understand the problem it tries to solve. Suppose we have a User class. class User { private String name; private String email; private String00
AMAbhinandan Mishrainabhinandanmishra1.hashnode.dev·Jun 12 · 3 min readDesign Patterns #3: Observer PatternThis is probably the first pattern you'll encounter in real-world systems without realizing it. Before learning the observer pattern, let's first understand the problem. Let's understand with the exam00
AMAbhinandan Mishrainabhinandanmishra1.hashnode.dev·Jun 12 · 5 min readDesign Patterns #2: Factory PatternWhile learning strategy pattern one question should have come to your mind: PaymentStrategy paymentStrategy = new UpiPaymentStrategy(); Who is responsible for creating this strategy object? Because i00
AMAbhinandan Mishrainabhinandanmishra1.hashnode.dev·Jun 12 · 3 min readDesign Patterns #1: Strategy PatternBefore starting learning strategy pattern, let's first understand the problem that this pattern solves. Suppose we are building an e-commerce application, where users can pay using multiple methods: 00
AMAbhinandan Mishrainabhinandanmishra1.hashnode.dev·Jun 11 · 12 min readDesign Principles #4: SOLID principleTill now we have learned the following principles that need to be followed to make code flexible and maintainable: Low Coupling (less dependent) and High Cohesion (highly purpose-specific classes) C00