Tue May 10 15:07:56 GMT 2016

development

How to produce damn good software - http://www.manageability.org/blog/stuff/how-to-build-damn-good-sw

Recommendation of managing bugs - http://www.onlamp.com/lpt/a/6096 http://www.onlamp.com/lpt/a/6097

Collecion of link about software engineering - http://codebalance.blogspot.com[..]01/selection-of-successful-software.html

The Big Ball of Mud and Other Architectural Disasters - http://www.codinghorror.com/blog/archives/001003.html

1. – Have a clear development process.
2. – Understand the vision and goals of the project.
3. – Use iterations.
4. – Transparency.
5. – Commitment.
6. – Leadership
7. – Customer focus.

http://www.makinggoodsoftware.com[..]echnical-tips-to-deliver-great-software/

If it aint broke, don't fix it; vs continue improvement - http://agile.dzone.com/news/if-it-aint-broke-dont-fix-it , one good question asked is, what mean broken? Bug? or Quality? What is Quality?

The Mythical Man-Month Revisited - http://onlamp.com/lpt/a/4900

Story from QuickBooks - http://www.drdobbs.com[..]rticleId=240003694&siteSectionName=tools

How long did the source code live? - http://blog.activelylazy.co.uk[..].uk/2016/02/24/longevity-of-source-code/

http://kukuruku.co[..]arn-from-real-examples-how-to-avoid-bugs


(google search) (amazon search)
1 2 3 second