The process of failure is also a process

Do the process is not to do engineering, the process is to do a project process, and the project is the result, customers see a software is not good or bad to see you do a lot of times very hard to feel your products, they want only results, not pay attention to your process. The hardships of the process only self-understanding, other people pay attention to only the results, a thing do not personally realize never know how difficult it is, everyone, every industry, every position is not his surface seems so easy, everyone has the difficulty of everyone. Success of the flowers, you only see her current bright, but its bud, soaked in the sad tears spring, spilled the blood of the sacrifice of the rain.

Go through the Motions: program, do the project can not just go through the motions, you on the computer perfunctory he will be perfunctory to you, the final written program can not run, or the results can not satisfy customers, the ultimate trouble is their own.

The realization is the goal, the programming is a huge project, the other person sees only the result, for does not know the programming person they also can only understand the result, the process hardship is not our ostentatious capital. Although the process is more important to yourself than the outcome, the majority of people are more concerned with the results. and the best result for programming is to be able to meet the user's requirements well, and it is our ultimate goal. The process is hard, but the final result is not a qualified programmer, this will certainly be eliminated by the company. The purpose of programming is to achieve, so that the computer can follow our ideas to achieve our expectations.

Engineering is just a way of realizing that by doing engineering it tells the computer how they should do it. The final result cannot be that we have finished the project (every process), but have not completed the project (every "achievement goal"). Engineering is just a way, not all of the goals must be done with engineering, no matter what method, the way to achieve the goal is a good way. The customer and the project manager will only focus on the results and not the process of your work.

Process is not a dead model, to learn to adapt, to write a program, you can refer to the predecessors have written similar source code, but is not sure to follow their pattern to write, their method is not necessarily the best. To achieve a purpose is not only one way, the process is not a dead model, methods are people think out, the idea of predecessors is not always correct, or is always the best, to learn to doubt, in the predecessors of the model to add their own ideas.

"Cerio" and "Kahurido", learn the experience of predecessors and programming ideas should pay attention to learning their essence of things, take its essence discard its dross. Learning their bones, or thinking, is not just a shelf, but a form of programming. The more simple things closer to nature, the road to Jane, the same.

Project is not done, is organized, the success of a project is not by a person to complete. A vast project requires people from the team to work together. Everyone in the team is responsible for each part of the project, and after each part is completed, they need to be assembled to form a complete project.

The process of failure is also a process