The purpose of software development is to develop software products with applicability, validity, modification, reliability, understanding, maintainability, reusability, portability, traceability, interoperability, and satisfying the user's requirements under the stipulated cost and time.
And for the whole development process, the development (coding) process is the core outcome of the entire software product process, the code of good or bad in addition to the implementation of the function will have an impact on other such as modifiable, reliability, understandable, maintainability, maintainability, reusability, portability, traceability, etc., so "OK" The code is very important for the software.
How to write a "good" code is the subject of this series of articles, with the example of. Net core code, which describes some of the aspects involved in code management and the corresponding support tools.
This series of articles describes how to write a "good" code from the following 4 aspects:
- Code management tools and selection of the development process
- Good code is out of the pipeline-using Git to manage the source code
- Good code is tube out of--git branch workflow with pull Request (update ing)
- Code specification and application of tools
- Unit Test & Code Coverage
- Continue Integration & Continue deliver
Note: This series of articles for reference only, in the actual development of the factors that affect code management, so in practice, according to the actual situation to adjust. Welcome to the discussion if you have any questions.
Good code is out of the box--talking about the code management method of. Net core and landing (update ... )