Code quality is an abstract concept that fails to get traction at the business level. Consequently, software companies keep trading code quality for new features. The resulting technical debt is estimated to waste up to 42% of developers' time, causing stress and uncertainty, as well as making our job less enjoyable than it should be. Without clear and quantifiable benefits, it's hard to build a business case for code quality. In this talk, Adam takes on the challenge by tuning the code analysis microscope towards a business outcome. We do that by combining novel code quality metrics with analyses of how the engineering organization works with the code. We then take those metrics a step further by connecting them to values like time-to-market, customer satisfaction, and road-map risks. This makes it possible to a) prioritize the parts of your system that benefit the most from improvements, b) communicate quality trade-offs in terms of actual costs, and c) identify high-risk parts of the application so that we can focus our efforts on the areas that need them the most. All recommendations are supported by data and brand new real-world research. This is a perspective on software development that will change how you view code. Promise. "Code quality is an abstract concept that fails to get traction at the business level. Consequently, software companies keep trading code quality for new features. The resulting technical debt is estimated to waste up to 42% of developers' time, causing stress and uncertainty, as well as making our job less enjoyable than it should be. Without clear and quantifiable benefits, it's hard to build a business case for code quality. In this talk, Adam takes on the challenge by tuning the code analysis microscope towards a business outcome. We do that by combining novel code quality metrics with analyses of how the engineering organization works with the code. We then take those metrics a step further by connecting them to values like time-to-market, customer satisfaction, and road-map risks. This makes it possible to a) prioritize the parts of your system that benefit the most from improvements, b) communicate quality trade-offs in terms of actual costs, and c) identify high-risk parts of the application so that we can focus our efforts on the areas that need them the most. All recommendations are supported by data and brand new real-world research. This is a perspective on software development that will change how you view code. Promise.        First of all, the attendees will get a vocabulary to communicate around code quality with both engineering and non-technical stakeholders. Second, I'll show how to apply this information in the work of an architect to ensure our systems remain maintainable. [color=#111111][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][size=2][font=Verdana, Arial, Helvetica, sans-serif][h2][/font][/size][/font][/size][/color][/font][/size][/color][/color][b][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][url=https://drive.google.com/file/d/1e1m1Z76RWk7kE35wFVXoErF1GvABmj7p/view?usp=sharing]Slides[/url][/font][/size][/color][/font][/size][/color][/font][/size][/color][/b][color=#111111][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][size=2][font=Verdana, Arial, Helvetica, sans-serif][/h2][/font][/size][/font][/size][/color][/font][/size][/color][/color]