Difference between revisions of "Code review"
Jump to navigation
Jump to search
(→Good Reads: add guidelines from the Code Project) |
(→Good Reads: organize by topic) |
||
| Line 7: | Line 7: | ||
== Good Reads == | == Good Reads == | ||
| − | + | Good reads on different angles of code review: | |
| − | * [https://medium.com/palantir/code-review-best-practices-19e02780015f | + | |
| − | * [https:// | + | * [https://medium.com/palantir/code-review-best-practices-19e02780015f Best practices] (Palantir) |
| − | * [https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/ | + | * [https://www.codeproject.com/Articles/524235/Codeplusreviewplusguidelines Review checklist] (Code Project) |
| − | * [http://www.processimpact.com/articles/humanizing_reviews.pdf | + | * [https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/ Motivation: team culture] (Google & FullStory) |
| + | * [https://blog.codinghorror.com/code-reviews-just-do-it/ Motivation: code quality] (Coding Horror) | ||
| + | * [http://www.processimpact.com/articles/humanizing_reviews.pdf Motivation: humanizing peer reviews] (Wiegers) | ||
[[Category:Software development]] | [[Category:Software development]] | ||
Revision as of 11:37, 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)
- Review checklist (Code Project)
- Motivation: team culture (Google & FullStory)
- Motivation: code quality (Coding Horror)
- Motivation: humanizing peer reviews (Wiegers)