---
title: "Code Quality"
description: "4 posts about Code Quality, summarised, each linking to the original."
---

# Code Quality
> 4 posts about Code Quality, summarised, each linking to the original.

## Articles

### [Boost Your Pipeline: Top 6 CI/CD Integrations for Qodana](https://yomu.fyi/post/boost-your-pipeline-top-6-ci-cd-integrations-for-qodana.md)
- Company: [Jetbrains](https://yomu.fyi/company/jetbrains.md)
- Author: Kerry Beetge
- Published: Oct 14, 2026
- Type: Tutorial

Qodana brings IntelliJ IDEA’s inspection engine into CI/CD pipelines, automating code quality checks on every commit to catch issues before they reach production. The tutorial covers six integrations—GitHub Actions with its v2025.2 marketplace action and pull request integration, GitLab’s native CI/CD component that removes Docker complexity, TeamCity’s GUI-based native build runner with no YAML required, Jenkins via Docker-based Jenkinsfile for complex workflows, Azure Pipelines’ QodanaScan@2025 task displaying results in the Extensions tab, and CircleCI with a container-optimized orb. Each integration supports quality gates, baseline comparisons, and automated feedback, enabling teams to enforce consistent coding standards without disrupting existing workflows. Teams can select the integration that matches their current platform without requiring new tools or retraining. This shift-left approach reduces rework by catching defects early and transforms the pipeline into a quality guardian.


### [Code Quality Never Changes – Or Is AI Challenging This Notion?](https://yomu.fyi/post/code-quality-never-changes-or-is-ai-challenging-this-notion.md)
- Company: [Jetbrains](https://yomu.fyi/company/jetbrains.md)
- Author: Kerry Beetge
- Published: Oct 8, 2026
- Type: Problem & solution

The post examines whether AI-generated code challenges traditional notions of code quality, especially in game development where performance, stability, and security are critical. It defines code quality across six dimensions: correctness, performance, stability, security, maintainability, and reusability. The author notes that while 95% of Unity developers use AI, AI code produces 1.7x more logic errors and more security issues than human code, though the overall issue rate is comparable. The proposed solution is to pair AI code generation with deterministic static analysis tools like Qodana, which can catch issues across all six quality dimensions. Studies cited show that combining static analysis with LLM calls reduces token usage by 72–92% and leads to 33% fewer vulnerabilities in master branches. The post demonstrates this workflow using Qodana integrated with GitHub Actions and IDE hooks that force AI agents to reformat and lint generated code.


### [Software Quality Assurance Tools and Tips for Developers](https://yomu.fyi/post/software-quality-assurance-tools-and-tips-for-developers.md)
- Company: [Jetbrains](https://yomu.fyi/company/jetbrains.md)
- Author: Kerry Beetge
- Published: Sep 29, 2026
- Type: Explainer

Software quality assurance (SQA) has evolved from a final gate to a continuous process integrated throughout the SDLC. The 2025 Stack Overflow Developer Survey shows 84% of developers use AI tools, increasing the need for tighter quality reviews. Shift-left analysis moves checks earlier, catching defects when cheapest and easiest to fix, and poor software quality costs the US at least $2.41 trillion annually. Essential SQA tools include static code analyzers, unit testing frameworks, integration testing tools, performance testers, and security scanners, but no single tool covers every aspect, so a layered toolkit is vital. A balance of automated and manual code review remains important, and best practices include automating repetitive checks, integrating testing into CI/CD, monitoring technical debt, and treating security as integral.


### [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.