Through the introduction of the first chapter, we understand what software engineering is, and why it is called Software engineering, and what effect he has on our lives.
Through some examples I also recognize the importance of customer demand analysis, as Chiu as the arithmetic, gradually more functions and needs.
In the second chapter, I also recognize the importance of personal ability and testing, which runs fast in a program for a few seconds instead of minutes.
A good unit test also has a lot of standards, through the analysis of the standard can find many defects, it is necessary to write down the test method.
So if we blindly optimize without analysis, it may be more effective.
The third chapter is the development of software engineers, the main method to evaluate the level of software engineers. The path of development of this profession.
70 pages also talk about the relationship between growth and code volume, and have a variety of engineers, but also have self-knowledge.
How can 1.2.4 make "good enough" software?
For the user's expectations and bug fixes of the program, even 0.01% of the probability to be foolproof, like the aircraft security measures, but how to find and to achieve it?
2.2 How can the performance analysis tool be fast?
Before running a performance analysis, what are some of the functions that let us anticipate the most time-consuming, or those statements. Some say processing files, because I/O takes time, some say sort,
Some say it's about dealing with every word. Others say that it is advisable to sort and process each word at the same time, so that it can speed up. To increase CPU utilization should be concurrent. Modifying part of the Code also
Can speed up, for example, on page 47.
3.4 Why to learn, how to learn, core competitiveness is what?
Multi-communication, multi-dozen code, according to the needs of customers, programming language, problem-faced attitude to deal with the problem of ideas and methods
The first three chapters of the Law of construction