To question the premise of the blog: https://www.cnblogs.com/Rongze-blog/p/11475280.html
Q: attempt to answer the questions you raise, and to clarify, it is how to read, practical, or figure out the discussion
Whether or not a new problem? Please suggest.
A: Due to problems previously proposed requires in-depth production environment, you may also need to continue to ask in future work, just one semester and have not been able to solve these problems, so I still have the previous view, not in detail here above.
Q: After this semester, you have mastered the skills which were not there before, how you grasp.
This semester I know the problem of their own past "wild ways" programming habits may bring. Do not pay attention to his past writing project documentation, so often lead to demand a good thought to hurried to write code, so it was not half so wasted a lot of time. And when once their own, the code of the document did not pay sufficient attention to the project code write more and more, you need to call the code has been written their own, often forget the role their own code and related parameters and return values of significance, leading to their cost a lot of time reading the previous source code.
This semester I learned a systematic software development process. Solid demand analysis and system design, project development does not allow the garden path, no worries in the realization. Detailed documentation and project database ER diagram design, not only let me Zhenti architecture project in development to keep in mind before, but also let me in the development of a modular thinking, and familiar with the role and value of each module.
Q: What is a profound experience, summed up a semester of their learning process.
Before I write documentation trouble, trouble that do test, I feel learning git trouble. But after it learned of software engineering course, I had the idea occurred innovation.
Because of his past to write code is very short, so the role of documentation and testing is not so obvious. But this time more than one item code, there are about thousands of small lines, as well as the number of more than one team, and instantly find it hard between team communication and cooperation. So a series of code management software is an absolute necessity, code documentation team also efficient exchange basis.
In particular, this whole group of unit testing, but also for the hit test and found a lot of problems. If these problems as I used to just look at the page display effect can not be found. So do not modify the code once, you run a unit test is necessary, and one-sided coverage is also very important