Stockertim Dictionary · Artificial intelligence · Technology
Code review
Also called code reviews, peer code review
In short
Code review is a structured read of code by a person before it is used, to find errors, security risks and unclear parts, and to confirm it does what was intended.
- Beginner
- Process
- Checked
In detail
Code review is the practice of having someone other than the author read a change to software before it is merged or run on live systems. The reviewer checks that the code does what was asked, handles unusual inputs, follows the team's conventions, is readable and introduces no security weakness.
A typical review works through a short list: does the change match the request; are inputs validated; are errors handled; are secrets such as passwords or keys kept out of the code; are there tests and do they pass; and is anything removed or overwritten that should not be. Many teams use version control so that each change is reviewed as a small, separate unit that can be reverted.
Code review matters more when code is written with an AI coding assistant. Generated code is produced quickly and looks tidy, which encourages approval without real reading. It can still call functions that do not exist, use insecure defaults, mishandle edge cases or quietly do more than was asked, such as deleting files.
For non-developers writing small scripts or macros, a lighter version still helps: read every line, ask the assistant to explain anything unclear, test on a copy, and ask a technical colleague to look before the script touches important data.
Worked example
A developer at Lagoon Logistics reviews a 120-line AI-written script that uploads delivery records to the accounts system.
- She checks the request against the code and finds the script also deletes the local records after upload, which nobody asked for.
- She finds an access key typed directly into the code and asks for it to be read from a secure setting instead.
- She runs the tests on sample data and adds one for a record with a missing date, which the script had not handled.
The change is approved only after the deletion is removed, the key is moved out of the code and the new test passes.
In practice
Code review happens through version control tools, pair working or a simple read-through. Common rules are that no change reaches live systems unreviewed, that reviewers understand every line they approve, and that AI-written code gets the same review as human-written code.
Watch out
- Approving code you do not understand is not a review; ask for an explanation or a smaller change.
- Passing tests show only what the tests cover; a review also looks for what they miss.
Learn it properly
Official sources
- Guidelines for secure AI system development · National Cyber Security Centre
- Top 10 for large language model applications · OWASP Foundation
Facts last checked on 3 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.