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:
- The code is not formatted properly.
- The code is not functionally broken into appropriate projects/packages/classes.
- Ambiguous application layering.
- The code is not properly commented. (Class level and method level comments are essential)
- 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.)
- Duplicate classes in different projects where one is old and unused but still resides in your source code.
- 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.)
- Constructors/methods having long list of parameters. (I believe maximum number of…
View original post 390 mots de plus