Okuzeka
Software Engineering vocabulary · Code Review and Code Quality

Code review

Meaning in software engineering, with examples

/ˈkoʊd rɪˌvjuː/nounCore term

In software engineering, code review means: The practice of teammates reading and commenting on each other's code changes before they are merged, to catch problems and share knowledge.

In Turkish: kod incelemesi, kod gözden geçirme

How it is used

Part of the everyday workflow on GitHub or GitLab. You ask for, do and pass a code review. 'Review' is also used alone as a verb: 'Can you review my PR?'

Example sentences

  1. Every change needs at least one code review before it goes into main.

  2. During code review, Elif noticed that the query runs inside a loop.

Common collocations

  • do a code review
  • ask for a code review
  • pass code review
  • code review comments
  • pull requestA request to merge your code changes from one branch into another, so that teammates can review and discuss them first.
  • address feedbackTo deal with the comments people gave you, by making the requested changes or explaining why you chose a different approach.
  • LGTMShort for 'looks good to me': a quick written comment a reviewer leaves to say that a code change is fine and can be merged.
  • nitpickA very small, optional comment in a review about details like naming, spacing or wording, which should not block the change. Often shortened to 'nit'.
  • refactorTo improve the structure of existing code, making it cleaner or easier to change, without changing what it does for the user.

More terms: Code Review and Code Quality

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: