Summary of the H3C aggregation layer switch authentication online number display system

Previously summary: accidentally picked up a teacher said a small program, and then plan 7 days (actual 10 days) of the small project came out.

(1) Time and quantity of works. Before I started talking to the teacher about the specific needs, I guessed the time to complete the small project with a sense of feeling. Then, with the teacher to determine the demand, then look back to my own estimated time. Two words, stupid. In fact, as a student of science and technology, we should pay attention to the evidence, not to judge by intuition. The determination of the amount of work, not by personal feeling can be OK. The right approach should be to exercise your ability to estimate the amount of work, the amount of code, or the time required for each module in an ongoing practice. I'm far from that point. From my own time on this small project and the comparison of the previous forecast, the gap is really big.

(2) about the project extension. Initially agreed to the teacher 7 days after the completion of this small project, but until the deadline, I will only complete the core functions, and then, anxious. or report to the teacher, this is the first time failure. Then the teacher affirmed my current completion of the work, and gave me an extension of the day, the result is still not completed, this is the second failure. At this point I "thought" the relevant technical prototype has been determined, so the teacher postponed another day. The result, incomplete, is the third failure. This time I was embarrassed to tell the teacher, I silently do a day, finished to the teacher, the result is completed. In fact, for the first time, the reason for the failure is that it is unreasonable to plan for time and procrastination. The second failure, the previous unit test is imperfect, the function set is incomplete, the system boundary is blurred. This has resulted in previous rework and is therefore postponed. Third failure, overestimate their ability to grasp the technical prototype is not in place. Among them, there is a big problem, and after the third failure, there is no timely feedback to the teacher, this is the wrong approach. Should inform the teacher in time. Your mindset needs to change. After the project is completed, submit it to the teacher. Asked the teacher about the project extension, the teacher gave the answer is that few projects can not be postponed, especially the initial experience, is usually painful. If someone tells you that you have been successful, he is lying to you. I think it is my own mentality and ability of the problem, the project technical difficulty grasp not in place, the time is not in place. Practice is not enough.

(3) present the project progress to the user. When I first showed the teacher the finished function point, I recorded a video of the operation, sent it to the teacher, and then described it in words. In fact, I am wrong in this way. The user doesn't care how you do it, what he needs to see is the execution process in the user's needs, not the execution of the system. At the same time, it should be a natural language when describing to the user. To the user to see what he wants to see. My ability to describe requires continued exercise.

(4) Technical prototyping issues in the project. This time the programming language involved is JS (jqery), Java, HTML. Java-specific servlets interact with JSP (HTML), List-to-json in Java, jquery manipulation DOM elements, Ajax technology, Highcharts, Java multithreading, Java timed Tasks, and JS timed refreshes. Feeling, their basic knowledge is really not solid, reading + practice, leak check.

(5) The most risky part of the project should be done first. Just put this sentence on the heart, this time really realized. Previously did not touch the Java multithreaded programming, disturbed to complete the technical prototype, initially confirmed in doubt to complete the part, however, after two rework, after several failures to determine the core module to meet the desired effect. Painful lesson.

(6) In the continuous practice, it is possible to succeed. People who will stick to it will do less. Real execution. It feels good.

(7) The last point, the words will be done, not easy to promise, once the promise of other things must be done, if not, should also give reasonable reasons rather than explain or evade. Less and fewer people can do that.

Send oneself often say a word, "road long its repair far XI, I will go up and down and quest."

Finally, thank the teacher gave me a chance of redemption, a chance of growth.

Summary of the H3C aggregation layer switch authentication online number display system