The previous chapter "Coded Tour - Preliminary Articles" tells the importance of the process, in which the coding process is composed of the encoding process, it should be organized in order.
The encoding process is not a constant, it is like a chain, which can be inserted into one new chain in any one of the iron chain, and can also pull out the link no longer needed. So a process is based on the needs of each group. Even so, we can list some basic links here for reference.
Guidelines, follows Guidelines to standardize design, while also avoiding some unnecessary hidden dangers, so it is recommended that each programmer first knows the official or organizational of each platform or organizes its own guidiness. Naturally, programmers who have just started to touch a guidelines clearly clear the standards specified in all Guidelines in the short term, which requires some kind of tool to constrain a guidelines implementation and execution. UML diagram, in other words, there is a design, let the programmer know what you will do before starting the encoding, if you find it wrong, at this time, you can correct it, even if you give up all the design, you can find a problem later than starting coding. Restart more (various resources). The specific design varies from person to person, and it does not discuss how to design. After designing Guidelines, you can start preparing a unit test code, simple unit testing is necessary, otherwise the code writes from the programmer has no quality assurance. After the unit test code is written, you can prepare the integrated test code, which will guarantee the perfect combination of the system, so write these test code more to spend more. Finally, I coded because the implementation of the first few steps, the current coding should be too long. ^ _ ^ Should now pay attention to, write a good document, the document here refers to the document written for the code, not the document written by the user. To mark each class, method, parameters, return data, etc., the information, etc., the information, etc. of the data, etc., these materials have an important role in the maintenance of future code together with the design data. The reconstruction of the code, this step is from maintenance perspective, and it is important, refactoring can make the structure of the code more clear, and sometimes it can also improve the efficiency of the code. Refactoring is actually a way to optimize code optimization.
As mentioned earlier, the above is just some of the basic streams that can be used in the encoding process, and programmers can insert other processes based on the needs of the organization.
Next, we will actually combine some tools to help us do the above processes. Common, We are almost here.
