How can I effectively track improvements in code quality?

There are several tools like SonarQube and Aikido that can help monitor code quality. They provide insights over time, making it easier to see how your efforts are making a difference.

Think about how your efforts align with your key performance indicators. A few focused weeks of work can significantly reduce linter issues. It's crucial to understand what those metrics really tell you about your progress and how they affect what you deliver to customers.

You might want to check out SonarQube. It's a great tool for tracking code quality over time, and it can help you see the improvements you've made as you tackle your technical debt.

While metrics can be useful, chasing them might not lead to the best outcomes. If you're able to add new features and fix issues quickly without having to do massive refactoring, you might not truly have any technical debt. Focus on tangible results over numbers.

You can try CodeAnt AI. It tracks quality and security metrics over time, and it provides simple graphs that clearly show your progress. We use it to show management our improvements—like a 40% drop in critical issues this quarter—which really helps justify our refactor sprints.

Have you considered asking your developers directly? They can often provide insights into whether they feel the code quality is improving based on their experiences.