Code reviews are where real technical English lives. “LGTM”, “blocking”, “nitpick”, “caveat” — these words shape how your team perceives your communication skills as much as your code quality. Today we go deep on the vocabulary that matters most in PR reviews and technical Slack threads.

📖 Word of the Day: idempotent

IPA: /ˌaɪdɛmˈpoʊtənt/ Nghĩa: Bất biến — thực hiện một thao tác nhiều lần cho kết quả giống hệt thực hiện một lần

Pronunciation tip: eye-DEM-poh-tent (stress on DEM, not eye or tent)

Example sentences:

  1. “This API endpoint should be idempotent — sending the same payment request twice must not charge the user twice.”
  2. “HTTP PUT is typically idempotent, but POST is not — design your retry logic accordingly.”
  3. “Our batch job isn’t idempotent yet. If it crashes halfway and restarts, we get duplicate records.”

🔗 Merriam-Webster: idempotent | MDN HTTP Methods

📚 Vocabulary Table: Code Review Language

PhraseIPAVietnameseUsage in a PR comment
nitpick/ˈnɪtpɪk/bắt bẻ chi tiết nhỏ”Nitpick: userId would be clearer than uid.”
blocking/ˈblɒkɪŋ/phải sửa trước khi merge”Blocking: missing null check will throw NPE in production.”
LGTM—Looks Good To Me — đồng ý merge”LGTM! Merging after CI passes.”
caveat/ˈkævɪæt/lưu ý quan trọng”This works, caveat: assumes input is pre-sorted.”
footprint/ˈfʊtprɪnt/tài nguyên tiêu thụ”Memory footprint grows unboundedly — worth capping.”

🎯 Pronunciation Guide

Practice this sentence aloud:

“The retry logic isn’t idempotent — that’s a blocking issue, not a nitpick. My caveat: fixing it will increase the memory footprint.”

Breakdown:

  • idempotent → eye-DEM-poh-tent (4 syllables, stress 2nd)
  • blocking → BLOCK-ing (short O)
  • nitpick → NIT-pick (short I, hard K)
  • caveat → KAV-ee-at (3 syllables, stress 1st)
  • footprint → FOOT-print (compound, stress FOOT)

✏️ Exercise 1: Classify the Comment

Label each PR comment as blocking, nitpick, or caveat:

  1. “The variable name x makes this harder to read — consider requestCount.”
  2. “Null pointer exception will happen when the list is empty. Must fix before merge.”
  3. “This solution works, but assumes the database is always available — may fail under network partitions.”
  4. “Can we add a trailing newline at end of file? Convention in our codebase.”
Answers
  1. Nitpick — readability preference, not critical
  2. Blocking — will crash in production
  3. Caveat — works but with a known limitation
  4. Nitpick — style convention

✏️ Exercise 2: Write in English

Translate these Vietnamese code review comments to natural English:

  1. “API này không idempotent — gọi retry 2 lần sẽ tạo 2 records.”
  2. “Bắt bẻ nhỏ thôi — tên biến flag không rõ nghĩa.”
  3. “Được, nhưng lưu ý: code này chỉ chạy đúng khi timezone là UTC.”
Suggested Answers
  1. “This API isn’t idempotent — retrying will create duplicate records. Blocking.”
  2. “Nitpick: flag is vague — what does it represent?”
  3. “LGTM, but caveat: this only works correctly when the server timezone is UTC.”

💡 Idiom of the Day: “rubber stamp”

Nghĩa: Phê duyệt mà không thực sự xem xét (như con dấu cao su — ấn cái là xong)

Examples:

  • “Don’t rubber-stamp this PR — there’s a potential race condition in the auth flow.”
  • “We rubber-stamped 20 PRs last sprint and shipped 3 bugs to production.”

Vietnamese equivalent: Ký cho có / phê duyệt hình thức

🗣️ Mini Dialogue: Monday Code Review

Thuan: Hey Linh, left some comments on your payment service PR.

Linh: Thanks! Is anything blocking?

Thuan: One blocking issue: the retry handler isn’t idempotent — it’ll charge users twice if the first request times out. Everything else is nitpicks.

Linh: Got it. I’ll add a payment-request ID to deduplicate. Caveat: this will increase our Redis footprint slightly.

Thuan: That’s fine, Redis is cheap. Fix the idempotent issue and it’s LGTM from me.

Linh: Updating now. Thanks for the thorough review — much better than a rubber stamp!

🚀 Today’s Challenge

Open your next PR or code review and:

  1. Classify every comment you write as blocking, nitpick, or caveat
  2. Use at least one word from today: idempotent, footprint, caveat

Labeling severity in code reviews makes you look more senior and saves everyone time — no more guessing whether something must be fixed before merge.

Noon covers vocabulary depth. Morning = Speaking Skills, Evening = Role-play Practice. 📚

Export for reading

Comments