Effective Java Programming Language Guide
Effective Java is an explicit (and acknowledged) homage to Scott Meyer's Effective C++. Josh Bloch shares the programming practices of the most expert Java programmers with the rest of the programming community. Distilling the habits of experienced programmers into 50 short stand-alone essays, Bloch has laid out the most essential and effective Java rules, providing comprehensive descriptions of techniques. The essays address practical problems that all Java programmers encounter, presents specific ways to improve programs and designs, and also shows how to avoid traps in Java programming. An enormously useful book, each essay contains top notch code examples and insightful "war stories" that help capture the students' attention.
2. Creating and Destroying Objects.
Enforce the Singleton Property with a Private Constructor.
Enforce Noninstantiability with a Private Constructor.
Avoid Creating Duplicate Objects.
Eliminate Obsolete Object References.
3. Methods Common to All Objects.
Always Override HashCode When You Override Equals.
Always Override toString. Override Clone Judiciously.
Consider Implementing Comparable.
4. Classes and Interfaces.
Favor Immutability. Favor Composition Over Inheritance.
Design and Document for Inheritance or Else Prohibit It.
Prefer Interfaces to Abstract Classes. Use Interfaces Only to Define Types.
Favor Static Member Classes Over Non-Static.
5. Substitutes for C Constructs.
Replace Unions with Class Hierarchies.
Replace Enums with Classes.
Replace Function Pointers with Classes and Interfaces.
Make Defensive Copies when Needed.
Design Method Signatures Carefully.
Use Overloading Judiciously.
Return Zero-Length Arrays, Not Nulls.
Write Doc Comments for All Exposed API Elements.
7. General Programming.
Know and Use the Libraries.
Avoid Float and Double if Exact Answers are Required.
Avoid Strings where Other Types are More Appropriate.
Beware the Performance of String Concatenation.
Refer to Objects by their Interfaces.
Prefer Interfaces to Reflection.
Use Native Methods Judiciously.
Adhere to Generally Accepted Naming Conventions.
Use Checked Exceptions for Recoverable Conditions.
Runtime Exceptions for Programming Errors.
Avoid Unnecessary Use of Checked Exceptions.
Favor the Use of Standard Exceptions.
Throw Exceptions Appropriate to the Abstraction.
Document All Exceptions Thrown by Each Method.
Include Failure-Capture Information in Detail Messages.
Strive for Failure Atomicity.
Don't Ignore Exceptions.
Avoid Excessive Synchronization.
Never Invoke Wait Outside a Loop.
Don't Depend on the Thread Scheduler.
Avoid Thread Groups.
Consider Using a Custom Serialized Form.
Write ReadObject Methods Defensively.
Provide a ReadResolve Method when Necessary.