This article comes from Totango 's co-founder and CEO Guy • Neil Paz (Guy Nirpaz), he shows the differences between good and bad developers (or needed effort) developers in this article.
If you think the use of "good" and "bad" to distinguish developer wrong, then these can also be seen as the difference between the primary developers and senior developers. But in any case, to see more of the other excellent developer (or senior developer) is how to do, to upgrade their skills, work of great help.
The article reads as follows:
Excellent developer is an artist, a craftsman enjoy the creative process. Bad developer code only as agriculture is responsible for generating the code yourself.
Good developers to understand the customer's problem. Bad developers only understand the technical issues at hand. Good developers will continue to try to understand "why", and then to implement, while being able to grasp the overall situation. Bad developers to focus on building classes, methods, and configuration files, without regard to the overall situation.
Good developers understand the complete architecture of the product. Bad component developer only know he wrote. Good developers fully understand the technology used in the product, understand their purpose and how they work internally.
Good developers who are not afraid of new technology, and the ability to grasp quickly. Bad developer insists he only currently available technology, for any technological change negative attitude.
Excellent developers to improve their skills through continuous learning, they often read technical articles and books. Bad developers do not have time to learn, they are always too busy, so that can not do other things.
Good developers who care about the quality of products, but also very concerned about the quality of the process, they strive to create defect-free code. Bad developers will be left to QA bug to discover, and then repaired.
Good developers who can create value for customers to develop features, bad developers who just want to complete the task. Outstanding developers do not claim that demand is not a complete description of, and to ensure full understanding of these characteristics. Bad developers will wait until the demand for complete details before starting work. Good developers are always ensure that relevant information with product features, once the information is lost, he would try again to get it.
Good developers who are not afraid to join someone else's code in the product, and bad developers worry about someone else use his code. Good developers who think we should not spend too much time writing speaks for itself (self-explanatory) and visible (well-documented) code. Bad developers always need to allocate additional time to record and simplify the code.
Good developers who will never feel that their code has been good enough, the opposite will continually organize and repair. They committed to creating elegant solutions, that his job is to provide value to customers. Bad developers only consider their own code is elegant, the value-creating work to others.
Reproduced in: https: //www.cnblogs.com/MichaelShang/archive/2012/06/29/2570141.html