Jump to: navigation, search

Fuel/Code Review Rules

< Fuel
Revision as of 01:54, 3 June 2014 by Dmitry Borodaenko (talk | contribs) (Why do we need code review?)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Why do we need code review?

Code review is essential to sustainable software development process. It serves the following goals:

  1. Confirm that proposed code change is suitable for its purpose: it solves the stated problem and follows the agreed architecture.
  2. Analyze external impact of the code change: it doesn't introduce new issues, doesn't reduce stability and performance of the whole solution.
  3. Enforce code quality standards: the proposed change is well structured, well documented, and is consistent with the coding style of the surrounding code.
  4. Spread knowledge about architecture and implementation details, keep other developers up to date with current state of the code base.