What are the goals of the refactoring code? Is it only to increase the code structure? Is there a way to make a change in the future?
understandable
Purity
Inspection by code is easy to identify, which is easy to understand. Extremely complex, poorly structured, Ruby Goldberg style code is more difficult to inspect the defects. In addition, it is very easy to put under compilation and component coupling between components, well under compound code testing. In addition, under testing small, well-formed bits overlap less in code coverage between test cases, for faster and more reliable tests (which runs a self-sustained cycle for better and better tests) makes. Also, the more direct code can be more predictable and reliable.
Ease of maintenance and development
Well, high quality, easy to understand, easy to understand, easy to use, easy to use and maintain, It is easy to make changes now because they have small effects and it is more clear to make appropriate changes.
Refactoring code is the quality and quality of accuracy as per quality quality, but where refactoring pays the most, it is in the maintenance and development of software design. Often, a good strategy when adding new features to old, poorly-wanted code, the target code is to be refactored, then adds new features. It will often take less development efforts than trying to add new features without refactoring and an easy way to improve the quality of the code base "Piece in the sky" can not make much mistake, the conceptual advantage of refactoring / redesign work that It is difficult to justify the management.
Comments
Post a Comment