Code Review: Add Context When It Counts (Google's Advice)

Google's testing blog just dropped a note that should be pinned on every developer's desk – especially those who've ever left a comment saying 'Add tests' without a hint of which ones. The topic: adding context to code review responses and why it matters.

Why it hurts
We've all seen comments like 'This is bad' or 'Rework it.' The author might think they're a guru, but they're just breeding tension. Google's recipe is simple: if you're criticizing code, explain why. Not just 'because I said so,' but with references to best practices, potential bugs, or non-functional requirements.

When context is critical
Context matters most in three cases: security discussions (so the author understands risks), complex architectural decisions (to avoid rewriting everything in a month), and bug reports (so the developer can reproduce the issue). And no, 'I don't like it' is not context.

How to do it right
Instead of 'Remove this hack,' write: 'This hack might break under load >1000 RPS, let's use a cache with TTL.' Instead of 'Add tests,' say: 'Cover the empty API response case – we've hit that bug in production before.' And always specify what you've already verified and what's just a hunch.

METABYTE studio's take
We at METABYTE went through the 'LGTM' and 'fix by feel' phase too. Now our CI has a plugin that highlights comments without context – and late-night calls dropped by half. Give it a shot, even if your code review is just a checkbox in Jira.