Java programming ideology has come to an end

I started to read "Java programming thoughts" in July. Today I have no motivation to read it, so I decided to come to an end.

Why is there no motivation? The time for reading this book is in the spare time. Sometimes I don't want to read it when I come back from work, so sometimes I read it intermittently and find that reading it is not efficient. Then, I feel that I really need some java experience to better understand this book, but I am still working on C, so I have never used Java. There is no need to go further. Let's get down to the basics, and there will be a good starting point for writing Java later.

This book is a summary of 2011. I have read this book since I started my work. Although intermittent, I have read it twice. Java focuses on object-oriented, polymorphism, and internal class applications. What I cannot understand most is generic, so I haven't read the 15 chapters. The application of the design model described in the book is also quite classic. I'm excited that the master wroteCodeThe application design pattern makes it hard to imagine when you will write and write that code.

Next, the target is the operating system.