How to Master Java (J2SE article) beginners

J2SE This article is another article "How to calculate the Master Java (J2SE)" (hereafter referred to as the standard article) sister article, proposed the standard, but does not tell the novice how to achieve that standard seems to be justified.

The first thing to say is to achieve this standard is more difficult, not three years is generally impossible, no actual project experience edification is not possible, the following will explain why. Then give two treasure: one is Tij (thinking in Java), the other is the CHM-formatted JDK API. Tij can look at (javaresearch.org/download/thread.jsp?thread=21158) Java Programming ideas (complete Chinese Simplified second edition), if English can be strongly requested to see the original English, The CHM-formatted JDK API download address can look at the javaresearch.org/forum/thread.jsp?column=61&thread=4921 Cherami webmaster recommendations. Although I did not read the Tij (I started using Java to do the project when the Tij has not come out), but I browsed the directory and read the contents of some chapters, feel the author of Java is very familiar with the actual experience is very rich, a lot of content is a view of the experiences.

To be clear, I'm talking about content and understanding the author's meaning, if you do some projects in Java after you look back Tij you will find that if you have just begun to remember and master the content of Tij will be how much help the project.

Mastering the content of Tij can at least reach the standard of grammar, thought and specification in the standard article, and it also has great benefit to the control of API. The API for a CHM-formatted JDK is due to the fact that the JDK API is really large, personally think it is not likely to remember so much, and the webmaster recommended that the API can be very convenient according to the class name or method name to find the corresponding description, sometimes we just generally remember which class or method should be used, But forget the specific details, this time can check that dongdong, I have now become the first to put that CHM open and then start doing things habit.

Need to remind that you can not rely on it completely, some things still need to remember, if you do not know what to use how do you check it? You should at least remember an index, which class or method can accomplish the index of what function. The next step is the actual project's edification. If you do not do applets, you will not use Appletviewer and htmlconverter, if you do not pack you will not use the jar, if you do not do the class library you may not use Javadoc, If you don't care about the performance of the system you may not even consider using JAVAP, if you don't do a stand-alone program, you may not even notice how much we hate that more than a DOS window and use JAVAW instead of Java to run your program, if you're not internationalized, How can you use NATIVE2ASCII to convert code, and if you don't do serialization and upgrade your class you don't know why you need serialver. Leaving these commands or tools, you may not know what Java can do. These commands are based on the command line and may not be used to a new era of custom graphical interfaces, but you have to know how to use them at the command line, because it is likely that the environment in your real project is a command line (Unix/linux server).

When developing an actual system, you cannot use EditPlus or Notepad or VI or EMCs to write code, so you must have an IDE tool that you are familiar with so that you can manage huge projects, and these IDE tools are not intended to be used only as editors, What you might need more than that is to use their debugging features to track the incurable diseases (how to set various breakpoints, especially the conditional breakpoints in the loop), and their code hints and integrated versioning capabilities.

The actual project to master the API is also a great test, the real project duration will be more compact, so to complete what function needs to use what those classes and how to do is the real test of your API mastery. You're lucky if you haven't done a project that requires frequent changes, but that's not always the case. After you modify the code, you think there is no problem, you often just test the part of your eyes, but what about the other parts? Do I have to test it, for goodness ' '? Yes, this is often the case, because the return error caused by the change in demand may be our worst nightmare! If your code is well structured, you can use JUnit to write unit test cases to ensure that your modifications do not adversely affect the interfaces of the parts.

An OO-compliant system should also be a system that is easy to test or easy to write unit test cases! If you are not fully involved in a project, you will not know how painful it is to copy files, release versions, package, build Javadoc, run test cases, build maintenance, establish milestones, build benchmark versions, and incrementally update versions. But if you use ant to write a script to help you accomplish the tasks that are necessary and trivial, you may find that development projects are sometimes easy.

Once you have experienced the real ordeal of these projects, you will not be in a hurry when you see the error message, and you can know exactly where the problem is, what the possible causes are, and what the solution is. Without problems, you will not learn to solve problems, you will not be able to improve!

Finally summed up: Master Tij, you on the Java grammar, APIs, ideas, and specifications have a good foundation, and through actual project exercise, you will be more familiar with the API, you will also master those basic commands at the command line how to use, how to choose an IDE and most important: How to debug, debugging programs , test programs, and use tools to get computers to do trivial routine work.

The above is just a personal point of view, I hope for those who are eager to master the Java Novice has some enlightenment and help.