http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Metrics should not be known by developers, if you do not known the metric you cannot write code only for the sake of having good metrics. But in the end metrics themselves are not so useful. Code quality can means different things, I think that we should speak of Code quality in a team, meaning that the code have good quality if everyone in the team can look at it, and understand how it works and most important, he can modify it with good confidence. Clearly that are some factor like number of bug found that can be also a good starting point to measure quality of a particular piece of code. alk. http://ayende.com/3552/meaningless-code-quality-part-2#comment3http://ayende.com/3552/meaningless-code-quality-part-2#comment3Wed, 27 Aug 2008 10:22:11 GMTMetrics about coupling and dependencies are a good indication of maintainability. But, they're not foolproof. One thing I've learned over the years is to never underestimate people's ability to write lousy code to make metrics look good. http://ayende.com/3552/meaningless-code-quality-part-2#comment2http://ayende.com/3552/meaningless-code-quality-part-2#comment2Mon, 25 Aug 2008 13:29:38 GMTA good code quality metric exists - it's WTFs/minute. Easily googlable. For example, http://imod.co.za/2008/02/07/wtf-measure-of-good-quality-code/ http://ayende.com/3552/meaningless-code-quality-part-2#comment1http://ayende.com/3552/meaningless-code-quality-part-2#comment1Mon, 25 Aug 2008 04:55:58 GMT