TL;DR (That is, Too Long; Didn’t Read)

From The Scholarly Kitchen:

I recently spent the better part of a work day reading Richard Poynder’s 87-page treatise on the current status of open access. Even as I printed it out, so as to protect myself from any digital distraction while reading, I wondered whether reading the full text was in fact the best use of my time. Was there an executive summary that might suffice? Could I skim it and just pick up the general gist of his argument? Truthfully, the response to both questions turned out to be No. It was a substantive piece and thoroughly documented, via footnotes as well as embedded links. Clearly, a thorough reading was going to require attention and time. Did I have either?

I was not the only person who reacted to the length of Poynder’s “ebook.” Others were having to make the same decision about whether the time spent reading would be well-invested. Although I hadn’t realized something was in the works at the Scholarly Kitchen, Rick Anderson, Associate University Librarian at the University of Utah, had done some of the heavy lifting in evaluation (see here). On Twitter, a researcher asked for the TL;DR version and the author quickly referred him to Digital Koans where the selection of a single concluding paragraph summed up what the author felt was covered in the meaty essay.

. . . .

But even so, someone else tweeted out that, no matter how worthwhile the content, he or she could hardly hand over a document of 87 pages to their provost and expect them to read something of that length. The time commitment required to consume the dense material would not seem justifiable, unless the topic was one with which the provost was already deeply concerned.

This gives me pause, because how we view the task of reading, how much time we allocate to reading, and the criteria for determining what is worthy of being read continues to be a challenge. It is something with which many professionals wrestle on a daily or weekly basis.

. . . .

Given the demands of real life, how much reading is feasible? The group included Verity Archer of the Federation University in Australia, who referenced the concept of “time privilege”; the fact that those with the greatest flexibility in their schedules are usually the most privileged when it comes to reading. Those early career researchers who most need the time to read and absorb the literature are generally the ones most weighted down with teaching and administrative tasks. Women who are primary care-givers outside of the office will tend to push the work of reading into their leisure evening or weekend hours. If reading is part of one’s day job, in Archer’s view, then the available hours in the workday should allow for it.

. . . .

Others referenced irregular reading habits unless faced with a grant or syllabus deadline, at which point they would do a spell of binge-reading. The hesitation associated with that practice was summed up well by David A. Sanders of Purdue when he wrote, “We should…resist the urge to promote research results that we have not personally evaluated.”

A humanist quoted in the Times Higher Ed piece wrote that the question of determining what to read was “now infinitely more complex in the age of digital and computational possibilities”.

. . . .

The Danish AI company, UNSILO, recently reported on results from their 2019 survey on the acceptance and usage of AI in academic publishing. They found that publishers have hitherto focused on how AI might solve their own problems rather than those of the research community. As noted on page 8 of the report, “The primary perceived benefit of AI was that it could save time. This could be seen as evidence of a new realism among publishers, since the thinking is presumably to apply AI tools to relatively straightforward processes that could be completed faster with the aid of a machine, such as the identification of relevant articles for a manuscript submission, or finding potential peer reviewers who have authored papers on similar topics to a manuscript submission.” While I see this as a sensible use of AI by content and platform providers, the pragmatic reality suggests an uncomfortable possibility. There is no magic solution. AI isn’t currently up to the task.

In the earlier instance of the librarian reading for purposes of peer review, there was a quick response from one of the founders of Scholarcy, an application offering summaries of full-text articles to the researcher. The tagline for the company is blunt “Read less, learn more,” and springs from the founders’ own frustrations in trying to handle the volume of content to be read in the PhD process. Among other functionalities noted in its marketing text, Scholarcy will highlight the important findings in a paper, eliminating the need for the reader to print out and laboriously highlight critical segments or sentences. The reader can customize specific aspects — the number of words, the level of highlighting, and the level of language variation (this last allows you to more easily cite the finding in your paper). Scholarcy will navigate the user to Google Scholar, to arXiv, and to other open source material referenced in the paper. There are additional functionalities and Scholarcy invites the visitor to their site to engage with their demo, a worthwhile use of 15 minutes. Their tool is recommended for researchers, librarians, publishers, students, journalists, and even policy wonks.

Link to the rest at The Scholarly Kitchen

PG is not an expert on academic writing, but in the legal world, there is a lot of poor writing. Sentences and paragraphs are structured according to standard practice, citations are perfect (thanks, in part, to some computer assistance), but the thought behind the expression often seems to be haphazard and poorly-realized.

Contracts written by lawyers working for or in large business organizations are the worst. You stack poorly-organized thinking upon legal necessities upon boilerplate mindlessly copied and pasted and you end up with an extraordinary mess that sometimes contradicts itself and requires that you go to paragraph 54 to understand something written in paragraph 29, which is later modified in paragraph 62(a)(iii).

1 thought on “TL;DR (That is, Too Long; Didn’t Read)”

  1. When I was working on a PhD many years ago, I quickly learned how to read books without reading them. When you concentrate on a single subject, you become adept at picking out where the author is coming from and where they are going without reading all their words. Unfortunately, a lot of books, especially self-help books today, three hundred pages can easily be condensed to a page or two (if that)of meat that distinguishes that book from a dozen other similar books.

    There are exceptions, writings that require scrutiny and rereading to appreciate, but they are rare.

Comments are closed.