Description

This book is a useful companion for anyone learning to write clean Java code. The authors introduce you to the fundamentals of becoming a software craftsman by comparing pieces of problematic code with an improved version to help you to develop a sense for clean code. This unique before-and-after approach teaches you to create clean Java code.

Learn to keep your booleans in check, dodge formatting bugs, get rid of magic numbers, and use the right style of iteration. Write informative comments when needed, but avoid them when they are not. Improve the understandability of your code for others by following conventions and naming your objects accurately. Make your programs more robust with intelligent exception handling and learn to assert that everything works as expected using JUnit5 as your testing framework. Impress your peers with an elegant functional programming style and clear-cut object-oriented class design.

Writing excellent code isn’t just about implementing the functionality. It’s about the small important details that make your code more readable, maintainable, flexible, robust, and faster. Java by Comparison teaches you to spot these details and trains you to become a better programmer.

Contents and Extracts

• Foreword
• Acknowledgments
• <b>Welcome!</b>
  • Who Should Read This Book
  • Why Read This Book?
  • How to Read This Book
  • Online Resources
  • Get Ready for Your Mission to Mars
• Start Cleaning Up
  • Avoid Unnecessary Comparisons
  • Avoid Negations
  • <b>Return Boolean Expressions Directly</b>
  • Simplify Boolean Expressions
  • Avoid NullPointerException in Conditionals
  • Avoid Switch Fallthrough
  • Always Use Braces
  • Ensure Code Symmetry
  • What Have You Learned?
• Level Up Your Code Style
  • Replace Magic Numbers with Constants
  • Favor Enums Over Integer Constants
  • Favor For-Each Over For Loops
  • Avoid Collection Modification During Iteration
  • Avoid Compute-Intense Operations During Iteration
  • Group with New Lines
  • Favor Format Over Concatenation
  • Favor Java API Over DIY
  • What Have You Learned?
• Use Comments Wisely
  • Remove Superfluous Comments
  • Remove Commented-Out Code
  • Replace Comments with Constants
  • Replace Comments with Utility Methods
  • Document Implementation Decisions
  • <b>Document Using Examples</b>
  • Structure JavaDoc of Packages
  • Structure JavaDoc of Classes and Interfaces
  • Structure JavaDoc of Methods
  • Structure JavaDoc of Constructors
  • What Have You Learned?
• Name Things Right
  • Use Java Naming Conventions
  • Follow Getter/Setter Conventions for Frameworks
  • Avoid Single-Letter Names
  • Avoid Abbreviations
  • Avoid Meaningless Terms
  • Use Domain Terminology
  • What Have You Learned?
• Prepare for Things Going Wrong
  • Fail Fast
  • Always Catch Most Specific Exception
  • Explain Cause in Message
  • Avoid Breaking the Cause Chain
  • Expose Cause in Variable
  • Always Check Type Before Cast
  • Always Close Resources
  • Always Close Multiple Resources
  • Explain Empty Catch
  • What Have You Learned?
• Assert Things Going Right
  • Structure Tests Into Given-When-Then
  • Use Meaningful Assertions
  • Expected Before Actual Value
  • Use Reasonable Tolerance Values
  • Let JUnit Handle Exceptions
  • Describe Your Tests
  • Favor Standalone Tests
  • Parametrize Your Tests
  • Cover the Edge Cases
  • What Have You Learned?
• Design Your Objects
  • <b>Split Method with Boolean Parameters</b>
  • Split Method with Optional Parameters
  • Favor Abstract Over Concrete Types
  • Favor Immutable Over Mutable State
  • Combine State and Behavior
  • Avoid Leaking References
  • Avoid Returning Null
  • What Have You Learned?
• Let Your Data Flow
  • Favor Lambdas Over Anonymous Classes
  • Favor Functional Over Imperative Style
  • Favor Method References Over Lambdas
  • Avoid Side Effects
  • Use Collect for Terminating Complex Streams
  • Avoid Exceptions in Streams
  • Favor Optional Over Null
  • Avoid Optional Fields or Parameters
  • Use Optionals as Streams
  • What Have You Learned?
• Prepare for the Real World
  • Use Static Code Analysis Tools
  • Agree On the Java Format in Your Team
  • Automate Your Build
  • Use Continuous Integration
  • Prepare for and Deliver Into Production
  • Favor Logging Over Console Output
  • Minimize and Isolate Multithreaded Code
  • Use High-Level Concurrency Abstractions
  • Speed Up Your Program
  • Know Your Falsehoods
  • What Have You Learned?