> For the complete documentation index, see [llms.txt](https://teresahsieh850506.gitbook.io/leetcode/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teresahsieh850506.gitbook.io/leetcode/master.md).

# Wake Up and Solve That LeetCode Problem!

![](/files/-MYERzn4K4LvoTz8qiP6)

## 解題 flow

一個題目用  1.5 \~ 2 小時，完成以下兩個回合：

**第一回合**

1. 思考題目要做什麼，用紙筆寫下自己的思維
2. 花 0.5\~1 小時寫下程式碼，實現想法
3. 保留 0.5 小時刻意重構程式，思考空間/時間複雜度等等，可以尋找討論區裡的討論，研究別人的切入點，**把一種題目想到極致**

**第二回合 (隔一段時間再說)**

第一次解題時不太執著，要讓子彈飛一下，兩天後再回來看看

一方面是可能兩天後會有新的想法，但更重要的是——我們在優化時會研究別人的 solution，當下可能好像懂了，但可能隔一段時間會忘記，需要複雜或做更深入的內化


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://teresahsieh850506.gitbook.io/leetcode/master.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.