Краток опис на предавањето: An incredible amount of effort is spent daily for maintaining and evolving huge amounts of legacy code that usually bears the unmistakable odour of a 'stinky' design. At the same time we hear more and more often about tools that claim to guide to us to the green pastures of software quality. These tools compute myriads of metrics and throw at us thousands of warnings. Managers are gazing ecstatically at complex dashboards full of complex and vividly coloured charts and trend lines. Sophisticated 'technical debt calculators' are converting, with great boldness, internal quality issues to scary financial figures. With such an impressive arsenal of methodologies, techniques, and tools, software projects should be under full control. Except they are not! Often, metrics leave us clueless on how to improve the quality of our software; even worse, following blindly the goal of fixing some metric values usually leads to a degradation of a system`s quality. In this talk, I invite you to take together a closer, critical look at some of the most prominent code quality tools. I will share some of the practical lessons learned through my 15+ years of experience on creating and using code analysis techniques and tools. I will also discuss the need to find new ways of correlating the various sources of information about a project, in order to move from raw data to insightful knowledge that can lead to real improvement actions. The presentation will abound in pragmatism, as I will try to share with you some of the insights that I got while helping teams to deal with code quality issues in large-scale software companies.