We’ve all done it, written “LGTM” (Looks Good To Me) or “+1” in a code review when we’re in a hurry. And sure, sometimes the code really looks good. But is that brief comment in a code review enough to encourage your team to improve their skills and reduce technical debt?
Let’s explore why clear, constructive feedback matters and how you can give more meaningful code reviews in English.
🟢 Why “LGTM” isn’t enough
“LGTM” can feel impersonal and vague. It gives your team no clear indication of what they did well or what specifically needs improving. Over time, this habit can lead to:
- Repeated mistakes or suboptimal solutions.
- Increased technical debt as issues slip by unnoticed.
- Missed opportunities for skill improvement and team growth.
🟢 Examples of meaningful feedback
Even short comments in English can dramatically improve team clarity and motivation. Here are some easy examples to start using today:
Positive Feedback Examples:
- ✅ “Great simplification! Your changes make the function much clearer.”
- ✅ “Well done catching that bug early.”
Constructive Feedback Examples:
- ✅ “Have you considered the performance implications here?”
- ✅ “Good job! Just check for potential edge cases in your validation logic.”
- ✅ “This works well, but readability might improve if we split it into smaller functions.”
🟢 Quick practice exercise
Look at this sample code snippet and think of one positive and one constructive comment:
Possible answers:
- Positive: “Nice and clear loop logic, very readable.”
- Constructive: “Consider handling negative prices explicitly or logging them.”
🟢 Your challenge for this week
The next time you’re tempted to type “LGTM”, pause for 30 seconds. Find one specific point to praise or suggest an improvement.
Your team (and future you) will be grateful.