Prioritizing Technical Debt with Hotspots
Technical debt and code quality issues cost time, money, and missed deadlines. That’s why it’s vital to know when you can safely move ahead and implement new features as well as when you might have to take a step back and improve what’s already there. It’s a hard balance. A hotspot analysis helps you stay on top of it and communicate when to tip that scale. This tutorial explains how to interpret the hotspot analysis in CodeScene.
More in Tutorials
Setting up the Pull Request Integration for Context-Aware Quality GatesAutomating Project Creation for Frictionless Team OnboardingHow to customize Code Health rules with .codescene/code-health-rules.jsonIdentify, Visualize, and Manage Technical DebtStill need help? Ask the team