The sixth chapter of the Road to Jane

The author first speaks of programming in the language of understanding, the author in the first chapter, said, all day to discuss the language good, or the language of bad people, and even sad, for a programmer, or a programmer to think of people, the first step to see the software programming, is a "language is just a tool."

In this diagram, the author illustrates the relationship between code, method, process, and organization, which is the original definition of programming in the inner ring, and is the most primitive state, and any work related to the code will eventually fall back to such a rule. What drives this logic forward is the emergence of "methods" and "methodologies". Long-term programming practice, natural attribution and summary, must be precipitated into a certain (software development) method, so the "process" appeared, "the object" appeared, so the relevant methodology has appeared. This is the result of practice, the method is not created by a person or an organization, is the results of the accumulation of practice. It is only from the practice that we can sum up experiences and methods, experience comes from review, understanding and analysis, not the next line of code that you will write.

In the process of half-life engineering, the process solves the problem of the relationship between the characters in the project.

The process is about how many people are organized together for development. He first eight works in the link decomposition, so that there is a link, there is a role, have a role, there is communication. Therefore, the problem in the process is the role, communication and link problems. The link is important depending on the specific programming behavior, that is, the specific project, for the product, more important is the quality and technical barriers, but in such a model to do the project, the customer will only see them because of the project's repeated delay two and angry. As a project manager, it's scary because he can't tell the difference.

The narrowest project is to describe "what to do" and "what to do". In other words, it is the description of the target and the detection of the result. As for the realization of this project goal, it is the "process" and "method", and the effective and rapid realization of "process" and "method" is required, is "tool". The process is accompanied by engineering, which solves the problem of "unison" collaboration in engineering. The root cause of the project is the increasing size of software, as well as the "complexity" of the project, requiring different areas of knowledge to participate in the role of a person is difficult to do, demanding more resources. As a model of development behavior, "team" is the result of the gradual accumulation of software scale and complexity. The team is bound to grow bigger and larger, because the size of the software will become more complex. A software company without team consciousness will be aurra in a highly process, methodology-savvy army with a large number of tools. Engineering theory actually contains histology, as can be seen in the above picture, Mr. Greatlypraised the organization and works separated, and in this drew a longitudinal line. If, as a project manager, you must have a part of the work of a non-technical, you must pay more attention to the organization and plan of the project, standing in the "organizer" view of the problem.

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.

The sixth chapter of the Road to Jane