Excellent developers vs poor developers

Wangguo iteye I want to comment on (0) font size: T |
T

This article is from guy nirpaz, co-founder and CEO of totango. In this article, he lists outstanding developers and poor (or hard-working) differences between developers.

AD:

This article is from guy nirpaz, co-founder and CEO of totango ),This article lists the differences between excellent developers and poor (or hard-working) developers.

If you think that "excellent" and "poor" are used to distinguish between developers, you can also regard these as the differences between junior developers and senior developers.However, no matter how you do it, let's take a look at how other excellent developers (or senior developers) Do it, which is of great help to improve their skills and work methods.

The content of this article is as follows:

An excellent developer is an artist who enjoys the creation process. Poor developers only treat themselves as code farmers responsible for generating code.

Excellent developers understand customer issues. Poor developers only understand the technical issues at hand. Excellent developers constantly strive to understand "why", implement it, and grasp the overall situation. Poor developers focus on building classes, methods, and configuration files, regardless of the overall situation.

Excellent developers understand the complete architecture of the product. Poor developers only know the components they write. Excellent developers fully understand the technologies used in products, their usage, and how they work internally.

Good developers are not afraid of new technologies and can quickly master them. Poor developers only stick to the technologies they currently have, and have a negative attitude towards any technological changes.

Excellent developers learn to improve their skills. They often read technical articles and books. Poor developers do not have time to learn. They are always too busy to do other things.

Excellent developers care about product quality and process quality. They strive to create defect-free code. Poor developers leave bugs to QA for discovery and repair.

Excellent developers develop functions that can create value for customers. Poor developers only want to complete the task. Excellent developers do not claim that the requirement description is incomplete and make sure they fully understand these features. Developers with poor requirements will not start to work until the requirement details are complete. Excellent developers always ensure that they have information related to product functions. Once the information is lost, they will find a way to get it.

A good developer is not afraid to add other people's code to the product, while a poor developer is worried that others will use his code. Good developers do not think they should spend too much time writing self-explanatory and well-known ented code. Developers with poor performance always need to allocate additional time to record and simplify code.

Excellent developers will never feel that their code is good enough. On the contrary, they will continue to organize and fix the code. They are always committed to creating elegant solutions and believe that their job is to provide value to customers. Poor developers only consider whether their code is elegant and leave the work of creating value to others.

Original English: good developer, bad developer

This article from: http://www.iteye.com/news/25311