Code Review

Created

Created

2020 Jul 22 1:5

Creator

Creator

Seonglae Cho

Editor

Editor

Seonglae Cho

Edited

Edited

2026 Jan 6 0:9

Refs

Refs

Github Pull Request

Since stricter reviews are necessary, a lead's review is essential for code quality.

Code Review However, for this to work, the lead must have the skills to provide good feedback even if they're not actively coding.

Check all file reviewers before merge

The person who asked resolves

Modification suggestion
Information question
Reason question

Code Review Methods

Mob Code Review

Nudge Code Review

Google Critique & Gerrit (open-sourced)

How Google does code review

Google has two internal code review tools: Critique, which is used by the majority of engineers, and Gerrit, which is open-sourced and continues to be used by public-facing projects. Here's how they work.

https://graphite.dev/blog/how-google-does-code-review

How Google does code review

How Google takes the pain out of code reviews, with 97% dev satisfaction

A study of Google's code review tooling (Critique), AI-powered improvements, and recent statistics

https://engineercodex.substack.com/p/how-google-takes-the-pain-out-of

How Google takes the pain out of code reviews, with 97% dev satisfaction

With Git

Post-Commit Reviews

I recently read an excellent article in the Amazon Builder's Library by Clare Liguori which goes into great detail about AWS's CI/CD architecture. It's a truly brilliant post and I recommend everyone interested in CI/CD infrastructures read the article. The article covers the gamut from unit testing to integration testing (in production) to staged rollouts in "waves" to automated rollbacks.

https://medium.com/@copyconstruct/post-commit-reviews-b4cc2163ac7a

Post-Commit Reviews

Backlinks

Vibe Coding Code Quality Code Review

Recommendations

/////