Qoders Blog     About     Archive     Feed
by Qadeer Ahmad Khan

Effective Java Summary

Here is a collection of short summaries of Joshua Blochs great book Effective Java for easy future reference. Effective Java - Creating and Destroying Objects Effective Java - Methods Common to All Objects Effective Java - Classes and Interfaces Effective Java - Generics Effective Java - Enums and Annotations Effective... View entire post

Effective Java - Serialization

Serialization (Ch 11) This is a short summary of Joshua Blochs book Effective Java chapter 11. I have only included items that I find relevant. Be careful when implementing Serializable (item 74) Costs of implementing Serializable: It decreases the flexibility to change a class’s implementation once it has been released,... View entire post

Effective Java - Concurrency

Concurrency (Ch 10) This is a short summary of Joshua Blochs book Effective Java chapter 10. I have only included items that I find relevant. Synchronize access to shared mutable data (Item 66) Reading or writing a variable other than long or double is atomic, so why use synchronized? Synchronized... View entire post

Effective Java - Exceptions

Exceptions (Ch 9) This is a short summary of Joshua Blochs book Effective Java chapter 9. I have only included items that I find relevant. Throw exceptions appropriate to the abstraction (Item 61) Higher layers should translate lower-level exceptions to their domain. Lower level exception may not make any sense... View entire post

Effective Java - General Programming

General Programming (Ch 8) This is a short summary of Joshua Blochs book Effective Java chapter 8. I have only included items that I find relevant. Avoid float and double if exact answers are required (Item 48) In binary floating point arithmetic floats and doubles cannot represent 0.1 or any... View entire post

Effective Java - Methods

Methods (Ch 7) This is a short summary of Joshua Blochs book Effective Java chapter 7. I have only included items that I find relevant. Parameter validation (Item 38) Non-public methods should check their parameters using assertions (assert) because you as author control the circumstances under which the method are... View entire post