[Declaration]: This article is created by Kingofark. All content in this article represent only Kingofark personal opinions, regardless of any other individual or group. Anyone or group can be copied, spread this article, but there is a complete statement. Kingofark is not responsible for non-adaptation of those who do not agree to the above or those who do not fulfill the above requirements. This declaration.
Kshi Book Hysteries - Java
[Kingofark's words]: Yes, the 5 reviews can't write ... Because I don't look at so many books ... :- is degraded, it has a time to talk. I suddenly think of "×× nutrient rice noodles", so the article "K" is a hybrid ".
"Recommendation" shows the view of Kingofark personal pairs, the range is between 0 and 10, 10 means KingofARK feels excellent (although not perfect when it is sure), 0 fingers do not have to be accumulated (although not It is definitely the dregs). "Recommendation" is inevitably bringing personal paranoia, so please don't think about it.
[1]: "Java Programming Ideology 2nd Edition" Copyright, Bruce Eckel, Machinery Industry Press
[Recommendation]: 10
[Recommended reason]:
"Thinking in java", Bruce Eckel, does not seem to introduce it. The classic original library of Machinery Industry Press is one of the most anticipated books, "Java Programming Ideology 2" The photocopy version is naturally the book I will buy. After reading, there are about three people impressed me, not, it is four: Inner Classes, Swing, JNI and books.
One: The author used nearly 30 pages (oh, can this be a introduction?) Inner Classes, the various usage and deformations are fully displayed.
Second: The huge SWING is picked out to introduce the most important point, it feels very clear, and there is no interaction between API Documentation.
Third: The introduction to JNI is short and delicate, very useful. If you are interested in viewing J2SDK source code (such as Collections), you will find a JNI when you find a "sensitive" place. For a person who studies Java, JNI is a technology that is not necessarily used but must know. The author has been interested in the J2SDK source code to see which places have used JNI.
Four: By reading this book, the author is more thoroughly understood by the principle of "entropy", strengthens the belief of "The Truth Is Out There". It is open on the table (note that there is no pressure to put any pressure, just let it be expanded - the author in the "Java Programming Ideology 2" photocopy version, first in 24 With yourself, you can evolve it into the "0-470 pages" and "471-last page"; the author tries to stick to it, but it continues to make a volume within 1 hour after sticking, the number of volume is linearly increased. In this way, any test attempting to stick to these entities will end in failure. So Kingofark's conclusion is "You observe it, it is more complicated" (this is also a X file !? Mott can save me!).
In the practice of the book, you will often see the author proposes such requirements such as Prove. The author believes that as a resultant and beginner, not only want Show, but also propof, so, in addition to the code display, it is possible to do more. You can not only use javap to see the code from disassemble, but also use Java -verbose to view detailed operation, or use JDB to detail the real-time situation of running. The heart is very basic, is explaining the mastery of your mechanism behind Java - Isn't this began to go in-depth? In addition, the author feels that many of the example programs in the book are quite good, very worthy of detailed experience and grasp.
... Oh, don't you do? Then let us look forward to the "Thinking in Java 2 / E Chinese version", Mr. Houjie.
[2]: "Java Efficient Program Guide", Joshua Bloch, Wenshan and other translations, Machinery Industry Press
[Recommendation]: 0
[Recommended reason]:
The translation is not smooth (but it is not the worst domestic, even "OK"), many sentences are not completely can't understand, but it takes some time to analyze and guess the sentence structure - on the Mandarin level from primary school For a very poor author, it is better to see the original English.
The translation of the translation in the translation cannot be said that it is not serious, and only the title in the directory:
"Item24: make Defensive Copies When Need" (Kingofark Translation: Implementing Protection Copy when needed)
Translated as:
"6.2 use protection copy"
"Item32: Avoid Strings Where Other Types Are More Appropriate" (Kingofark Translation: When using other types, avoid using Strings)
Translated as:
"7.4 Try to avoid using strings"
The original author Joshua Bloch is particularly mentioned in the foreword. The book gives a principle in accordance with the "Effective C " format. The original English book is indeed doing this, and the "item: ..." is used in the title. These principles.
Do you see the problem inside the simplified translation?
If there is a "Kingofark Efficient Life Guide", it is mentioned.
"Don't wee-wee in public (don't pee in public applications)"
Translation is "Don't pee"
Can you?
If someone has urinary uremia, isn't it to find Kingofark?
If someone teaches you "don't pee", don't you listen? ...... An, Kingofark, dare not heard.
If you have a guide to a life guide you "don't pee, do you see? ...... Nothing, Kingofark is afraid.
Efficient? Funny? ! guide? disaster? !
Finally, I want to tell those people who are willing to read: The author searched on Google, downloaded the original article 3, 5, 6, 7 chap PDF - still quite a lot of J
[Three]: "Java Program Debugging Practical Manual Second Edition", Will David Mitchell, 岚, Electronic Industry Press
[Recommendation]: 9
[Recommended reason]:
On that day, the author just saw the first edition of this book in the bookstore. I wanted to go to buy a book. When I didn't expect to buy it next time, the book "Second Edition" book is out - weird is From the description page of the book (that is, the copyright, the price of the price, is still the original version of the original version. The author did not read the book, but it feels smoothly in full text, and the translation is smooth (some places are more incapable), and the literary narratives have embodied authors' rich experience and unique insights - this is a good sign. At the technical level, the author has not found any "horse feet". The content of the book is rich: the discovery of vulnerabilities, prevents and clearing, debugger usage, testing, error message, and rich and useful appendix. From the content involved, the author thinks this is something that Java programmers should learn.
What impressed by the author is Chapter 7 "Psychological Training", Chapter 12 12.6 "Error Information", 24 regulations of computer programming, and Appendix E "Word Macro".
Chapter 7 "Psychological Training"]
The text is simple to talk about writing a comment, the name, and individual independence (7.2 Do not mix deep search and breadth search), people think that the problem is not true. It is a 7.4 "environment" to make the author can't help but. 7.4, authors pointed out that "the environment is very important in debugging", gives 9 "Help you improve the environment around you":
(Article 4) "Close the email tips on the computer screen. ..."
(Article 5) "If you accept a huge email, please do this for you for you."
(Article 7) "Find a flagpole that can rise and fall to half, and the banner, write under the banner: 'When you are half the flag, please don't bother me.' People will respect your decision."
These seem to be paranoid, selfish and even funny opinions, at first glance, maybe you only have a smile; however, the author believes that the author is very image the importance of "creating a good working environment",
In China, these areas and greatly learn from the study of learning - the domestic situation, all day work open QQ and unrelated person chatters, big people are; the heart is dry, all day acceptors, big people are there. In fact, let's talk, or that sentence, good habits and end is more important than everything - Otherwise, how many "IT-Bao Company" is too bleak?
[Chapter 12 12.6 Error Message]
12.6.1 What happened?
12.6.2 Why?
12.6.3 What will happen after?
12.6.4 What can users do now?
12.6.5 What can users do in the future?
12.6.6 Where can users get help now?
12.6.7 How can users help developers improve?
12.6.8 I have recently happened to the user's software similar problem?
12.6.9 How should users describe the problem to technicians?
12.6.10 Chat Room and Help
12.6.11 What compensation will software developers will provide users?
12.6.1 to 12.6.11 describe how to handle user-oriented error messages, and 12.6.9.1 "Why not use FAQ systems?"
"(Why don't you use a FAQ system? This is a discussion. "- No matter what the author does not agree with the author, the author has to admire the authors of the software as a product as a product (the author gives a very inspiring suggestion in 12.6.9).
The software is a product, and its service is all-round, you need to consider thoughtful for users, this is the meaning of the sky. Thinking of the domestic, the author wants to make a complaint: people always do it well - we am admired, don't serve, don't, you can't afford it ... In fact, what is this? I want to say that people will be four words: conscientiously responsible. Do we have? 12.6.12 to 12.6.18 Tell the developer's response measures when the developer encounters an error report.
12.6.19 "What should be displayed in the screen or the report" is given:
"The message should answer the user as follows:
l What happened? ……(slightly)
l What happened next? ……(slightly)"
[Appendix C "24 regulations of computer programming"]
These 24 may not count any classics, some are also familiar with the terms. The author believes that such an entry is more good, printing out a place in a conspicuous place, absolutely will not be good.
[Appendix E "Word Macro"]
This chapter gives a Word macro code. It is still very valuable (especially you can show friends "How to use the computer" "" Magic "use wordj). The book is given on handling bookmarks and jump, hidden text, personal comments, green keywords, programming help, and providing URLs that can get more macros.
Recommendation 9, the author did not see more of the same type of book. This book is not perfect, but it is important and necessary.
(Finish)
