Extreme ProgrammingExtreme Programming (XP) Ultimate Programming Perhaps this translation is not accurate, we still use XP bar, XP's procedure and our usual understanding of the software engineering to advocate it is absolutely different. It advocates first write code, code first, what design, what document, let's talk about it, it's important to see the code than anything (this is like some people's ideas, but we think this is not take). Beck put forward this kind of thinking and wrote a book for this thought. It emphasized in the book to write the code, you must first write a small test program so you have a grasp of the system, and then expand The system is modified. It advocates relative concepts, which is to let a pair of programmers write code and take each other. We very supported him at this point. Two people have some new discovery when communicating. Its statement is totally different from traditional software engineering ideas, and traditional software projects believe that it is successful, then concentrates on programming this best. Beck's basic idea is to start with a simple model, then add something, then let this thing close to the design goal until success. In this way, the work of all members in the group will not be divided, and all people have to analyze, program, test, and develop together. It has been said above, because there is a paired programmer to develop, there is a lot of communication, so there is no need to do something on what paper. This is just a way, beginners don't think this is good. Basic, mature, and everyone is recognized as a good way is still a traditional software engineering method. It is not a new best in the computer this discipline. Because we are here to advise beginners, from the most basic beginning, don't think that the new theory is always the best. The new theory is not tested, so it is also the most unsafe.
