The sixth chapter of the Road to Jane

with the passage of time, our Java course is nearing the end, has begun to prepare for the Java preparation time, although the time is so urgent, but I still in a busy schedule to take out this time, to write the sixth chapter of the book.
The process is accompanied by engineering. The process solves the problem of the relationship between the roles in engineering. The problem in the process is the problem of role, communication and link. The process is how, the customer does not care, he will not because of your vision of the technology to describe, he wants only substantive procedures. Engineering, the implementation of the project needs to use tools, need to implement methods, there is a process of team collaboration, and ultimately achieve the object. The "complexity" of the project may require the participation of different areas of knowledge, while "large" requires more resources (human, technical and managerial). As a model of development behavior, "team" is the result of the gradual accumulation of software scale and complexity.
Projects and organizations are best separated, and the project manager pays attention to the details of the project while also focusing on human resources, project funding, and coordination of multiple projects. These are not directly related to the project itself, but rather the content of "organization". These are all trying to show that a project manager must have some or even most of the non-technical work. The project manager should set up plans, set goals, train staff, coordinate work, prepare resources, determine the progress of a certain part of the project, and often meet to summarize, motivate and even punish the staff, not blindly optimistic. If you can't do this, you're likely to make mistakes and lose the trust of your employees, and the next thing you'll be waiting for is to pack up and leave.
just as "pattern" is a method, and the pattern is the act of writing your code yesterday. You do not see the act of doing things, and you cannot understand the value of "patterns" as a method. So the gurus unanimous: patterns need some programming experience to understand. In the same way, understanding the process also requires programming experience, and understanding the object also requires programming experience, which may occur when you review your previous line of code written, or the previous experience of a project failure. Experience comes from review, understanding, and analysis, not the next line of code you're going to write.
Engineering, is the description of the target and the detection of results, the realization of the need for tools to help. The increasing scale of software is the root cause. However, a few years ago there was no need for engineering. Even if a person is willing to spend 20 years writing an arbitrarily large and complex operating system software company will not give him the opportunity. Complexity requires a role in different areas of knowledge, but it requires more manpower, technology and management. "Team" is the result of successive accumulation of software size and complexity. The increasing size of the team means that software is becoming more complex.
Many people think that the boss is the person who sends money to himself, this is actually wrong. The decision to make money is usually made by the team manager of the department, the manager of the discipline, and the finance manager. The boss solves the problem of "Operation" in the company. From the author's narrative, I understand that it is important for us to be clear about the reasons for our employment, the level of our work, and whether you or your boss has the authority to decide if a project should be approved or discontinued.
I still want to continue to learn Java this course, stepping on the sun, welcome hope, create a better future

The sixth chapter of the Road to Jane