第一次看此系列文的朋友，請先移步到 Day 1 – 如何開始？進行方式、自我介紹實戰 哦！
今天的場景是：團隊需要一起撰寫技術設計文件，你負責 API 的部分，但文件中還有其他人寫的架構、流程圖。常常卡住的地方是「如何在英文中表達要請對方補充內容，或提出修改建議」。
今日目標：學會 用簡單英文表達協作文件的需求，例如補充、修改或確認。
選擇一份文件，取代 Prompt 中的 {你的文件} 部分。
[Config]
- Day: Day17 – Documentation Collaboration
- Scenario: Working with teammates to co-write or review technical documentation (e.g., API design doc, README, or system design).
- Document:
```markdown
{你的文件}
```
記得把對話錄下來，自己聽一次，想想有哪裡不自然、哪裡需要調整。
救命句：
Could you add more details here?
爭取思考時間：
Let me think how to explain it.
🤖 If you were a new developer joining this project, which part of the documentation would you find most helpful first: the Project Structure section or the API Endpoints section? Why?
🗣️ I will focus on the project structure section first, because I want to know where is the project entry point and how should I develop it.
很單純想說先找進入點跟怎麼開發。不過後來發現可以用 start with 跟 to see 來接後面的，都比較口語。
I will start with the project structure section to see how to develop it.
🤖 So now that you’ve chosen to focus on the structure first, let’s imagine your teammate asks you to add a short note to the documentation. They want you to explain briefly why the internal folder is not supposed to be accessible from outside. What would you write in a simple sentence or two?
🗣️ I will write like the internal section is known by this programmer only, it doesn't allow to known by the other outside this project.
想說：寫在 internal 內是不應該被外部的人知道。
GPT 回饋可以用 shouldn't be 來取代 doesn't allow to 比較自然
the other outside this project 可以說 people from outside
🤖 So now imagine while you're writing that note, your teammate suddenly says, "Hey, can you also add a quick tip about how to run database migrations?" So now there's a little bit of an unexpected detail. How would you add that in one or two simple sentences?
🗣️ I will write down a header called Data Migration, and in the second part, I will write down the code base, the code sample.
「寫一個標題叫 Data Migration，然後在內文加上範例程式」，不過「內文」我不會說。所以臨時講 second part。
反饋：write down 可以直接講 write 就好。
後續則是可以說 and then I'll add a code example.
有沒有發現今天的文章結構不一樣了呢？
今天貼完 Prompt，GPT 就瘋狂問問題，問題都是跟關鍵字無關的。我才發現我之前太依賴關鍵字在說了，當我沒有東西可以看，就又花時間在想關鍵字。導致都沒有注意到文法及音調，有點失去一開始要練對話的目的了。
文章結構之後就像今天一樣調整成不寫關鍵字，而是紀錄 GPT 的問題及我的回答思路，試試看會不會對我自己比較有幫助。
1) Per-turn Corrections
Turn 1 Correction: You said “I will focus on the project structures section first because I want to know how the program entry point…” Correction: “I’ll focus on the Project Structure section first, because I want to know where the project entry point is.”
Alternative: “I’ll start with the Project Structure section to see where the entry point is.”
Turn 3 Correction: You said “The internal section is knowing by project developers only…” Correction: “The internal section is known by the project’s developers only. It shouldn't be used from outside the project.”
Alternative: “The internal folder is just for our team and not for external use.”
2) Top 3 Patterns
Article usage: Sometimes missing “the.” A simple rule: use “the” when talking about a specific section.
Past participle: “Known” vs. “knowing.” Remember that passive forms often need the past participle.
Negation clarity: Using “shouldn’t” instead of “doesn't allow to.” Keep negation simple.
3) Phrase Pack
“I’ll focus on the [section] first…”
“It’s meant to be used only by [the team].”
“We should add a short note about…”
“This section handles external requests.”
“Let’s add a code example here.”
“It shouldn’t be accessed from outside.”
4) Intonation Tip
When giving an important note, stress the key word: “It shouldn’t be used from outside the project.”
5) Fluency & Pronunciation Notes
Overall pace is good—keep sentences short.
Good job repeating corrections after hearing them.
Watch out for articles like “the.”
Practice the difference between “known” and “knowing.”
Great effort at staying clear even with a small pressure point.
6) Key Focus for Next Time
Let’s focus on article usage and passive forms.
We’ll do a 3-minute drill next time on using “the” correctly and forming passive sentences.
iThome鐵人賽
看影片追技術