Aaron Bedra of Relevance came down and spoke about static code analysis and the benefits it can have on the quality of your codebase. He talks about the differences and benefits of RCov, Flog, Flay, Roodi, and Reek.

1. Metrics Magic
Aaron Bedra
Principal, Relevance, Inc.
Charlotte Ruby

4. Code quality

5. Code coverage

6. Code complexity

7. Code duplication

8. Why do I care?

9. Maintainability

10. Testability

11. Refactoring

12. Sanity

14. reek

15. gem install reek

16. reek [options] [files]

17. reek finds code
smells

18. roodi

19. gem install roodi

20. roodi [pattern]

21. Roodi finds code/
design smells

22. Flog

23. Flog scores your
code

24. The higher the
score, the “worse”
your code is

25. gem install flog

26. flog [pattern]

27. Flay

28. gem install flay

29. flay [pattern]

30. Why do I need 4
quality tools?

31. There’s no substitute
for peer review

32. RCov

33. gem install rcov

34. DEMO

35. Cool, so what do I
do with all this ?

36. Continuous
Integration

37. You can make these
tools fail the build!

38. But wait! There’s
more!

39. metric-fu

40. metric-fu includes
• flog
• flay
• reek
• rcov
• saikuro
• and a few more

41. And wraps them in a
nice pretty picture

43. There are lots of
options

44. Use what works for
you

45. But don’t ignore the
metrics!

46. Contact
• aaronbedra.com (blog)
• abedra (twitter)
• aaron@thinkrelevance.com
• github.com/abedra

47. Questions?