Today I looked at the sixth chapter "from programming to engineering" in the main road to Jane. The article takes "the column and the word" the "to get its essence and forget its thick, in the inside and forget the outside, see what it sees, not what it sees, see what it sees, and leave it not to be seen." "For preface. In the first section, "Language is just a tool", the author tells about some of the programming languages he has been thinking about. He had also been interested in discussing the merits and demerits of the language, but now he is not, he is no longer focused on language, as he wrote in the first chapter: it is good to talk about the language all day, or the language is bad, even sad. Indeed, the quality of the program is not the language, but the algorithm. Section II
Say something, today looked at the road to Jane Sixth chapter "from programming to engineering."
The article takes "the column and the word" the "to get its essence and forget its thick, in the inside and forget the outside, see what it sees, not what it sees, see what it sees, and leave it not to be seen." "For preface. In the first section, "Language is just a tool", the author tells about some of the programming languages he has been thinking about. He had also been interested in discussing the merits and demerits of the language, but now he is not, he is no longer focused on language, as he wrote in the first chapter: it is good to talk about the language all day, or the language is bad, even sad. Indeed, the quality of the program is not the language, but the algorithm.
The second section also wrote "program", program = algorithm + structure, programming of the fine meaning of this, from the beginning of development behavior, it exists. There's nothing to say.
The third section says "method". The process of methodology and methodology, long-term programming practice, natural attribution and summarization, must be precipitated into some kind of (software development) method, so the "process" appeared, so the "object" appeared, so the relevant methodology appeared. method is not created by a person or an organization, it is the result of time. This is a good saying, a pattern or a routine, or more slowly become a method.
The fourth section is about "process", the process associated with the project, the process is to solve the problem of the relationship between the role of the project. That is to say, the process is part of the composition project. The previous chapter said "The process of failure is also a process", referring to the relationship between some processes and engineering.
Immediately after the fifth section, "Engineering", said: The most narrow project, is to describe "what to do" and "do what." said that in order to achieve the project goal is to use the tool, in the project is very large and complex, no team-aware software companies will be highly process, proficient in methodology theory, with a large number of tools in the face of the army will be Aurra.
Of course, a project engineering needs to be organized to be well organized. The sixth section is about the organization, and the article mentions that engineering theory actually contains histology. So the project manager's work is also very demanding.
Anyway, there is a lot of preparation before doing a project, at least using a programming language to program, we should have organized to do in order to make the project more perfect.
The sixth chapter of the Road to Jane