第一次看此系列文的朋友，請先移步到 Day 1 – 如何開始？進行方式、自我介紹實戰 哦！

🎬 情境故事

你提交一個優化查詢的 PR。Reviewer 說命名不一致、少了邊界測試，還擔心可維護性。你需要在會議上口頭回應，決定哪些接受、哪些婉拒，並把更改範圍與時程講清楚。

今日目標：用簡短句完成「承接 → 立場 → 下一步」。

🤖 Config Prompt

[Config]
- Day: Day13 – Code Review: Responding to Feedback
- Scenario: You are a software engineer who just received review comments on your PR. I will practice three moves: (1) accept feedback, (2) decline with reasons, (3) discuss change scope and next steps. Keep it realistic for web/backend/full-stack contexts.

👉 在練習之前...

想一下：

1. 接受 feedback 可以怎麼說？（先承接、再承諾）
2. 拒絕 feedback 可以怎麼說？（給理由、提替代）
3. 討論更改可以怎麼說？（對齊標準、切範圍、約時間）

並且把關鍵字寫下來。

我的關鍵字：

1. you're right.
2. I'd prefer ... because ...
3. Which should we prioritize

🎯 開始進行練習

記得把對話錄下來，自己聽一次，想想有哪裡不自然、哪裡需要調整。

📌 小技巧

🆘 今日救命句

• 救命句：

  Thanks for the feedback—let me check.

• 爭取思考時間：

  Give me a second to think—may I clarify one point?

🔑 核心句型

1. 接受（承接＋承諾）

   • Good catch. I’ll add the edge-case tests today.
   • You’re right about the naming. I’ll align it with our style guide by EOD.

2. 拒絕（禮貌＋理由）

   • I see your point, but we optimized for latency due to the SLA.
   • I’d prefer to keep this approach because it prevents N+1 queries in peak hours.

3. 拒絕＋替代方案（折衷）

   • Instead, how about keeping this query but adding an index and a wrapper?
   • What if we keep SQL now and document it, then refactor in a follow-up PR?

4. 討論更改（對齊標準）

   • Which should we prioritize—readability or response time under 200 ms?
   • Do we have a module-level guideline I should follow here?

5. 確認範圍與切分

   • Let’s scope this PR to A/B and move C to a separate ticket.
   • I can deliver the tests today and the refactor tomorrow—does that work?

6. 收尾與責任分配

   • To confirm: I’ll add tests and rename today; you’ll review the wrapper change.
   • Summary: keep SQL, add comments, post benchmarks within 24 hours.

📝 我的今日反饋

今天最大的收穫是 GPT 說：

• Practice keeping responses short and to the point.

我覺得這是我現階段最需要著重的地方，有時候會回答太長了。
比如說 we can use the package to load the configuration from yaml.，其實可以說 we can use the package for configurations. 就好。原本冗長的話，可以拆成 2～3 句更有重點的短句。

今天花很多時間一直在調整題目，因為沒有真正提交 PR，所以很難真的回應對方的問題。如果大家有什麼比較好的想法，歡迎多多留意！！

1) Per-turn Corrections:

Turn 1: You said, "Your function name is more clear."

Rewrite: "You mean: Your suggested function name is clearer."

Alternative: "Your suggested name is definitely clearer."

Turn 4: You said, "Because XML support's out of scope."

Rewrite: "You mean: I'd like to keep it JSON-only for now because adding XML support might be out of scope."

Alternative: "Let's stick to JSON for now since XML is out of our current scope."

2) Top 3 Patterns:

Comparative Forms: You sometimes say "more clear" instead of "clearer."
Rule: For short adjectives, just add "-er." "Clear" becomes "clearer."

Staying Concise: Occasionally, your sentences got a bit long.
Tip: Keep it short and simple; break one long sentence into two.

Clarifying Scope: You did well after a hint, but remember to clarify what's in scope early.
Mnemonic: "First define, then refine."

3) Phrase Pack:

"Your suggestion makes it clearer."

"Let's keep it in scope for now."

"We can handle that in a future iteration."

"I'd prefer to keep it JSON-only."

"We can use a tool like Viper for configuration."

"That sounds like a good next step."

4) Intonation Tip:

Stress key differences. For example, say "Let's only use JSON" with a bit of emphasis on "only" to highlight your main point.

5) Fluency & Pronunciation Notes:

Overall pacing was good and moderate.

Your clarity improved each time you repeated a corrected sentence.

Watch out for filler words when you hesitate—pausing silently is fine.

You did well following the correction policy and shadowing.

6) Key Focus for Next Time:

Work on comparative adjectives (e.g., "clearer").

Practice keeping responses short and to the point.

Do a quick two-minute drill on summarizing feedback in one sentence.

Great job today!