Difference between revisions of "Code review"
(start References section) |
(→References: more good reads) |
||
| Line 5: | Line 5: | ||
See [[Code review in Phabricator]]. | See [[Code review in Phabricator]]. | ||
| − | == | + | == Good Reads == |
| − | * [https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/ Lessons From Google: How Code Reviews Build Company Culture] | + | * [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.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/ Lessons From Google: How Code Reviews Build Company Culture] (Google & FullStory) | ||
| + | * [http://www.processimpact.com/articles/humanizing_reviews.pdf Humanizing Peer Reviews] (Wiegers) | ||
[[Category:Software development]] | [[Category:Software development]] | ||
Revision as of 13:06, 9 October 2018
This page documents code review practices used for Software Heritage development.
Implementation
See Code review in Phabricator.
Good Reads
- 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)
