Seven Sins of program development-the 7 deadly sins of Software Development

Http://www.infoworld.com/d/developer-world/the-7-deadly-sins-software-development-872? Page = 0, 1

 

Lust (overengineering)

-Do not over-design

-
Shipping is a feature
. A really important feature. Your product must have it.

 

Glutony (failing to refactor
)

-Continuous refactoring code

-Clients may see only the new features in each release, but over the long term, they'll thank you for keeping off the fat.

 

Greed (competing internal SS teams)

-Avoid repeated Development

-Share and share alike shocould be your mour

 

Sloth (not validating inputs)

-Interface/service input verification

-Remember, a web form that uses JavaScript to validate its inputs can be
Easily sidestepped by Disabling JavaScript in the browser or not using
Browser to access it at all.

-This... is a problem, but it is regarded as the seven sins, isn't it a bit?

 

Wrath (not commenting code)

-Code is its own best documentation of what itDoes
; Comments shoshould be there to explainWhy

-The readability of the Code does not solve the logic complexity of the business.

 

Envy (not using Version Control)

-Continuous version control,

-Not necessarily the code. Why is version control unavailable for programming manuals, technical documents, project suggestions, and personnel arrangements?

 

Pride (not unit testing)

-Continuous unit test

-Test first

-Computational Science:... erro
R, unknown irrelevant

 

Summary after reading:

Problem tracking, Pair programming, unit testing, refactoring code, Version Control