Difference between revisions of "Code review"

From Software Heritage Wiki
Jump to: navigation, search
(Good Reads: add guidelines from the Code Project)
(Good Reads: organize by topic)
Line 7: Line 7:
 
== Good Reads ==
 
== Good Reads ==
  
* [https://www.codeproject.com/Articles/524235/Codeplusreviewplusguidelines Code review guidelines] (Code Project)
+
Good reads on different angles of code review:
* [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://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/ Lessons From Google: How Code Reviews Build Company Culture] (Google & FullStory)
+
* [https://www.codeproject.com/Articles/524235/Codeplusreviewplusguidelines Review checklist] (Code Project)
* [http://www.processimpact.com/articles/humanizing_reviews.pdf Humanizing Peer Reviews] (Wiegers)
+
* [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: