Monday Noon: Technical Vocabulary Deep Dive 🛠️
Session focus: The exact words engineers use in code reviews, pull requests, and Slack threads — with pronunciation and real context.
📖 Word of the Day
Refactor /ˌriːˈfæk.tər/
Vietnamese: Tái cấu trúc code (cải thiện cấu trúc mà không thay đổi chức năng)
Why it matters: You’ll hear “can you refactor this?” in almost every code review. Knowing how to use it confidently sets you apart.
Example sentences:
- “I’d like to refactor this function before we merge — it’s getting hard to read.”
- “We spent the whole sprint refactoring the authentication module.”
- “The tech debt is piling up; we really need to refactor the payment service.”
🔗 Resources:
- Pronunciation: Cambridge Dictionary — refactor
- Usage in context: search “refactor” on GitHub code reviews
📋 Vocabulary Table
| Phrase | IPA | Vietnamese Meaning | Real-World Example |
|---|---|---|---|
| nitpick | /ˈnɪt.pɪk/ | Bắt bẻ, chỉ ra lỗi nhỏ nhặt | ”Just a nitpick — can you rename this variable to be more descriptive?“ |
| blocker | /ˈblɒk.ər/ | Vấn đề chặn tiến độ | ”We have a blocker: the API isn’t returning the right schema.” |
| lgtm | /el dʒiː tiː em/ | Looks Good To Me — chấp thuận | ”LGTM! Go ahead and merge when CI passes.” |
| codebase | /ˈkəʊd.beɪs/ | Toàn bộ mã nguồn của dự án | ”This change touches the entire codebase — be careful.” |
| address | /əˈdres/ | Giải quyết / xử lý (một vấn đề) | “Can you address the comments before requesting another review?” |
🎙️ Pronunciation Guide
Practice Sentence:
“I’ll refactor the legacy codebase to address the performance blocker before the next release.”
Breakdown:
| Word | Stress | Sounds like |
|---|---|---|
| refactor | re-FAC-tor | ree-FAK-ter |
| codebase | CODE-base | KODE-bays |
| address (verb) | a-DRESS | uh-DRESS |
| blocker | BLOCK-er | BLOK-er |
💡 Tip: “Address” is tricky — as a verb (to handle something), stress the second syllable: a-DRESS. As a noun (a location), stress the first: AD-dress.
🔗 Audio References:
✏️ Exercise 1: Vocabulary in Context
Fill in the blanks using the words: refactor, blocker, nitpick, LGTM, address
- “This is just a ________ but I think
getUserDatawould be a clearer name thangetData.” - “The broken test suite is a ________ — we can’t ship until this is fixed.”
- ”________, nice work! Approve and merge.”
- “Could you ________ the edge case where the user has no profile picture?”
- “We should ________ this before adding more features — the logic is tangled.”
✅ Check Your Answers
- nitpick
- blocker
- LGTM
- address
- refactor
✏️ Exercise 2: Translation Challenge
Translate these Vietnamese sentences into English using today’s vocabulary:
- “Tôi muốn tái cấu trúc module này — nó quá khó đọc.”
- “Chúng ta có một vấn đề chặn tiến độ: database đang bị lỗi kết nối.”
- “Looks good to me! Bạn có thể merge được rồi.”
- “Bạn có thể xử lý các comment trong code review không?”
✅ Model Answers
- “I want to refactor this module — it’s too hard to read.”
- “We have a blocker: the database is throwing connection errors.”
- “LGTM! You can go ahead and merge.”
- “Can you address the comments in the code review?”
💡 Idiom of the Day
”In the weeds”
IPA: /ɪn ðə wiːdz/ Vietnamese: Đang bị sa lầy vào chi tiết nhỏ, mất đi bức tranh toàn cảnh
Usage Examples:
- “Let’s not get in the weeds here — can we focus on the main architecture decision first?”
- “Sorry I’m a bit in the weeds with this bug — give me 30 minutes.”
🌱 You’ll hear this in meetings when someone is spending too much time on minor details. Use it to redirect discussions!
🎭 Mini Dialogue
Setting: Slack thread during a PR review
Minh: Hey, I left some comments on your PR. Nothing major — just a few nitpicks about naming.
Thuan: Thanks! I’ll address them now. Is there anything that’s a blocker for the merge?
Minh: Actually, yes — the unit tests are failing in CI. That’s a blocker.
Thuan: Oh, I see it now. The mock wasn’t set up correctly. Let me fix that and refactor this test file while I’m at it — it’s messy.
Minh: Sounds good. Ping me when it’s ready and I’ll do a final review.
Thuan: Will do. Should be fixed in 20 minutes.
🚀 2-Minute Challenge
Right now, open GitHub (or GitLab) and find a real PR comment.
Look for these words:
- ✅ “refactor” / “address” / “blocker” / “nitpick”
Then write one sentence using a word you found — as if you’re the reviewer.
Example: “Can you refactor the error handling here? It’s a bit hard to follow.”
Post it in your study notes or say it out loud. That’s real practice! 💪
📊 Today’s Progress
| Skill | What You Practiced |
|---|---|
| 📚 Vocabulary | 5 core PR/code review terms |
| 🎙️ Pronunciation | Stress patterns for technical verbs |
| ✍️ Writing | Fill-in-the-blank + translation |
| 💬 Speaking | Mini dialogue + challenge sentence |
Part of the Daily English series for tech professionals. Come back at 6PM for the Evening session — Writing & Email Fluency!