AUTHOR REBUTTAL

I am disappointed that Mr. Weiss has missed the entire point of my recent paper on the readability of computing periodicals. While his first paragraph provides a good summary of the paper, he then raises two completely irrelevant questions. The main question is, “Are computing journals readable?” Many computing professionals (including myself) feel they are not. This paper gives empirical evidence on readability levels. The next question is, “What factors affect readability?” There is much research (cited in the article) to show that word and sentence length are valid predictors of readability levels. For example, since grammar school we have all been instructed not to use “run-on” sentences. Scholarly journals are real abusers of this basic principle of clear communication. Also, excessive use of “big words” may look impressive, but this practice does not contribute to conveying information. Would (should) we use such words and sentences in conversations?

Mr. Weiss criticizes Flesch’s formula. Even a cursory review of the literature on readability will show Flesch to be the major figure in this area. Furthermore, other approaches would have yielded substantially the same results. Computing periodicals are not very readable. By the way, Mr. Weiss makes an erroneous statement in his third paragraph. It is an index score of 100 (not zero) that represents maximum reading ease. Also, Mr. Weiss’ comments on other considerations determining readability are fully recognized in the article with reference citations to detailed critiques of readability indices.

Readability indices indicate potential barriers to effective communication of ideas. I would ask that the reader review Figure 1b in the article which shows an example passage with a low readability score. Try reading it out loud to yourself or someone else. This is not a readable passage.

Mr. Weiss uses terms such as “presumptuous,” “ridiculous,” “dangerous,” “wrong,” and “foolish” to refer to the approach taken in this paper to measure readability. What approach would Mr. Weiss suggest? What specific guidelines can be given to writers, editors, and publishers? Criticisms without specific alternatives have little value.

In spite of the fears of Mr. Weiss, I believe there is a growing concern about readability. Requests for the BASIC program that I used in the study came from a very surprising cross-section of readers. In addition to US colleges and universities, I received many requests from foreign institutions. Other requests came from government (including military) organizations. Requests also came from private organizations and individuals. As a side note, the paper received coverage in Business Week, Chronicle of Higher Education, New York Times, and even USA Today.

In closing, I would like to “challenge” Mr. Weiss to analyze a current or future writing project using a readability index. I believe that a very useful perspective will be gained on the difficult task of writing papers with a high degree of readability.

--Ronald S. Lemos, Carson, CA REVIEWER RESPONSE

I am delighted that Mr. Lemos found my review readable and understandable in spite of my deliberate use of artificially long sentences and multisyllabic words, and grateful for this opportunity to say again what he understood at once: that I think the Flesch readability index is a bunch of dangerous nonsense.

I share Lemos’s concern for the readability of computing periodicals, and I truly understood that this concern probably stimulated his article and the editors’ acceptance of it. I did not cite this as the author’s main point because he did not make the point clear and explicit. Instead, he said, perhaps with academic irony, “Readers are left to draw their own conclusions as to the appropriateness of the apparent degree of difficulty in readability evident in the magazines analyzed.” (There is a sentence that Flesch would deplore]) I took as the entire point of the article the one he identified in his second paragraph, saying, “In this article we are concerned with measuring readability,” and I undertook to criticize his measuring tool and the meaning that might be attached to measurements made with it.

I agree with Flesch and Lemos that long words and long sentences make for hard reading, but I do not agree that short sentences and short words are all that are needed for easy and interesting reading, the common meaning of the word “readable.” I object to Flesch’s arbitrary assignment of the word “readable” and the phrase “reading ease” to a measure that includes only these characteristics. Indeed, I deplore any purely mechanical attempt to measure with a single number such a multidimensional and indeed, artistic, characteristic as “readability” in its common meaning.

I consider such efforts to be dangerous, for their use and acceptance will lead technical writers away from the effort to achieve clarity with unity, coherence, and emphasis and will substitute the false rule of “only short words and short sentences.” Lemos tells us that he has had many requests for the BASIC program that he used, so we can confidently expect this ridiculous definition of “readability” to spread.

To emphasize the nonsensical nature of the Flesch Reading Ease Index I have taken up Lemos’s challenge by rewriting my response with short sentences and words to achieve an RE of 117.943:

Hey. Right. Ahhh. Thanks, Ron. You know, I am glad you wrote. I am glad you came on so strong. You read my piece. You caught my drift. You got my point. You heard me. Right. Yeah. Good.

You got it. The Flesch thing is dumb. The Flesch thing is bad. No one with his head on right should use it. I wish we could stop it. Thank you, Ron, for the chance to say it once more. Good.

You and I, Ron, we feel the same way about big words and long strings of words. We hate them. Right. They are hard to read. Right. Yeah. But that is not all. Short words and short strings of words can be hard to read and real dull too. Yeah. You know, there is more to easy to read than just short. Lots more. Right. Yeah.

Stop Flesch while there is time] Hey]