Developer Network> Development Tools> Java> Text
Why is it necessary to reconstruct the "Reconstruction-Improved Design of Martin Fowler" One of the best-selling computer books for two consecutive years, you can know the extent to which the rejuvenation to the programmer . So what is the reconstruction? Reconstruction is based on the existing function of the software, improves software quality, performance, making its program's design mode and architecture more reasonable, improve software scalability and maintenance. Maybe someone will ask, why not spend more time when the project starts, but take time to refactively in the future? To know a perfect design, you can predict that any changes in the future, or a flexible design does not exist. The system designer is often only controlled from the big direction, but cannot know that each sub-branch season will never change, and users who make demand often have to start "product head argument" after the software is formed. After all, the system designer is not the first fairy, and the changes in function have resulted in the adjustment of the design. Therefore, "Test is the first, continuous reconstruction" as a good development habit, is increasingly adopted, tested and refactored to the Yellow River, and become a magic weapon to ensure software quality. By reconstructing the following goals: • Continuously biasing and improved software design reconstruction and design are complementary, it is complementary to each other. With a refactor, you still have to do pre-design, but don't have to be the best design, just a reasonable solution is enough. If you don't have a refactor, the programming will gradually corrupt the deterioration, and it is more like a line. Kite, uncontrolled wild horse. Reconstructing is actually the finishing code, let all code with divergent tendencies return to this border. · Make the code easier to understand that Martin Flower has a classic words in "Reconstruction": "Any fool can write a computer that the computer can understand, only the procedure written by human is easy to understand is an excellent programmer." In this regard, the author feels deep, some programmers can always write the running code, but the names in the code have dizzy to grasp the seat armrests, trying to pick up such code to pick up such a code. Will you want to escape? The software life cycle often requires multiple appraisers to maintain, and we tend to ignore these later people. In order to make the code are easily understood by others, you need to do many additional events when implementing software functions, such as clear typography layouts, concise annotations, which are also an important aspect. A good approach is to use metaphor named, namely the function of the functionality, named visualization or manicing techniques, a good attitude is to name each code element like a newborn, maybe the author is a bit Name parallelism, if you can Rong Xiang Ya, will be deeply available. Full-text reading: Reconstructing Reconstruction Reconstruction with JBuilder 2005
