These kinds of questions often lead to holy wars since they end up being a matter of taste and style.įor Java, there’s a general style guide (unfortunately not updated for the latest versions of Java). These can get pretty detailed, even to the point of specifying whitespace (how deep to indent) and where curly braces and parentheses should go. Most companies and large projects have coding style standards (for example, Google Java Style).
#Code on time review code#
In 6.005, we’ll do code review on problem sets, as described in the Code Reviewing document on the course website. In open source projects, particularly, much conversation happens in the context of code reviews.Ĭode review is widely practiced in open source projects like Apache and Mozilla.Ĭode review is also widely practiced in industry.Īt Google, you can’t push any code into the main repository until another engineer has signed off on it in a code review. It’s analogous to proofreading a term paper.įinding bugs, anticipating possible bugs, checking the clarity of the code, and checking for consistency with the project’s style standards.Ĭode review is an important way that programmers learn and teach each other, about new language features, changes in the design of the project or its coding standards, and new techniques.
Code review is careful, systematic study of source code by people who are not the original author of the code.