Effective Java Reading

think in Java , effective Java These two books have always been in the Java ecosystem for enduring. Originally wanted to turn over think in Java this mountain, but read half to give up. Too long, so unbearable, and then big interest, also by too much cumbersome text erased, but can not be denied that it covers a lot of classic Java knowledge, may have to wait for me to mature a little more patience, and then come back to turn this book.

Two or three years ago I bought this effective Java from Google chief architect Joshua Bloch 's classic, when I touch Java time is not very long, I think will write a few Hello world, Just want to explore the original forest, the results can be imagined, there is no return.

Get the book that day, I excitedly back to the dorm, opened the book read the introduction, mostly with the usual book no difference, blow a blow the author's life, find a few industry Daniel again blow this book, finally do a summary, who who can read this book, almost like this. After reading the introduction, I found the book to be said that I had finished reading it. Do not misunderstand, this is not I am bragging, but I can not understand the rest of the part, to tell the truth, or a little lost, I TM even the first chapter are indefinitely, I can see what. The first paragraph and the Book of the fate of the basic is so over.

Over the next two years, I have been involved in some practical projects, learning such things as design patterns, the JVM, reading some of the JDK's source code implementations, and a deeper understanding of the set and framework principles. I went back to see this classic that I couldn't have done two years ago. As the saying goes, where to fall, where to climb up is not. The Book of 78 principles, roughly including concurrency, design patterns, polymorphism, class libraries, exceptions, serialization and other related knowledge, from security, efficiency, performance, expansion, readability, these aspects of the

How do I use Java efficiently?

This book has a lot of, you have encountered in the actual production, or is about to encounter, or the future will encounter some design ideas, can help you shape programming ideas. Before you can read this book, this book is the goal of your efforts, after reading this book, this book shape your programming ideas. After reading it, maybe the value of this book really reflects, you can not have encountered in the actual development of all the problems, this book will be your future development of the compass. Help you to choose the best solution from the complicated coding design.

I have turned over the book over the past few days, but there are a lot of things I do not understand, some may be accumulation is not enough, some because of translation reasons, has been difficult to read. English good classmate, can read the original, relatively labored a little, harvest nature is also proportional. What impresses me most is the knowledge of the generics section, which I would like to mention for space reasons.

New Hashmap<string,map<string,object>> ();

It feels pretty common code, but it doesn't look right, the next section of the generic statement feels a bit redundant causing huge waits, and the students who are familiar with guava may know what I'm going to say.

 Public class typeinference {    publicstatic <K,V> hashmap<k,v> newinstance () {         returnnew hashmap<k,v>();    }      Public Static void Main (string[] args) {                map<String,Map<String,Object>> map =  Typeinference.newinstance ();            }}

You may be able to use the type deduction to make it look pleasing to the eye, but unfortunately, the JDK collection tool class does not have the above static method, only to write one by itself.

The book also has many seemingly obscure, but very pleasing to write things. In addition to some more deep-seated exploration, to Javaer help is quite large, welcome to read the Book of students to learn to communicate together.

Effective Java Reading