3 ms·
haldar's summary is completely incorrect, as you would expect from someone who says 'tl;dr' the paper finds that faults (and wmc (methods per class), cbo (coup
by kragen 4y ago
haldar's summary is completely incorrect, as you would expect from someone who says 'tl;dr'
the paper finds that faults (and wmc (methods per class), cbo (coupling between object classes), response for a class (rfc), number of methods added (nma), etc.), correlate to class size (non-comment source lines of code), not program size
it only looked at one program so it could not measure any effects due to program size
moreover it wasn't measuring code quality in the sense of 'defects per kloc', it was measuring defects (whether a bug had been detected in a class in the field or not)
stripping away the acronyms, what they found was that classes that contained more code more often had at least one bug, and also had more methods, but that having more methods without having more code didn't make classes significantly more likely to have a bug
and similarly for the other complexity metrics like how many different methods a class calls and implements (rfc)
this is unsurprising, since things like the number of lines of code in a class and the number of different methods in a class are just alternative metrics of class size, and everyone knows that in general more code means more bugs
that's why we measure code quality in defects per kloc and not total defects. the paper didn't even try to measure code quality in that sense
that doesn't mean the paper is bad. if the paper's authors are correct that many other papers have failed to control for size in their defect metrics, they have identified a serious shortcoming in the existing research literature; haldar merely totally failed to understand them
so the paper haldar tried to summarize doesn't measure either program size or code quality
(some of their references did look at program size tho)
why are none of the other comments pointing this out
are they all just commenting without having read the paper
now i am sad
- ziddoap 4y ago>as you would expect from someone who says 'tl;dr' ...What? This is hilarious. How is using an acronym to provide a brief summary of something indicative of correctness?
- kragen 4y ago'tl;dr' is an abbreviation for 'too long; didn't read' people who don't read long things sometimes know a lot about things like how to weld, how to comfort the grieving, and what makes them happy, but they are always profoundly ignorant when it comes to book learning that's what happened in this case, where haldar's summary claims that this paper shows that a variable they didn't attempt to measure is the best predictor of another variable they didn't attempt to measure evidently he just looked at the diagrams and guessed what the words meant
- ziddoap 4y ago>people who don't read long things sometimes [...] but they are always profoundly ignorant when it comes to book learning You seem to have fundamentally misunderstood how this acronym is used. When provided by an author, it doesn't mean that the author didn't read... It's literally just a substitute for "Summary:". An indication to the reader that if they find the article too long to read, they can read the immediately following subsection to get a summary of the article. Do you also think that people who say "Summary:" are profoundly ignorant? Or are you just against acronyms?
- kragen 4y agoprobably you haven't noticed this, but using 'tl;dr' instead of 'summary' or 'abstract' is a group identity marker by which the author shows solidarity with their (presumably profoundly ignorant) readers. it's the same sort of gesture as describing the paper's authors as 'eggheads' or 'boffins' and evidently in this case the blog post author really didn't read the paper they were 'summarizing' i find your contributions so far to the discussion of this paper profoundly disappointing
- ziddoap 4y ago>probably you haven't noticed this >their (presumably profoundly ignorant) >i find your contributions so far to the discussion of this paper profoundly disappointing I'm not sure why you are so hostile, and why you think everyone except yourself is profoundly ignorant, but it's clear that you have some sort of world view where you're superior than anyone else you interact with. I doubt anything I say would convince you otherwise. tl;dr: I found this conversation disappointing, too.
- kragen 4y agoi frequently interact with people i admire and who know more than i do (and sometimes they are the same people), and, as i said above, even people who are profoundly ignorant about book learning are often wise about many other things rather than being hostile, i have taken the time to explain in more detail the things you asked about in my previous comments because they were unclear to you i am surprised that you have stooped to launching personal attacks on me in this comment, since so far i have criticized only your low-quality comments (and the original blog post) rather than any presumed personal attributes of yours try to do better please
- jt2190 4y ago> How is using an acronym to provide a brief summary of something indicative of correctness? I’m struggling to understand how this is the point that’s most worth debating here. What do you propose we’ll learn?
- kragen 4y agoit turns out they thought they were being criticized so they got defensive, explaining their otherwise shockingly aggressive and even mendacious comment thread here: https://news.ycombinator.com/item?id=33567361 https://news.ycombinator.com/item?id=33567361 not sure that's a good excuse for their total failure to contribute anything substantive though
- deleted 4y ago[deleted]