Due to project needs, the company should be short of staff. Is anyone interested in javaWeb a sentence from the project manager? I have never written javaEE before. If there is any concept, I learned it from training. I also watched videos and learned it myself, but I have only done small codes and had not done a complete project yet. This is the first one.
Writing code is always a shuttle, and you can do it at will. After installing MyEclipse and MySQL and building the tomcat environment, the leader gave a SpringMVC framework and said it would be written. If you don’t understand, ask. Since some methods in the framework are packaged by him, he did not spend too much effort on the framework configuration. But for a novice, it was enough. He used to only use interfaces, but now he has to send an interface to the mobile terminal and write a web background. This is an exciting thing. After reading some information, he understood the method of writing interfaces, and then started to give the interface.
In the process of writing Java, I found that the code is not the most difficult, because Android is also written in Java, so it feels quite easy to get started. However, the project implementation requires a complete logic. There will be no such idea when developing the mobile terminal. You just need to care about writing the app interface well and implementing the functions. However, the server needs to consider the entire development process. The core feeling is database design and server performance optimization, as well as coordinating the web and mobile terminals. The activities and login registration written in the previous part are quite simple. Today, the project was introduced to the mall and encountered difficulties. I thought about the database design method of the server for a whole day. Because the web terminal has not started writing, I have to think about the situation of uploading products on the web terminal, and how to give the mobile terminal interface. I want to complain here. The company has no experience in the mall and has not come up with a specific implementation plan, so I am purely researching and implementing it myself.
It’s good to write a little about the product details page. It’s so easy to collect anything. The most annoying thing is the design of attributes. At the beginning, I thought about it to design it into two tables, one is the basic information of the product and the other is the attribute information. However, after thinking about it, I found that it is almost impossible for the web to upload multi-attribute products. I can’t give the interface even if I upload it immediately. After reading some information on the Internet, I got some inspiration. I designed three tables, one basic information, one attribute, one parameter, and the last one puts the price or inventory of the parameters corresponding to the attributes. This way, I solved the inventory problem. Although the customer did not seem to have such a requirement, it would be better to be more thorough.
Products are just an example. In the past, I always thought that only one thing could last longer and develop better, but after writing javaEE, my ideas changed a little. Studying a technology can indeed develop the top of the industry, but understanding more can give you a different view of the entire project. In the past, you always cared about your own implementation and did not consider project development and extension. The design of the server side can give you a scalable thinking, comprehensively considering the coordination of each device side and the degree of project extension, and pursuing the ultimate.
I think programming is a lifelong thing. Projects are like children. They must let them grow up healthily and become stronger and stronger. Therefore, it is absolutely inevitable to know more technologies. This is also the program's "want to go out and see the world"!