Benutzer:Port(u*o)s/tl;dr

aus Wikipedia, der freien Enzyklopädie
Zur Navigation springen Zur Suche springen

Vorlage:Essay Vorlage:Policy in a nutshell

„Je n'ai fait celle-ci plus longue, que parce-que je n ai pas eu le loisir de la faire plus courte.“

Blaise Pascal[1]

Überlange, ungegliederte Beiträge stellen andere Diskussionsteilnehmer vor ein Dilemma: Sollen sie in übertriebenem Maße Zeit darauf verwenden, den Sinn Deiner Worte zu ermitteln, oder eher ein wenig grob sein, indem sie Deinen Beitrag einfach überlesen? Angesichts dieser Not ist es kollegialer und auch diskussionsförderlich, ein paar Augenblicke darauf zu verwenden, diese Gedanken auf Häppchengrösse zu bringen und - wir Schweizer sagen: pfannenfertig - zu servieren.

Traditionellerweise wird die Wendung too long; didn't read (abgekürzt tl;dr) im Internet als Antwort auf einen übermässig langen Text gebraucht. Damit zeigt ein Leser an, dass er dieses Statement wegen seiner unangemessenen Länge beiseitegelassen hat. [2] Im Zusammenhang dieses Textes geht es insbesondere um Wikipedia-Diskussionen.

As a label, it is sometimes used as a tactic to thwart the kinds of discussion which are essential in collaborative editing. On the other hand, tl;dr may represent a shorthand acknowledgement of time saved by skimming over or skipping repetitive or poorly written material. Thus the implication of the symbol can range from a brilliant and informative disquisition being given up due to lack of endurance, interest, or intelligence, to a clustered composition of such utter failure to communicate that it has left the capable reader with a headache; judging this range is very subjective.

Reasons for length, good or bad[Bearbeiten | Quelltext bearbeiten]

Many people who edit Wikipedia do so because they enjoy writing. However, that passion for writing can influence what they write to be longer than necessary. Sometimes, this is because the writer incorrectly believes that long sentences and big words will make them appear learned.[3] In other cases, misplaced pride prevents the author from seeing that not every word in their golden prose is necessary. Perhaps the author may be too hurried (or lazy) to write clearly and concisely; recall Pascal's famous quote, "I made this so long because I did not have time to make it shorter." While a genius like Pascal may have been justified in that balancing of priorities (just as neurosurgeons may not spend time doing the hospital landscaping), the rest of us must do our share of the work. In a related vein, administrator candidates may be judged merely by how much they have written, versus the much more subjective value of their contributions.

Due to these factors, many articles, instructions and especially comments on Wikipedia are longer than necessary. Some of Wikipedia's core policies are considered by some to be too long (e.g. Creative Commons license). This may be considered to put too much burden on the readers to understand. Such a problem can be seen in other applications as well.[4]

Writers often begin a project by writing long-winded drafts. As they go through the iterative process of revising their work, they (should) come to a better understanding of what they're trying to communicate, and be able reduce the length of the work. If this process is stopped prematurely, the result is needlessly long (to which Pascal's earlier quote refers). Writers may err towards wordiness out of concern that short prose which is not carefully edited (at high time cost) would oversimplify, to the point of distorting or omitting, or carry a higher risk of being misunderstood.

Albert Einstein described the work of theorists as making theory as simple as possible, without failing to explain all empirical cases. This is often paraphrased as "everything should be made as simple as possible, but not simpler." Much argument between individuals results from one trying to point out the ways in which another's model of reality is incomplete. Thus the concept that Einstein mentioned often spurs lengthy exposition, often to account for the corner cases.

A venerable aphorism is that "brevity is the soul of wit."[5] A similar sentiment advises would-be skilled writers to "omit needless words."[6] Editors are encouraged to write concisely, and avoid undue technical jargon. If it becomes necessary to write lengthy text in an article, editors may wish to include a short summary. Additionally, it may be appropriate to use simple vocabulary to aid the readers in comprehension. Many readers may not use English as a primary language, or may have other "unarticulated needs".[7]

Needless length may be interpreted as a mark of arrogance. The message to the reader seems to be, "My time is more valuable than yours. I can't be bothered to express myself clearly and concisely, so I'm shifting the burden to you to sift my words." Some people are constitutionally more loquacious than others, and thus may not be arrogant so much as miscalibrated. Still, the loquacious must force themselves to see things through the eyes of readers, and push beyond their own comfort level — what they themselves think is already clear — to arrive at greater clarity. Taking the time to distill your thoughts not only helps you communicate more effectively, but also builds rapport with your readers.

