Metrics that point out use of bad coding practices could be a good thing. But it wouldn't measure "code quality" -- as that's largely based on the quality of the design.
I don't think we'll ever have an objective, quantitative measure for design quality any moreso than we can objectively measure the quality of a movie or novel. At best, a metric might be able to compare the design quality of three different same-technology implementations of the same functionality, but who would bother implementing the same functionality three times in the same technology?
If you try to compare the ugliness of applications with different functionality, how could a program separate the simplicity of the design from the simplicity of the requirements?
Flat View: This topic has 50 replies
on 51 pages
[
«
|
789101112131415
|
»
]