The Art of Saying "No" in Code Review

The Art of Saying "No" in Code Review: 7 Levels from Soft to Hard There's a skill that nobody teaches in CS programs: how to reject code without making it personal. Native English speakers learn this through years of cultural osmosis. Non-native speakers often learn it the hard way — by accidentally sounding rude, or by being so polite that their blocking feedback gets ignored. I've collected these 7 levels from real code reviews across 4 companies and 3 countries. Each level serves a different purpose. Master all 7, and your code reviews will be clearer, kinder, and more effective. Level 0: The Positive Observation Not saying no at all — just pointing out what's good. Nice approach here — the early return keeps the happy path clean. TIL about this API. Clean usage. This is much more readable than the previous version. 👍 When to use: When code is genuinely good. Sounds obvious, but most reviewers only comment when something is wrong. Positive comments build trust so that your "no"s lan