*** ![[code-review-pyramid.jpg]] - Changes do what the developer intended. Everything works as needed in the task. - Changes aren’t too complex to understand. All members of the team can understand every line of code and can easily maintain this code in the future. - The author picked good names for everything. They’re not long and hard to read. - Author added comments where necessary. Good comments are those that explain why a piece of code exists — and aren’t just explaining what the code is doing. If the code isn’t clear enough to explain itself, then the author should make the code simpler. - Changes follow the style guide. If you don’t have a style guide in the company, you should definitely create one. - Do changes need documentation? If they change the main part of basic or main functionality (build, test, API, integration, etc.), then the author needs to create or update the documentation about it.