I am personally starting to be a bit fed up with the prevalence of what I call "linking hit-and-runs" answers (Example).
The major problems with these types of answer are that:
- They require the asking user to read a complete article (or worse, actually browse the site) to find something that may be buried really deep.
- They usually steal reputation from people who are putting an effort in their answer.
- The links may die unexpectedly, leaving future visitors without the answer they are looking for.
As you can see from the numbers below, the problem is quite prevalent. I've defined a "link-and-run" (LAR) as a post where links occupy >= 15% of the body and the character count is lower than or equal to 200.
For a possible solution, please see Reduce posting of “linking hit-and-runs” answers.
The following program calculates the ratio of posts considered to be "linking hit-and-runs" in the Stack Exchange Network data dumps. Simply run it in the same directory as the data-dump you want to parse.
It will show you two ratios. LAR/Total is the number of LARs relative to the total numbers of posts. LAR/Qualify is the number of LARs relative to the number of posts below 200 characters.
Source: Read Source
These numbers are calculated with the application above using the January 2010 data dump.
Ratio LAR / Total ( Percent ) LARs/Total 97787 / 1819345 ( 5.37 % ) LARs/Qualify 97787 / 459812 ( 21.27 % )
Ratio LAR / Total ( Percent ) LARs/Total 3918 / 94217 ( 4.16 % ) LARs/Qualify 3918 / 22399 ( 17.49 % )
Ratio LAR / Total ( Percent ) LARs/Total 6751 / 84934 ( 7.95 % ) LARs/Qualify 6751 / 28233 ( 23.91 % )