Perhaps you have read my Xiaowen "How to become a Java Junior Programmer", which only introduces some knowledge that a Java programmer should have. I believe that you will never think about doing a primary programmer, gotting the boat developed by the software, you must have a great ideal, such as being a senior member in a relatively short period of time, and make a software in the near future Project manager, if it is possible that you must have a high level in a company, or have its own company ...
Perhaps it is a bit far, but it is definitely your dream. Before the opportunity has not arrived, let us first do every step at the feet. Now become a (senior) engineer.
In addition, I want to explain that you want to learn some Java senior knowledge from this article, because this article tells you what is a (advanced) Java engineer should learn, not tell you the specific knowledge details.
First, Java. To become a Java (Advanced) engineer, you must learn Java. The general programmer may only need to know some Java's grammatical structure. But to become a Java (Advanced) engineer, you have to study in Java. You should study more JDBC, IO, UTIL package, Text package, JMS, EJB, RMI, thread. If possible, I hope that you will browse all of Java's packages, know the probably API, so you find a lot of features you want to achieve, you can implement it through Java's API, you don't have to pay too much brain. .
Second, design mode. In fact, writing code is very easy, I believe you have the same feeling. But how to write is more difficult. This "good" word includes code reusability, maintenanceability, scalability, etc. How to write a good code is often necessary to use some design patterns. Of course, long-term code experience accumulates, as long as you use your heart, you will form your own code style. I believe that your code is also comparable to the reusability, maintainability, and scalability of the code. But since the former person has given us a summary of experience, why not step on the shoulders of the former person?
Third, XML. It is almost impossible to use XML in the current system. XML's function is very powerful, it can do data conversion, do system configuration, and even save your system business data. So you must understand XML, including its grammar, structure. You also need more skilled use of some APIs, such as Jdom, SAX, etc., because XML often acts as system configuration information in our general project, you need to resolve these configuration information, develop a perfect project .
Fourth, it is precisely using one or two frames. As mentioned in "How to become a Java Programmer", "the framework has many reusable code, good hierarchical relationships and business control logic, the framework development allows you to save a lot of development costs." But I hope that you can be proficient, more is to see the use of the framework through the framework. This way you think when you develop a project, such as you will think of SQL statements with your Java code, so you will consider configuring your business logic to XML or databases, so that the entire project is easy to expand .
Five, familiar with the mainstream database. In fact, the truly large project is someone else to do a database, but there are often many projects as required as (advanced) engineers, you are also involved in the design of the database and the writing of SQL. So in order to contribute to the country, it is recommended that you understand some mainstream databases, such as SQL Server, Oracle, multi-connection SQL and stored procedures, and triggers. If you are not a "class", you also need to add some knowledge of database principles.
Sixth, proficient in one or both of the WebServer. Although I have said it again, I still have to emphasize one or both of you are going to be. Because as a Java engineer, you want to become a high-end Java engineer, youdomacly to deploy your project to WebServer, and only when you are proficient in a webserver, you can use its resources to maximize Can save a lot of time and energy. Seven, UML. I know that you will definitely want to be a senior engineer, so you need to know or master UML, depending on how great you have determined to be a senior engineer and project manager. In a comparative formal development team, UML is a discussion of the project's communication tool. You have to be a software engineer, you must learn at least, you have to do a senior engineer, you have to describe your understanding of the project. Although this is not a must, it is very important.
8. Standing at a high degree of analysis: This is not a knowledge point, nor can it be learned by books. I only mention this because I am still anxious than you, I hope you become a senior software engineer faster, not a general software engineer. I hope that you will learn from your system analyst, demand analyst, system designer in your work, and stand on their angle to see your project. It is best to have a general analysis, design, design, then compare them in your mind, and then find the difference, think about the shortcomings.
Nine, tools. Unlike the "how to become a Java primary programmer", you may come into different tools at this stage, although you need to use JB or IDEA, you can know more about Rose, together, because You have to draw UML. Don't have a lot of HTML editors such as Dreamweaver, those JSP pages let primary programmers will write.
