[Effective Java] [Item 63] Include failure-capture information in detail messages

Java Enums Essentials

Effective Java | Item 44 | Favor the use of standard functional interfaces

Effective Java | Item 43 | Prefer method references to lambdas

Effective Java | Item 42 | Prefer lambdas to anonymous classes

Block unwanted sections of web pages

Effective Java | Item 54 | Return empty collections or arrays, not nulls

Effective Java | Item 53 | Use varargs judiciously

Effective Java | Item 52 | Use overloading judiciously

Effective Java | Item 51 | Design method signatures carefully

Effective Java | Item 39 | Make defensive copies when needed

Effective Java | Item 38 | Check parameters for validity

[Effective Java] [Item 65] Don't ignore exceptions

[Effective Java] [Item 64] Strive for failure atomicity

[Effective Java] [Item 63] Include failure-capture information in detail messages

[Effective Java] [Item 62] Document all exceptions thrown by each method

[Effective Java] [Item 61] Throw exceptions appropriate to the abstraction

[Effective Java][Item 59-60] When to use checked and unchecked exceptions ? [contd...]

[Effective Java] [Item 58] When to use checked and runtime exceptions ?

[Effective Java] [Item 57] Use exceptions only for exceptional conditions

[Effective Java] [Item 19] Use interfaces only to define types

[Effective Java] [Item 6] Avoid creating unnecessary objects

[Effective Java] [Item 5] Prefer dependency injection to hardwiring resources

[Effective Java] [Item 4] Enforce noninstantiability with a private constructor

[Effective Java] [Item 3] Enforce the singleton property with a private constructor or an enum type