Dirty code

A Software Architect's blog

Imagine the plight of a maintenance developer working on dirty code. I call the code which is not clean as dirty and it has any of the following characteristics:

  1. The code is not formatted properly.
  2. The code is not functionally broken into appropriate projects/packages/classes.
  3. Ambiguous application layering.
  4. The code is not properly commented. (Class level and method level comments are essential)
  5. Classes or methods having huge chunks of old code that is commented. (In today’s age of code repositories, I don’t understand the need to maintain old code in comments.)
  6. Duplicate classes in different projects where one is old and unused but still resides in your source code.
  7. More than one class with same name in different packages. (Java allows defining classes with same name in different packages. I agree but production code seldom uses same class names.)
  8. Constructors/methods having long list of parameters. (I believe maximum number of…

View original post 390 mots de plus

Publicités

Laisser un commentaire

Choisissez une méthode de connexion pour poster votre commentaire:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s