Clean Architecture & Design Patterns in Practice · 课时

日常编码中的模式

识别您可能已经在使用的设计模式简单示例，并学习如何有意识地应用它们

日常编码中的模式 是 CoddyKit 上的免费 Clean Architecture & Design Patterns in Practice 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Clean Architecture & Design Patterns in Practice 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Clean Architecture & Design Patterns in Practice 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Spotting Patterns

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.

Why Recognize 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!

Iterating: The "Loop" Pattern

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.

Looping Example

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.

import java.util.ArrayList;
import java.util.List;

public class Main {
  public static void main(String[] args) {
    List<String> fruits = new ArrayList<>();
    fruits.add("Apple");
    fruits.add("Banana");
    fruits.add("Cherry");

    System.out.println("My fruits:");
    for (String fruit : fruits) {
      System.out.println(fruit);
    }
  }
}

Interchangeable Actions

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.

Action Example

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

interface Operation {
  int execute(int a, int b);
}

class Add implements Operation {
  @Override
  public int execute(int a, int b) {
    return a + b;
  }
}

class Subtract implements Operation {
  @Override
  public int execute(int a, int b) {
    return a - b;
  }
}

public class Main {
  public static void main(String[] args) {
    Operation addOp = new Add();
    System.out.println("10 + 5 = " + addOp.execute(10, 5));

    Operation subOp = new Subtract();
    System.out.println("10 - 5 = " + subOp.execute(10, 5));
  }
}

The "Notifier" Pattern

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.

Notifier Example

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".

interface ClickListener {
  void onClick();
}

class MyButton {
  private ClickListener listener;

  public void setClickListener(ClickListener l) {
    this.listener = l;
  }

  public void simulateClick() {
    if (listener != null) {
      System.out.println("Button clicked!");
      listener.onClick(); // Notify the listener
    }
  }
}

public class Main implements ClickListener {
  @Override
  public void onClick() {
    System.out.println("Action: Button was handled!");
  }

  public static void main(String[] args) {
    MyButton button = new MyButton();
    Main handler = new Main();
    button.setClickListener(handler);
    button.simulateClick();
  }
}

Consciously Applying Patterns

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.

Pattern Recognition Quiz

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?

Recap: Everyday Patterns

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!

常见问题解答

「日常编码中的模式」课时是免费的吗？

是的 — 「日常编码中的模式」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Clean Architecture & Design Patterns in Practice 课程的其余内容，请升级到 CoddyKit PRO。 Clean Architecture & Design Patterns in Practice 课程共包含 4 节课。

「日常编码中的模式」这节课中我会学到什么？

识别您可能已经在使用的设计模式简单示例，并学习如何有意识地应用它们你通过在浏览器中直接运行的动手代码来练习 Clean Architecture & Design Patterns in Practice，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Clean Architecture & Design Patterns in Practice 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Clean Architecture & Design Patterns in Practice 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「日常编码中的模式」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Clean Architecture & Design Patterns in Practice 课中编写并运行代码吗？

能。每节 Clean Architecture & Design Patterns in Practice 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Clean Architecture & Design Patterns in Practice