The document discusses code quality and technical debt. It defines technical debt as debt that accumulates when code quality is not maintained. Poor code quality can slow down development over time, like how debt needs to be paid back. The presenter then demonstrates SonarQube, a tool that measures code quality over seven axes (design, duplications, documentation, complexity, unit tests, coding rules, potential bugs) and tracks technical debt. It allows seeing how quality and debt evolve historically and comparing components. The key messages are that technical debt should be managed on an ongoing basis like cleaning a kitchen daily, and that all developers should be engaged in quality control from the start.

1. Patroklos Papapetrou @ppapapetrou76
Holding down your
technical debt with
#itakeunconf #SonarQube

2. Agenda
● Code Quality in a nutshell
● The seven axes of quality
● Technical Debt
● SonarQube Demo Time

3. private String _ugly_name;
private String ANOTHER_$UGLY___NAME;
private static String am_i_static;
public void please_work(ArrayList objects){
for (Object object : objects){
if (object == null){
String toString = object.toString();
} else
am_i_static = object.toString();
doSomething(object);
}
}
private void doSomething(Object object) throws
NullPointerException {
throw new
NullPointerException(object.toString());
}

4. What is code quality?

5. private String _ugly_name;
private String ANOTHER_$UGLY___NAME;
private static String am_i_static;
public void please_work(ArrayList objects){
for (Object object : objects){
if (object == null){
String toString = object.toString();
} else
am_i_static = object.toString();
doSomething(object);
}
}
private void doSomething(Object object) throws
NullPointerException {
throw new
NullPointerException(object.toString());
}

6. What is code quality?
“It’s an indicator about how quickly
developers can add business value to a
software system”

7. Why measure?
Source code is the heart of every system

8. Why measure?
Developers don't write “new” software. They
maintain “legacy” systems.

9. The broken window theory

10. What we should measure;
● Abstract numbers? (Almost) useless
● Evolution through time? Definitely!
● Metrics? Yes but which ones?
● Welcome to the seven axes of quality

11. The seven axes of quality

13. The seven axes of quality
Design
Duplications
Documentation
Com
plexityUnitTests
Coding rules
PotentialBug
Technical Debt

14. Technical Debt
“If the debt grows large enough, eventually the company will
spend more on servicing its debt than it invests in increasing
the value of its other assets”
Steve McConnell
(Author of code complete)

15. Technical Debt – My take
“Technical debt for software systems what salt is for
cooking. You need it, you can't see it but if you don't control
it it's too late”
Patroklos Papapetrou
(Yet another software gardener)

16. This is how the source
code looks like when we
don't pay off technical debt

18. SonarQube star Features
Dashboards

19. SonarQube star Features
Historical Data

20. SonarQube star Features
Differential Views

21. SonarQube star Features
Components drilldown views

22. SonarQube star Features
Quality Gates

23. DEMO TIME

24. The big picture
Track and reduce Technical Debt on an
ongoing basis. (Clean up kitchen every day)

25. The big picture
Engage all devs from day #1
(Not only mums wash the dishes )

26. I have a dream…
...that one day code
quality management
will be as much as
important and
essential is today
source code
management

27. Thank you
ppapapetrou76
@ppapapetrou76
http://www.linkedin.com/in/ppapapetrou
1