DEV Community

Discussion on: What does code quality mean to you?

Collapse
alainvanhout profile image
Alain Van Hout • Edited

To me, code quality means any changes to code that improve predictability and reduce the amount of effort needed to make future changes. Generally speaking, that's done through rules of thumb (use clear variable names, limit method length, use unit tests), which on average will have a positive effect on the aforementioned predictability and effort.

From another viewpoint, code quality is one facet that helps is increasing maintainability (others are good communication, proper requirements, reflecting on architectural tradeoffs, etc).

Collapse
thenjdevopsguy profile image
Mike Levan Author

Yeah, this is a good point. "Increasing maintainability" is definitely crucial. Making the code easier to read ultimately makes it easier to maintain as well. Good one!

Collapse
alainvanhout profile image
Alain Van Hout • Edited

Thanks 😁. I think that's an important and generally overlooked point: if maintainability is the goal, and code quality just a tool (and not the actual goal), then you (often) need to decide on what you need to spend your time on to optimally increase maintainability. When you need to spend twice as much time to get that code quality from 90 to 95% (figuratively speaking), then chances are that that time is better spent on other improvements that have a higher impact on maintainability.