---
title: "Technical Debt"
description: "1 posts about Technical Debt, summarised, each linking to the original."
---

# Technical Debt
> 1 posts about Technical Debt, summarised, each linking to the original.

## Articles

### [Code Quality Q&A With the JetBrains Qodana Team](https://yomu.fyi/post/code-quality-q-a-with-the-jetbrains-qodana-team.md)
- Company: [Jetbrains](https://yomu.fyi/company/jetbrains.md)
- Author: Kerry Beetge
- Published: Sep 22, 2026
- Type: Explainer

The Qodana team answers frequently searched questions about code quality, distinguishing technical debt from poor code quality and offering practices to reduce cognitive complexity in nested loops. They explain that code coverage measures how much production code is executed by unit tests, while mutation testing evaluates test quality by checking whether tests detect deliberate code changes. Unit tests provide the fastest feedback on code changes by catching regressions close to their introduction and making refactoring safer. To track improvement, teams should monitor static analysis trends such as new issues and technical debt, and also look for fewer Sev 1 issues in production and faster mean time to repair. False positives in automated scanning can be reduced by giving the tool more repository context, such as excluding inspections in qodana.yaml or silencing them with inline comments.