Reading the sixth chapter of "Boulevard to Jane"--from programming to engineering

Language is just a tool, in the process of learning programming, we are constantly exposed to a wide range of languages, learning and using them. We are anxious about not being proficient in a language, and of course we are excited by the knowledge of a language. But gradually, we forget the ultimate goal of learning language, programming and engineering are different, we may be programming in different ways to solve problems, perhaps because of the more ingenious or technical aspects of the method and their own partners to create contradictions, there is controversy. Such controversy is a good thing in the study process, multi-academic progress is helpful, but in the project is different, the project may be due to such a controversy and delay the construction, and finally may not have changed the project time has been lengthened. As a software engineering scholar, the requirement of language application is a good thing, but when we become an engineer, solve the problem, realize the project is the purpose, the use of language is only our tool, how to solve the problem faster and better is the problem we consider, and the language use of technical problems is no longer the key.

program = algorithm + structure, which is the fine meaning of programming, from the beginning of the development of the behavior it exists, like the foolish, he in the "mountain", he also used similar behavior to do programming practice, and so over the years, we also in the cycle and branch of the logic of the spin.

The emergence of "method" and "methodology" to push forward this logic, long-term programming practice, through the natural return and summary, so "process" appeared, so "object" appeared, so the related methodological methodology also appeared. The method is not created, it is a generation after generation of engineers in the process of implementing the project slowly accumulated. "Mode" is also a way of writing code in yesterday's programming.

The understanding of patterns requires programming experience, and the understanding of processes and objects also requires programming experience, and the source of experience is not in the next line of code you are going to write, but in the thought process of reviewing the previous line of code or the previous process.

Process, along with the project, will be broken down into different parts of the project, there is a link, there is a role, the same is the communication. In the process of implementation of the most important is the role and role of communication and links between the issues, so cooperation is the most necessary and necessary for the process of things.

Finally speaking of engineering, the most narrow project is to describe "what" and "do what", in fact, the project is the description of the target and the results of detection, as for the realization of the project objectives, is the "process" and "method" of the matter, and the rapid and effective implementation of the "process" and "method" is the most direct efficiency That's the language we're learning now.

The implementation of the project requires not only the technical staff, but also the project manager that any project needs, to co-ordinate such a project. That is to say, the implementation of the project needs to be organized, as the management to ensure that the project, in fact, is a complete team.

Therefore, the realization of the project, from the smallest use of tools, to the entire work of the team, from small to large, each has a use.

Reading the sixth chapter of "Boulevard to Jane"--from programming to engineering