10 characteristics of a bad developer

We meet them all the time, but we hope that we won't have to deal with them on our next project. Sadly there are many developers that fall under this category. Are you one?

I think it is important to distinguish between a bad programmer and a bad developer. Being a programmer, delivering code is one part of our job. But being a developer, making the project happen, is much more than just delivering code; it is working in a team, sharing knowledge, and most important, helping the customer get the product they need.

I have met great programmers, which are poor developers, and vice versa. However, the two are often related, and then you basically just have a bad resource.

In my opinion, being a bad developer is a lot more expensive for a project than being a bad developer.

Here is my list of top 10 characteristics of a bad developer:

1. Has a big ego and is more interested in his/her own success than the success of the team/the project.
   
2. Does not want to share knowledge of technology or domain.
   
3. Protects his/her own code at all costs, that is, does not let others criticize the code.
   
4. "Never does anything wrong".
   
5. The best defense is an offence. Attacks others before they can attack them.
   
6. Writes code in their own style, they are above any standards set by the project.
   
7. Only accountable when it suits them.
   
8. Often leaves others to solve their problem.
   
9. Talk about other team members behind their backs.
   
10. Usually delivers poor quality work, but not because they cannot do better, they just don't care to.