# Clean Code in Python

只有同一人開發與維護，大多數情況是必須要打團戰的，所以能夠撰寫一份大家看了都很舒服的程式撰寫風格是相當重要的，從程式撰寫的架構與風格，很容易看得出撰寫者的功力與邏輯，從一開始就培養出有系統架構的程式風格是最簡單的方式，後面再去修都相當困難且繁瑣。

我最常看到臉上冒出三條線的專案是這樣(幾乎為Python)：

* 將所有程式功能都撰寫在同一份`py`
* 變數命名方式無法直覺的辨認
* 函數丟的滿地都是
* 註解空空

{% hint style="info" %}
我以前剛開始自己寫的時候也是有經過這些過程，但開始成為不同角色後，想法就改變了，或看過讓人一肚子火的程式後，心想我以後絕對不行這樣。
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://go.raymondctw.dev/technology/python/clean-code-in-python.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.