Difference between revisions of "Code review"
Jump to navigation
Jump to search
(→References: more good reads) |
(→Good Reads: add guidelines from the Code Project) |
||
| Line 7: | Line 7: | ||
== Good Reads == | == Good Reads == | ||
| + | * [https://www.codeproject.com/Articles/524235/Codeplusreviewplusguidelines Code review guidelines] (Code Project) | ||
* [https://medium.com/palantir/code-review-best-practices-19e02780015f Code Reviews Best Practices] (Palantir) | * [https://medium.com/palantir/code-review-best-practices-19e02780015f Code Reviews Best Practices] (Palantir) | ||
* [https://blog.codinghorror.com/code-reviews-just-do-it/ Code Reviews: Just Do It] (Coding Horror) | * [https://blog.codinghorror.com/code-reviews-just-do-it/ Code Reviews: Just Do It] (Coding Horror) | ||
Revision as of 11:32, 12 October 2018
This page documents code review practices used for Software Heritage development.
Implementation
See Code review in Phabricator.
Good Reads
- Code review guidelines (Code Project)
- Code Reviews Best Practices (Palantir)
- Code Reviews: Just Do It (Coding Horror)
- Lessons From Google: How Code Reviews Build Company Culture (Google & FullStory)
- Humanizing Peer Reviews (Wiegers)