this post was submitted on 25 Oct 2025
8 points (59.1% liked)
Programming
23314 readers
268 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How does one measure code quality? I'm a big advocate of linting, and have used rules including cyclomatic complexity, but is that, or tools such as SonarQube, an effective measure of quality? You can code that passes those checks, but what if it doesn't address the acceptance criteria - is it still quality code then?
What if we don't define code quality in terms of the aesthetics of that code?
Why is the perception of code quality so important prior to that code ever having been executed?
How can we test our code? What does it's testability tell us? What do it's tests tell us?
Is our test code good quality? Does it need to be? How can we know it is? Is it's quality measured by the same metrics as the code it is testing?
'Clean Code' by Uncle Bob is a good place to start when answering these questions.
And here I was, almost agreeing. Clean code is defining quality through aesthetics, and that book is a very bad advice of how to define anything
That's a very narrow definition of the contents of the book.