Sonar
1 like2,477 views
This document discusses continuous inspection and fighting the seven deadly sins of developers. It introduces Olivier Gaudin and describes how industrialization has led to software factories and continuous integration. The rest of the document discusses the mission of today's developers as doing software right and for others, with methodology, transparency, and code quality. It defines the seven deadly sins of developers as duplicated code, complexity, design issues, lack of tests, coding standards, bugs, and comments. Sonar is introduced as a tool to measure internal quality and technical debt.
Sonar
- 1. BNP Paribas Continuous Inspection Fight back the 7 deadly sins of the developer! Olivier Gaudin olivier.gaudin@sonarsource.com @gaudol
- 2. Back in old times
- 3. The genius
- 4. The super hero Au fin fond de l'Univers, à des années et des années-lumière de la Terre, Veille celui que le gouvernement intersidéral appelle quand il n'est plus Capable de trouver une solution à ses problèmes, quand il ne reste plus Aucun espoir : le Capitaine FLAM !
- 5. This is my toy
- 7. Industrialisation has entered the game... ● Project under version control ● Project under continuous integration ● Technical and functional traceability
- 8. …and software factories evolved Makefile Issue Tracker IDE Continuous Refactoring Inspection VI / SCM Continuous Unit Tests Emacs Integration
- 9. What is the mission of today's developer ? ?
- 10. The end does not justify the means Doing the right software Doing the software right
- 12. Methodology
- 13. Transparency
- 14. Nothing is more important than code But source code is nothing alone
- 15. (Almost) Everything is maintenance ! Creation of an application Maintenance of an application
- 16. Internal quality « A well-written program is a program where the cost of implementing a feature is constant throughout the program's lifetime. » Itay Maman
- 17. How to measure internal quality ?
- 19. The 7 deadly sins of the developer Sins Technical Debt
- 20. The 7 deadly sins Applied to source code ● Duplicated code ● Bad distribution of complexity ● Spaghetti Design ● Lack of unit tests ● Lack coding standards ● Potential bugs ● Not enough or too many comments
- 22. Sonar is only a tool ! ● What should happen in case new defects are added ? ● How, when and who should make quality standards evolve ? ● How to train new joiners ? ● Any measure reported must be analysed
- 23. The « Done, Done, Done, Done » ● Developed ● Tested ● Approved by the « Product Owner » ● Technical debt under control