Episode 04B2 — Upper-Intermediate
Code Review in English
18:17 · 10 vocabulary terms · How to Request Changes on a Pull Request role-play · Free PDF transcript
Free transcript PDF
Episode 4 — Free transcript & study guide
- 10-term vocabulary table
- Full role-play transcript
- Language breakdown notes
- Quiz with full answers
Secure email link · Instant delivery · No spam · Unsubscribe anytime
Vocabulary
| Term | Definition | Example |
|---|---|---|
| Pull request (PR) | The package of code changes a developer submits for review before it is merged. Most people just say "PR." | "I've been through your PR — the session-management module." |
| Code review | The process of reading a colleague's code, checking it, and leaving feedback before it is merged. | "'Good work' and 'ready to merge' aren't the same thing — and that's exactly what a code review is for." |
| LGTM | Short for "looks good to me." An informal approval on a pull request, spoken as individual letters: L-G-T-M. | "Once those two things are in, this is an LGTM from me." |
| Nit | A minor, non-blocking review comment. A reviewer who writes "Nit:" signals that the author can take the suggestion or leave it. | "This is a nit, not a blocker — but renaming this variable would help readability." |
| Refactor | To restructure code to make it cleaner without changing what it does. It is a request to improve the structure, not a sign that the logic is wrong. | "This is a refactor, not a rewrite — the logic stays exactly the same." |
| Edge case | An unusual scenario at the boundary of what the code is designed to handle, which real users will eventually hit. | "I found an edge case — what happens when a user's token expires mid-session?" |
| Readable / readability | Whether other developers can read the code and understand it easily. Calling code "not very readable" is a technical observation, not a judgment of the developer. | "Think about readability — if someone needs to debug this six months from now, they have to read through all the refresh logic." |
| Iterate | To improve step by step through repeated cycles. In a code review, it means improving the code across review rounds instead of getting it perfect in one pass. | "We can iterate on the error-handling patterns in a follow-up PR." |
| Root cause | The underlying reason something went wrong, as opposed to the visible symptom. In a bug, it is the real technical failure behind it. | "The root cause is a missing error state in the refresh handler, not a logic problem." |
| Follow up | To continue something afterward, usually in writing — a later fix, message, or next step. As a noun, it is the thing you do afterward. | "I'll follow up with both fixes by end of day." |
Episode structure
Intro
~1–1.5 min
Vocabulary Preview
~2–3 min
Role-Play
~8–12 min
Slow Replay
~2–3 min
Language Breakdown
~3–4 min
Quiz + Wrap-Up
~2–2.5 min
Your hosts

Alex
Tech Lead

Sam
Developer