Every developer knows the feeling. You open a ticket that looks simple. A small change. Maybe one endpoint, one validation rule, one extra field. Then you open the codebase.
The logic is spread across three layers. The naming is inconsistent. Tests are missing or outdated. A dependency throws warnings. One change breaks something unrelated. Suddenly, the “small ticket” is no longer small.
This is where code quality stops being an abstract engineering ideal and becomes something very concrete:
speed.
During the PSG technauts TechNight on June 15, 2026, Dick Dijk gave a talk about SonarQube and code quality. But the most interesting part was not the tool itself. It was the problem behind it: how do you keep a codebase workable when teams, features, frameworks and deadlines keep changing?
