How deeply does 100 Java Mistakes and How to Avoid Them cover code review?

Defines the review process and its benefits, but defers detailed guidance on making reviews efficient.

Code review

As explained in 100 Java Mistakes and How to Avoid Them

Code review is the systematic examination of source code by one or more developers to identify defects and improve quality.

Code review is an organized peer examination of committed changes. A reviewer with different experience or background can catch defects the author overlooked before release, while also improving architecture, readability, performance, knowledge sharing, and mentoring. section 1.1

Use code review as one part of a broader quality strategy:

Combine code reviews with static analysis and automated testing because different approaches expose different kinds of bugs. section 1.8
Review more than correctness: consider architecture, readability, performance, and opportunities for knowledge sharing. section 1.1
Distinguish code review from pair programming: pair programming reviews code while it is written, but demands more discipline. section 1.1
Treat review as prevention rather than a complete guarantee; no single quality technique catches every bug. section 1.8

The second look

A developer commits a change that appears correct to its author. A peer with different experience notices a defect before release and also suggests a clearer design or more readable implementation. The same collaborative review performed while the code is being written becomes pair programming. section 1.1

How 100 Java Mistakes and How to Avoid Them covers it

Cover of 100 Java Mistakes and How to Avoid Them

liveBook manning.com

Read 100 Java Mistakes and How to Avoid Them on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

"Looks Good to Me"The code review process is the organized set of rules, roles, workflows, and practices governing how code reviews are performed.
liveBook manning.com

Lead Developer Career GuideA systematic examination of source-code changes by one or more developers to identify defects and assess adherence to standards.
liveBook manning.com

A Pythonic Adventure: From Python basics to a working web appCode review is the systematic examination of source code to identify defects, risks, and opportunities for improvement.
liveBook manning.com

Shipping Go: Develop, deliver, discuss, design, and go againA code review process is a defined process for examining source code to assess its quality and provide feedback.
liveBook manning.com

Think Like a CTOCode review is the systematic examination of source code by developers to identify problems and improve quality before or during integration.
liveBook manning.com

C++ Concurrency in Action, Second EditionCode review is the systematic examination of source code to identify defects, improve quality, and check conformance to standards.
liveBook manning.com

Think Like a Software Engineering ManagerA code-review round is a job-interview assessment in which a candidate examines source code to identify issues and explain improvements.
liveBook manning.com

The Art of CodeCode review is the practice of examining proposed source-code changes to identify defects, design problems, convention violations, and readability issues before integration.
liveBook manning.com

Grokking Web Application SecurityA code review is a systematic examination of source code by one or more developers to identify defects, security issues, and other problems.

Compare how 10 books explain code review →

Related concepts

artificial intelligenceused by · Artificial intelligence is the field concerned with creating computational systems that perform tasks associated with human intelligence, such as learning, reasoning, perception, or decision-making.
pull requestuses · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
static analysiscontrasts with · Static analysis is the examination of source code or other program artifacts without executing the program to infer properties or identify potential issues.
bugaddresses · A software bug is a defect in software or a related system component that causes behavior to differ from what is intended or expected.
software development life cyclepart of · The software development life cycle is the organized set of activities through which software is planned, specified, designed, built, tested, delivered, operated, and maintained.
conversational aiused by · Conversational AI is artificial intelligence that enables software systems to interact with users through natural-language dialogue.

This explainer was generated by Manning's knowledge graph from the text of 100 Java Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.