The phrase wall of text is frequently used to describe overlong, unformatted contributions.

Reducing wordiness[Bearbeiten | Quelltext bearbeiten]

If you encounter excessively long text in a Wikipedia article, consider trimming it down (if it is truly redundant) or splitting it into another article to fit our summary style (which helps provide drill-down ability for the readers). (More info at WP:SPINOFF.) Tag excessively long plot summaries with the {{Plot}} template if you can't trim it down yourself.

Make some effort to understand whatever valid ideas the previous author may have been trying (but failing) to communicate, so that you don't just hastily and inadvertently delete valid rough draft material instead of refining it to a better draft. Remember that your own credibility is at stake as well as that of the loquacious writer, because if you're hasty and harsh enough, you could end up earning a reputation for yourself as someone with incompetent reading comprehension. You may know that this is an unfair reputation, but your actions may speciously make it seem true to others. One of the reasons that some linguists (most famously Geoffrey K. Pullum) have a dim view of Strunk & White's advice "omit needless words" is that in the hands of amateur editors (as opposed to writers—that is, content critics as opposed to content creators), it mistakes all loquaciousness for nonsense and valueless redundancy in one overly hasty, facile stroke of the pen; and it fails to recognize that not all redundancy is cognitively or communicatively valueless. The upshot is simply to consider things circumspectly before deleting content. Note Strunk and White qualified their advice by stating that "this requires not that the writer make all his sentences short, or that he avoid all detail and treat his subjects only in outline, but that every word tell." Deleting is not always equivalent to improving, and intelligently differentiating the cases is seldom a facile affair (or as Strunk and White would recommend, "...is often not easy").

Maintain civility[Bearbeiten | Quelltext bearbeiten]

Sometimes a person might feel that a reader's decision to pointedly mention this essay during a discussion is dismissive and rude. Therefore, courteous editors might, as an alternative to citing WP:TLDR, create a section on the longwinded editor's talk page and politely ask them to write more concisely.

A common mis-citation of this essay is to ignore the reasoned and actually quite clear arguments and requests for response presented by an unnecessarily wordy editor with a flippant "TL;DR" in an attempt to discredit and refuse to address their strongly-presented ideas and/or their criticism of one's own position. This is a four-fold fallacy: ad hominem, appeal to ridicule, thought-terminating cliché, and simple failure to actually engage in the debate because one is supposedly too pressed for time to bother, the inverted version of proof by verbosity.

See also[Bearbeiten | Quelltext bearbeiten]

Vorlage:Wikipedia glossary

Nachweise[Bearbeiten | Quelltext bearbeiten]

  1. Verehrte Patres, ich hatte nicht vor, ihnen so bald und so lang zu antworten. Das eine wie das andere hängt mit der wenigen Zeit, die ich habe, zusammen. Ich habe das hier nur so lang bleiben lassen, weil ich nicht die Muße hatte, es kürzer zu machen. [http://www.archive.org/stream/lesprovincialeso00pasc#page/282/mode/2up Lettres Provinciales (1656-1657), Nr. 16
  2. Vorlage:Cite dictionary
  3. Study: Simple Writing Makes You Look Smart. Livescience.com, 31. Oktober 2005, abgerufen am 13. April 2012.
  4. McCullagh, Declan. "FTC says current privacy laws aren't working," CNET News. June 22, 2010.
  5. William Shakespeare: [[Hamlet]]. Washington Square Press, New York 1992, S. 89.
  6. William Strunk: The Elements of Style. Bartleby.com, 1918, Elementary Principles of Composition.
  7. Chen, Brian X. "How Microsoft crowdsourced Office 2010," Wired. June 30, 2010; excerpt, "when users struggle to finish a task, ... researchers can examine why they are becoming confused or taking too long and work to resolve the problem. This is what usability researchers call "unarticulated needs" ... [and] any unaddressed shortcomings are "part of [an] engineering road map."

External links[Bearbeiten | Quelltext bearbeiten]

Wiktionary: TLDR – Bedeutungserklärungen, Wortherkunft, Synonyme, Übersetzungen