How to master Java (j2se)

This article is my sister-in-law on how to master Java (j2se) (hereinafter referred to as the standard article) and raises standards, however, it seems impossible to tell new users how to reach that standard. First of all, it is difficult to reach this standard. It is generally impossible to reach this standard without three years. It is also impossible to cultivate the experience of practical projects. The following will explain why. Then we will give two typical examples: tij (thinking in Java) and jdk api in chm format. Tij can look at Java programming ideas (the complete Simplified Chinese version 2), if the English can, it is strongly required to read the original English version, and the chm format of jdk api can look at the recommendations of the cherami webmaster. Although I did not finish reading tij (tij was not available when I started to use Java for projects), I have browsed directories and read some chapters, I feel that the author is very familiar with Java and has rich practical experience. Many content is based on experience. It should be noted that what I said includes content and understanding the author's meaning, if you have done some projects in Java, you can look back at tij. You will find that it will be helpful if you have remembered and mastered the content of tij at the beginning. The knowledge of tij can at least meet the syntax, ideas, and standard standards mentioned in the standard article, which is also very helpful for API mastery. The reason why JDK APIs in chm format are required is that JDK APIs are very large and I personally think it is unlikely to remember so many, the API recommended by the Webmaster can easily find the corresponding description based on the class name or method name. Sometimes we just remember which class or method should be used, but I forgot the details, so I can check that stuff at this time. Now I have developed the habit of opening the CHM first and then starting to do things. We need to remind you that you cannot rely solely on it. Some things still need to be recorded by yourself. If you don't know what to use, how can you check it? You should remember at least one index, which class or method can accomplish what kind of function index. The next step is the practical project. If you do not use an applet, you will not use appletviewer and htmlconverter. If you do not package, you will not use jar. If you do not use a class library, you may not use javadoc, if you do not care about the system running performance, you may not consider using javap, if you do not run the program independently, you may not even notice how much we hate the DOS window and use Java W instead of Java to run your program, how can you use native2ascii for conversion and encoding if you have not made serialization and upgraded your class? Why do you need serialver. Without these commands or tools, you may not know what Java can do. These commands are based on command lines and may not be used to the new era of graphical interfaces, but you must know how to use them in command lines, probably the environment you need to run in your real project is a command line (Unix/Linux Server ). When developing an actual system, you cannot use editplus, notepad, Vi, or EMCS to write code. Therefore, you must have an IDE tool that you are familiar, in this way, you can manage a large project, and these ide tools cannot be used only for editors. You may need to use their debugging functions to track intractable diseases (how to set various breakpoints, in particular, set the conditional breakpoint in the loop). In addition, their code prompt function and integrated version control function. The actual project's mastery of the API is also a great test, and the real project's construction period will be relatively tight, therefore, it is a real test of your understanding of the API. If you have not done a project that requires frequent changes, you are lucky, but this is often not the case. After you modify the code, you think there is no problem. You often test the current part, but what about other parts? I want to test it all. Oh, my God! Yes, this is often the case. The regression error caused by demand changes may be our biggest nightmare! If your code structure is good, you can use JUnit to write unit test cases to ensure that your modifications do not affect the interfaces of each part. An oo-compliant system should also be a system that is easy to test or easy to compile unit test cases! If you have not fully participated in a project, you don't know how painful it is to copy files, Release versions, package, generate javadoc, run test cases, maintain versions, build milestones, build baselines, and incrementally update versions, however, if you use ant to write a script to help you complete the necessary and trivial tasks of these projects, you will feel that development projects are sometimes quite easy. Once you have experienced the real hardships of these projects, you will not be confused when you see the error information. You can clearly know where the problem is, possible causes and solutions. If you don't have any problems, you won't learn to solve them, and you won't be able to improve! To sum up, Master tij. You have a good foundation for Java syntax, APIs, ideas, and specifications, you will be more familiar with the API, and you will also know how to use the basic commands in the command line, how to choose an IDE and the most important: how to troubleshoot, debug programs, test programs, and use tools to make the computer complete those trivial routine work. The above is just my personal opinion. I hope it will be helpful to those new beginners who are eager to master Java. If you are not satisfied, you can drop tomatoes. Pai_^