"Java programming thought" reading notes

Objective

This month has not been updated, that is, has been reading this "Java programming ideas", this book can be in the Java industry is a vivid book, no matter who talks about this book is agreed, whether this person really read this book, say Ah, this book is very good. And then look at the thickness of the book here, wow, thick really more than a little, so a lot of people look at not long to give up, can not see, but based on its thickness, said, this is a good book. Some people say that it is better to look at the actual technology than to read a book that is useless and even laugh at those who are watching. So in my world, if a book has not been read, if you make a comment, it doesn't make any sense. So I really read it carefully and wrote a lot of notes, but I won't write them down because it's too much.

However, it is really not easy to read such a thick book. I thought a lot of ways to record my reading notes, but at last I feel bad, I think my notes should have the following several functions.

1, as a clue, in the future I can quickly review and query.

2, already know, do not mention, do not know, the key record.

3, so that even if you have not seen the people can know what is worth them to see in the end.

So in the end I decided to use a way of questioning, or a way of stating, to record my reading notes, if you can answer the following questions, or to understand the contents of the statement, then the contents of the certificate in fact you already understand. If the answer is not clear, or the answer is unclear, then you can check the answer on the Internet, or browse through the books.

Here are all the notes I recorded.

Notes section

1. What is OOP?

2, public, private, protected permissions

3. What is a combination? What is inheritance?

4. How to allocate Java memory

5. References to Objects and objects

6, Java Virtual Machine garbage collection basic strategy; stop-copy; Mark-sweep;

7, control access to members to: Let the user do not touch the parts they should not touch, in order to let the designer of the class library can change the internal working method of the class

8. How are combinations and inheritance chosen?

9. Final, static, and the order in which the corresponding methods and blocks are loaded and initialized

10, the role of polymorphism is to eliminate the coupling between the types of relationships, polymorphism is a programmer: "The change of things and the non-edge of things separate" technology.

11, using the difference between the expression of inheritance, and using the field to express changes in the state

12. Comparison of interfaces and abstract classes

13. Anonymous Inner class

14. The role of generics is to prevent objects of the wrong type from being placed in the container at compile time

15, the comparison between the containers, such as ArrayList and LinkedList, and so on, such as set, HashSet, TreeSet, etc.

16, Priority queue Priorityqueue

17. An important principle of exception handling is "Catch exceptions only if you know how to handle them"

18, "Report" function is the essence of the anomaly

19, the non-variability of string

20, StringBuffer and StringBuilder

21. All classes are dynamically loaded into the JVM for the first time they are used

22, load-"link-" initialization

23, Instanceof is what method?

24. What is a dynamic agent?

25. Using generic methods to encapsulate tool classes

26. You cannot get any information about the generic parameter types inside the generic code.

27. Array differs from three aspects of other containers: efficiency, type, ability to save basic types

28. How is the interior of HashMap implemented?

29. What should I pay attention to when using i\o operation file?

30. What is Object serialization

31, enum and switch is a pair of friends

32. Annotations provide a formalized way for us to add information to our code so that we can use it conveniently at a later point in time.

33. Annotations can help us avoid writing cumbersome deployment profiles.

34, processes and threads, a process is a self-contained program running within its own address space, and a thread is a single sequential control flow in the process.

35. Two ways to implement threading

36, the role of the thread pool

37. Lock to prevent two tasks from accessing the same resource, implicit, explicit

38, the volatile keyword is what to do with

39. Wait with notify and Notifyall

40. Deadlock four conditions: at least one resource cannot be shared, at least one task it must hold a resource and is waiting to acquire a resource that is currently held by another task, the resource cannot be preempted by the task, must have a loop wait

41, to prevent deadlocks as long as the destruction of any one of the four conditions

42, there are many lock-free containers such as CONCURRENTHASHMAP, etc.

43. Make sure that multiple threads do not read and change a resource at the same time, which is the biggest problem the thread produces

Personal Summary

As a modern fast-paced life, can calm down to see the book, really not easy, so I think I see not careful enough, many times also missed a lot of focus. But I'm sure you can find them.

For this book, after reading, I found a few places you need to be aware of.

1. This book is considered good because it covers almost all the basics of the Java language, which is like a museum where all the collections are neatly placed.

2, the code of this book is more powerful than the text, I can accurately say, my notes in the book is almost a lot of the code to write comments, the same page, the code is at least twice times more time to see the text, if you skip directly, then you will miss a lot of wonderful parts.

3, Design Patterns in the book inside the flexible interspersed, I am really lucky I read this book before the design mode, otherwise the process of reading a lot of time will not understand what it said the design mode, and thus looked after, I also more understand the use of some design patterns.

4, now the network developed, a lot of questions on the Internet have ready-made answers, so rarely will open the book to find, and this book is too heavy, not suitable to carry, so please read the time to keep a heart, once understood, do not know on the mind.

5, the letter of the book is not as good as no book, and now development so fast, Java itself is constantly developing, 1.9 must have, so many books on the things may be outdated, many have been in the long river of history, so read more look outside the world.

"Java programming thought" reading notes