Top technical mistakes of programers

17 June, 2011

Please share your own thoughts or experiences with others as a comment, because we all must learn from our mistakes.
  1. Code merely for money
    If you do not enjoy programing, your code is bound to be scrappy.
    This result in not only your career, but your team members life too into misery.
  2. Not having basic competencies
    Those who are not sound in programing concepts like abstraction, polymorphism, use of interfaces, best practices in exception handling etc. bound to write code that is poor in design, highly unreadable and not maintainable.
  3. Try to be too smart
    Some developers try to be too smart by writing complex statements combining too many steps. This result in poor readable code that no one like to change.
  4. Try to show off newly acquired skills
    When you learn something new, its natural tendency that you like to use that knowledge immediately .
    But be patient. Use it only when it is really relevant.
  5. Too many objectives
    A program with too many goals for performance, memory use, robustness, and reliability
    will take longer to develop and result in over complicated code.
  6. No refactoring / restructuring
    Software is evolving product. When the code base grow, the individual classes, methods, etc. get complicated.
    Some lazy programmers do not restructure the code resulting overly complex code.
  7. Vicious complexity
    Some developers deliberately make their code unduly complex in order to mark their territory.
    They do that to make the company dependent on him, as part of plan for his job security.
  8. Top technical mistakes of programmers
    “There are two ways of constructing a software design.  One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.” - C.A.R. Hoare

Bookmark and Share Related Posts with Thumbnails



අද දෙරණ