3 ms·
This is... not at all a useful analysis, to put it lightly. The word "bug" or "defect" appears ZERO times in this study. Any study that completely ignores def
by userbinator 4y ago
This is... not at all a useful analysis, to put it lightly.
The word "bug" or "defect" appears ZERO times in this study.
Any study that completely ignores defects in measuring "code quality" is at best misguided, and at worst could drive change that actually results in increased defect density.
High quality code can simply be defined as code that has few bugs. Unfortunately that's a little harder to measure, but they could've at least analysed the issues for a start.
That said, I don't think there's going to be any correlation between the presence of swearing and the defect density.
- riffraff 4y agoThe tool they use for evaluation (softwipe) is discussed in another paper, but seems to basically count/combine the results of a set of different static and dynamic analysis tools (ASan, UBSan, cppcheck etc) Presumably those results should correlate somewhat with bugs and defects.
- z3t4 4y agoThe less code you write the fewer bugs, so LOC should be a good indicator of code quality :P But bugs alone says nothing about code quality, the more you look, the more bugs you will find. More popular software will have more bugs (found). Style guides are not the same as quality. Some people argue about line length, white space, and where to put line breaks, but that has nothing to do with the quality of the code/software, but it's easy to measure. Do you understand what the code does ? How easy is it to make a change ? Comprehension and maintainability probably results in better code/software quality, but is difficult to measure. Maybe if we measure the average bug count per user, as well as let users assess/rate the software - does the code/software do the job it was written for?
- ordu 4y ago> High quality code can simply be defined as code that has few bugs. Unfortunately that's a little harder to measure, but they could've at least analysed the issues for a start. It is nearly impossible to measure directly. One needs to find all the bugs to measure defect density directly. There are indirect ways, one could use a proxy variable, and they did. They used static analysis as a proxy variable, this choice has some traps to avoid, but bugs from bug-trackers or CVE's is highly dependent on a development practices and popularity of the code, they can (I'd say must) correlate with swearing by themselves. To deal with that one would need to formulate a causal hypothesis for real and to test it for real. Such a study is not for a bachelor thesis, it would be master's at least. Though I'd like to see authors to sophisticate their techniques enough to dig out a causal explanation.