This time read the second chapter of the content.
A
The opening story is somewhat confusing--unit testing.
A large piece of code is listed, read through, with some understanding, is the process of unit testing. And then understand that the ultimate goal of unit testing is to check for errors and improve the quality of program software.
Well, unit testing is the programmer a good detail action, like a careful embodiment. When writing the program, it also checks the operation of the program in various situations.
(I have a question, from a certain point of view, this is a waste of time, usually write their own code, a grunt to write down, to the end, to see if it can run, run successfully. Throw it, run it wrong. Take a look again. But I think there is no problem in general, there are two problems to find out. )
Looking online, I think the meaning of unit testing is very important:
First, save time. Perhaps, in carrying out this activity, the mind is in the process of unnecessary, in fact, is to ensure correctness. If you have written a large and complex program, and then go to check, I think in addition to the huge amount of work, wrong and wrong connection between the network, modify one, also affect the other, so waste more time.
Second, facilitate cohesion. Unit testing, after all, is the inspection process, when the quality of the code tested improved, the problem can be avoidance, then and other programs to ensure the cohesion stability.
Two
Performance analysis Tools
About this tool, feel novel.
In the data structure of learning, I first realized that the program for the computer also has simplified points.
Using this tool, I think the program of slimming weight loss is also targeted improvement.
Three
Psp
Introduction: The Personal Software process (Personal software PROCESS,PSP) is a self-sustaining improvement process that can be used to control, manage, and improve the way individuals work, and is a structured framework that includes software development forms, guidelines, and procedures. The PSP is relatively independent of the specific technology (programming language, tools, or design methodology) and its principles can be applied to almost any software engineering task. The PSP can explain the principles of individual software processes, help software engineers to make accurate plans, determine the steps that software engineers take to improve product quality, establish benchmarks to measure individual software process improvements, and determine the impact of process changes on the capabilities of software engineers.
This is like a list of software engineers ' own situations. I think this is a list of directions, rigorous distribution capabilities.
In the future practice, I should pay more attention to the problem of programming habits. such as unit tests, although not on the kind of very strict checks, but each module, I should go to check check.
The method of construction read Note 02