รูปแบบการออกแบบในการเขียนโค้ดประจำวัน

Software design patterns are reusable solutions to common problems. But guess what? You might already be using them without even knowing their fancy names!

In this lesson, we'll look at familiar coding scenarios and see how they relate to the bigger world of design patterns.

Understanding these patterns helps you:

• Communicate better: Use standard names for solutions.
• Write cleaner code: Apply proven structures.
• Solve problems faster: Reuse existing knowledge.

It's like learning the names of tools you already use in your workshop!

Think about how you go through a list of items. You probably use a for loop or a forEach construct.

This common way of accessing elements one by one is an everyday example of what the Iterator Pattern formalizes. It provides a standard way to traverse elements of a collection without exposing its underlying structure.

Here's a simple Java example of iterating over a list. Notice how the loop handles accessing each item, regardless of how the list is internally stored.

Have you ever written code where you need to perform different actions based on a condition, but all actions share a common way of being called?

For example, a calculator might have an "add" button and a "subtract" button, but both perform an execute action. This idea is a simplified version of the Strategy Pattern, where you define a family of algorithms, encapsulate each one, and make them interchangeable.

In this example, we define an Operation interface. Both Add and Subtract implement it, allowing us to choose which action to perform at runtime.

Imagine you have a button on a screen. When you click it, something happens. How does the button "tell" other parts of the program that it was clicked?

Often, you attach a "listener" or a "callback" function. This is a basic form of the Observer Pattern, where objects notify other interested objects (observers) about changes in their state.

Here's a simplified idea of how a "notifier" or "event publisher" might work. The Main class acts as an observer, reacting when MyButton "clicks".

Now that you've seen how common coding practices relate to design patterns, the next step is to apply them consciously.

• When you iterate, think "Iterator".
• When you swap algorithms, think "Strategy".
• When objects need to be notified, think "Observer".

This mindset helps you design more robust and understandable systems from the start.

Consider a situation where you are building a system that processes different types of financial transactions (e.g., deposits, withdrawals, transfers). Each transaction type has its own unique way of being processed, but they all need to be executed through a common interface.

Which design pattern concept does this scenario most closely resemble from our discussion?

You've seen that many common coding techniques are simplified versions of established design patterns. We explored:

• Iteration: Like the Iterator pattern.
• Interchangeable Actions: Like the Strategy pattern.
• Notifications: Like the Observer pattern.

Recognizing these helps you write clearer, more maintainable code and communicate design ideas effectively. Keep an eye out for them in your own projects!