Skip to content
Published on

Code Review English: Constructive Feedback Conversations That Build Better Code

🇰🇷KO🇺🇸EN🇯🇵JA
Authors
  • Name
    Twitter
Code Review Feedback Cover

1. 🎙️ Podcast intro

Welcome back to your practical English output training. Today’s theme is giving constructive feedback in code reviews without sounding rude or vague. You’ll train phrases for pointing out issues, suggesting improvements, and agreeing on next actions. Stay sharp, speak clearly, and let’s build feedback English you can use in real team conversations.

2. 📝 5 key expressions

ExpressionMeaning (KR)Example
I noticed that ~I discovered ~ (observation-based feedback)I noticed that this function handles errors differently from the other modules.
Could we consider ~?Could you consider ~?Could we consider splitting this logic into smaller functions?
One concern is that ~One concern is thatOne concern is that this query may be slow on large datasets.
To make it clearer, we could ~To make it clearer, you canTo make it clearer, we could rename this variable touserProfileMap.
Does this approach work for you?Is this approach okay?I suggest adding input validation first—does this approach work for you?

3. 🔇 Fill in the blanks — 5 questions

  1. I __ that this API returns different error codes depending on the endpoint.
    Correct answer: noticed

  2. Could we __ moving this helper function to a shared utility file?
    Answer: consider

  3. One __ is that this loop runs on every request and may affect performance.
    Answer: concern

  4. To make it __, we could add a short comment above this condition.
    Answer: clearer

  5. I can open a PR for this refactor—does this approach __ for you?
    Answer: work

4. 🗣️ Speaking practice — 3 questions

  1. Situation: I found duplicate logic in my colleague’s code. Politely suggest improvements.
    Model answer: I noticed we have similar logic in two places. Could we consider extracting it into one reusable function?

  2. Situation: A query with concerns about poor performance was discovered. Speak without offending your team members.
    Model answer: One concern is that this query might become expensive with larger data. Could we consider adding an index before release?

  3. Situation: I want to adjust the action plan after feedback.
    Model answer: To make it clearer, we could update the naming and add tests. Does this approach work for you?

5. 🔄 Korean → English Translation Quiz — 3 questions

  1. “The intention in this part is good, but the variable name is a bit ambiguous.”
    Correct answer: This part has a good intention, but the variable name is a bit ambiguous.

  2. “Could we consider separating this logic into a function?”
    Answer: Could we consider separating this logic into a function?

  3. “I think it would be safer if I added one more test case before deployment.”
    Answer: I think it would be safer if we add one more test case before deployment.

6. Listening Challenge

Listen to the sentences below and fill in the blanks.

A) “I __ that this endpoint does not validate empty input.”
Correct answer: noticed

B) “One __ is that this change may break backward compatibility.”
Answer: concern

C) “To make it clearer, we could add examples in the README. __ this approach work for you?”
Answer: Does

Discuss on Twitter • View on GitHub