Difference between revisions of "Code review"
Jump to navigation
Jump to search
m (→Good Reads) |
m (→Good Reads) |
||
| Line 5: | Line 5: | ||
See [[Code review in Phabricator]]. | See [[Code review in Phabricator]]. | ||
| − | == Good | + | == Good reads == |
Good reads on different angles of code review: | Good reads on different angles of code review: | ||
Revision as of 11:51, 12 October 2018
This page documents code review practices used for Software Heritage development.
Implementation
See Code review in Phabricator.
Good reads
Good reads on different angles of code review:
- Best practices (Palantir) ← comprehensive and recommended read, especially if you're short on time
- Review checklist (Code Project)
- Motivation: team culture (Google & FullStory)
- Motivation: code quality (Coding Horror)
- Motivation: humanizing peer reviews (Wiegers)