Lately I was asked how many bugs and smells detected through SonarQube were acceptable for a software product. And a Scrum master inquired which organizational changes are necessary to empower software developers to write good code. Speechless and dumbfounded I was unable to answer these questions.
After quite some time I realized these persons believe tools can measure the quality of software. But tools can only measure
non-quality.
They tell you when you are doing it wrong, only your heart can tell you when you are doing it right.
But first that does it means to have a quality software product?