Code Simplified

Documentation

• Document the Why, not the What
• What Type of Comment Should You Use, and How Do You Format Them

Naming

• Avoiding Redundant Method and Variable Names
• When and When Not to Abbreviate Names
• Scope and Good Variable Naming

Values

• Simplifying Magic Literals

Code Layout

• Horizontal and Vertical Code Formatting
• Code Indentation and Code Simplicity
• Grouping Statements by Concept, not by Variable

Code Duplication

• How do You Know if Code is Duplicated or Not
• Removing Code Duplication Using Loops and Collections

Nulls

• Why Using Null is so Bad
• Can Null Really Simplify Code?
• Handling Null at Compile Time

Control Flow

• Things to Avoid When Writing if Statements
• How to Simplify if Statements
• How to Lazy Load Without Using if Statements
• Being Positive When Writing if Statements

Methods and Functions

• Simple Return Statements and Values
• How Many Return Statements Should a Function Have?
• Clean Method Overloading

Classes

• Clean Constructor Overloading

Patterns

• The Principle of One Operation Per Line of Code
• How to Implement a Simple Paging Model
• Factory Method Pattern
• The Util Class Antipattern
• Simplifying Your DAO Layer
• When to Choose Inheritance Over Composition
• When to Choose Composition Over Inheritance
• Proper Use of Nested Classes

Tests

• The Worst Thing to do When Writing Tests
• Simplifying Unit Tests with Loops
• How to Write Simple Unit Tests
• Proper Use of Verify in Unit Tests
• Simplifying Logging in Test Code