1. java. To become a Java (advanced) engineer, you must learn Java. Generally, programmers only need to know some java Syntax structures. But to become a Java (high-level) engineer, you need to study Java in depth. You should study JDBC, Io, util, text, JMS, EJB, RMI, and thread more. If possible, I hope you can browse all the Java packages and find out the approximate APIs. In this way, you will find that you want to implement many functions, you can use Java APIs to achieve this without having to spend too much time on your own.
Ii. design mode. In fact, writing code is very easy, and I believe you share the same feeling. But it is hard to write well. The word "good" includes code reusability, maintainability, and scalability. Some design patterns are often used to write good code. Of course, long-term Code experience accumulation, as long as you are careful, will make you form your own code style. We believe that your code is also compatible with code reusability, maintainability, and scalability. But since our predecessors have already summed up our experience, why don't we step on the shoulders of our predecessors?
3. xml. It is almost impossible to use XML in the current system. XML is very powerful. It can perform data conversion, system configuration, and even save your system business data. Therefore, you must understand XML, including its syntax and structure. You also need to be familiar with some APIs for parsing XML, such as JDOM and sax, because in our general projects, XML often plays a role in system configuration information, you need to use these APIs to parse the configuration information and develop a perfect project.
4. proficient in one or two frameworks. As mentioned in "How to Become a Java beginner programmer", "The framework has a lot of reusable code, good hierarchies, and business control logic, framework-based development allows you to save a lot of development costs ". However, I hope that you can be proficient here. I hope that you can understand the ideas of the framework through the use of the framework. In this way, you will be more open-minded when developing a project. For example, you will think of separating SQL statements from your Java code, for example, you may consider configuring your business logic in XML or database, so that the entire project can easily expand.
5. Familiar with mainstream databases. In fact, a really large project is dedicated to database, but often many projects require you as (senior) engineers to participate in database design and SQL writing. Therefore, to better contribute to the country, we recommend that you learn more about some mainstream databases, such as sqlserver and Oracle, and connect SQL and stored procedures and triggers. If you are not from a "subject", you need to add some knowledge about database principles.
6. master one or two webservers. Although I have mentioned it again in "How to Become a Java beginner programmer", I still want to emphasize that you must be proficient in one or two types. As a Java engineer, if you want to become a senior Java engineer, you must deploy your project to Webserver, and only when you are proficient in a webserver, you can use its resources to the maximum extent, which can save a lot of time and energy.
VII. UML. I know that you want to be a senior engineer, so it is necessary for you to understand or be proficient in UML, depending on your determination to become a senior engineer and project manager. In a relatively formal development team, UML is a communication tool for discussing projects. If you want to be a software engineer, you must at least understand it. If you want to be a senior engineer, you must be able to describe your understanding of the project. Although this is not a must, it is very important.
8. analyze the problem at a high level: this is not a knowledge point, nor can it be learned through books. This is because I am more anxious than you. I hope that you can become a senior software engineer faster than a general software engineer. We hope that you will learn more from your system analysts, demand analysts, and system designers at work, and look at your projects from their perspective. At the beginning of the project, it is best to have a rough analysis and design on the project in your mind, and then compare it with them to find the difference and think about the disadvantages.
9. Tools. Unlike how to become a Java beginner programmer, you may be exposed to different tools at this stage, although you still need to use JB or idea, but you may need to know more about Rose and together, because you have to draw UML. Don't worry about Dreamweaver and other HTML editors. Let the beginners write those JSP pages.
