Many people don't like code, or write code. Maybe I feel that the write code is too boring, boring, or I may find that the code is really a simple thing (the masters think so), it is not worth hugging it, and even some people contain utilitarian ideas. I also have something wrong, I have to have, in order to cultivate a good sense of code, I don't want to find some of the benefits of some code. The first big thing for code: implement software products. Oh, it is really nonsense, but it is indeed the second advantage of the primary benefits: in the project plan phase, it can be used to estimate. Usually, it is estimated in accordance with the code line. For example, this seven-person team's previous history is an average of 100 lines of code per day. This project estimates that the total code behavior is 70,000, that is about three months to complete. A company I used to make foreigners assessed CMM2, and I looked at a project I have participated before, I can complete 400 lines every day! ! At that time, I said that "the company has this level, I see CMM2, I don't have to use CMM5", haha, write code is indeed a hard thing, especially for Chinese programmers. That gang scheduled bastard! The third bigity of the code: used for communication. There is no doubt that the code is the least in the language that does not produce. If your mouth is not good, you can say this: "I can't express it now. However, you see me to write a class .. It has such a method to accept the system variable we just talk. "Hey, I think anyone can listen to this expression, I can understand the idea of my companions. The fourth big benefit of the code: for design, through code implementation, it can be confirmed and modified. Based on a point of view, some pseudo code is directly constructed to complete the design, such code is definitely understood by all developers. Don't write troubled documents and fancy design graphics (of course, it must be supplemented later). In addition, the design of the design is sometimes necessary to verify the session with the code. I have a company a product. When I design it, I said: "Take the system when the system accepts the XML message issued by the participant. The XXX tool translates XML messages into Java objects, Java objects interacts in the system, if you need to respond to participants, then pass the object to the YYY tool (XXX tool, YYY tool is a famous open source software, but I Just starting to be familiar with the usage), YYY automatically converts the object into XML messages and sent to the participant. Oh, how easy it is designed. However, it is because this two tools found in later development are not like the legendary "magic", but the system is redesigned. The code developer sometimes complains to the design staff, in fact, this is to look at it in two, sometimes because the designer is not considered because of the ability, or if the cause of the designer is not considered. However, in some cases is a change in the project, and the design needs to be changed. The key to solving the problem is to negotiate together, complaining can only make the mood peace. A girl who has worked with the two little scorpions of myself has a good temper. I often call me when I realize the code. "Hey, this interface can't be implemented, because the objects come in less define a related field" I will say: "Vomit, I forgot to define, and add it right away."
