We started using SonarQube as part of our development workflow after realizing that it would be much more than a security gateway in our process, and we quickly discovered its potential to improve code quality, prioritize efforts together with the project manager, create onboarding tickets for new joiners, and align best practices across teams. However, we initially made mistakes by not understanding how SonarQube is meant to be used, installing it without sufficient knowledge, and only seeing it as a tool that provides statistics about our code rather than embracing the Clean Code approach. We learned from these mistakes and established strong technical foundations, created alignment on our Clean Code strategy with project stakeholders, defined and enforced a quality profile with a set of rules that made sense for us, and empowered developers to own the quality of their code.