Project summary for the first time

This is my first time to do the project, this short 10 days so I know a lot of javaoo, but also a little experience on the project to accumulate.

Just started to write and discuss requirements analysis, I thought the project is not very big, and the function is limited, only to delete and change, and almost no business logic, although we spent a whole day, but the database is not built to achieve perfection, By the time I wrote the code, I went back to modifying the database and JavaBean, which brought trouble to the project process.

Then is the process of development, often forget the comments or comments are not clear, sometimes looking back to find the method, often can not think back at that time what the thought is written, their code sometimes need to read for a long time to understand.

Because the interface used by the project is Lawo itself, the first time to read the code did not understand the interface some very good package, in writing, and then put these in their own way and repeated encapsulation once, the effect is significantly less than the front-end designers to provide ideas, resulting in time-consuming and laborious.

Next is the real implementation phase, spending a lot of time, but also found a lot of technical difficulties, they can not be very good to all the technical difficulties to decompose. While writing the core code, the encapsulation of the method is not in place. Even if the code is written, it often bugs, and in order to complete the function, almost no pursuit of code algorithm design and operational efficiency considerations.

But in the end there is a great harvest, which includes the consolidation of basic knowledge, some business implementation of the conversion process, as well as the design of objects, three-tier architecture design pattern of understanding are more profound.

Project summary for the first time