|Ⅰ||This article along with all titles and tags are the original content of AppNee. All rights reserved. To repost or reproduce, you must add an explicit footnote along with the URL to this article!|
|Ⅱ||Any manual or automated whole-website collecting/crawling behaviors are strictly prohibited.|
|Ⅲ||Any resources shared on AppNee are limited to personal study and research only, any form of commercial behaviors are strictly prohibited. Otherwise, you may receive a variety of copyright complaints and have to deal with them by yourself.|
|Ⅳ||Before using (especially downloading) any resources shared by AppNee, please first go to read our F.A.Q. page more or less. Otherwise, please bear all the consequences by yourself.|
|This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.|
The quality of software, not only depends on its architecture and project management, but also is closely related with the code’s quality. Bad, untidy code can run normally to some extent, but that will bring potential obstacles to the whole development team, as sure as a gun. As a result, that will greatly increase development time, resources and other costs. This same applies to both agile software development and traditional software development.
Continue reading Clean Code: A Handbook of Agile Software Craftsmanship HD PDF