"Boulevard to Jane-The thought of software engineering practitioners" third note

The 6th chapter from programming to Engineering

Language is just a tool, language without the so-called good or bad, only suitable, to which language mastered more skilled, ape to human, "learn to make and use tools" is the most important sign. Do not blindly to say which language is better, which language is not good, because it is in specific projects can be reflected in, I have always believed that "there is a very heli", at least in the early days of a language, it is also with the need to emerge. But you should know that a good project manager is not a person who does not make mistakes, but the one who succeeds with as few failures as possible. From the initial simple programming, to the current engineering team's organization development, implementation (a software) is the ultimate goal. So it can be said: implementation, is the essence of software development needs. method is an inductive summary of the existing behavior. Thus the method of implementation is always the first, then the analysis and design method.

The 7th chapter the software engineering in reality

The software industry today is not the result of a quarrel between some people (programmers or critics, for example), but the checks and balances of big companies. Borland and IBM, IBM and Sun, and sun and Apple are doing the same thing, and they have their own calculations. They suppress their opponents ' strengths and leverage their opponents ' and allies ' strengths to weaken their weaknesses or complement their strengths. Jumping out of the outside, Microsoft is not their common rival, but just because Microsoft occupies the crest of the head, it becomes the target. It's not the name of Microsoft that everyone is facing, it's just this position, and whoever makes that position will be exposed to the same risks and pressures. The importance of thinking about costs: project plans without costs are not supported by the operators, and the cost of the project is chronic poison, and the most deadly risk is the depletion of costs.

The 8th chapter is thinking or thinking

Contradiction is to achieve the goal and guarantee the quality, in the project balanced triangle (time, resources and function) discusses the goal question, but does not discuss the quality question. In other words, the classic textbook always focuses on how to complete projects faster, reduce resource usage, and achieve more functionality. However, even if this relationship is balanced, the results of the project can still create a natural handicap. Because the goal may be established in the balance, but the quality is controlled in the process. Even with the balance of time, resources and functionality, even if customers, project groups and companies are equally satisfied with this balanced "goal", it may still be "impossible". The word "law" in "Change of law", if interpreted as "law", can be used in software engineering. "Tao" is the law, if Ming "Tao", but can irresistable, so do software engineering is alive. Just as it is difficult to lyrics, unknown Tao, is not wise, not wise, and thus in the implementation of software engineering inevitable blindness and stagnation. Another layer of "knowing the law" means "knowing the principle". Understand "why this" or "why not". This is a common problem in software development, most people do not know how to use the techniques and methods, and once there is a problem, it is not good to investigate these techniques and methods. The real problem is that these people do not know the principles of these techniques, techniques and methods, and therefore do not know how to adapt or avoid mistakes.

"Boulevard to Jane-The thought of software engineering practitioners" third note