Warning

 

Close

Confirm Action

Are you sure you wish to do this?

Confirm Cancel
BCM
User Panel

Site Notices
Posted: 8/3/2013 8:30:18 AM EDT
I didn't get the memo.
Link Posted: 8/3/2013 8:30:54 AM EDT
[#1]
Is google broke?
Link Posted: 8/3/2013 8:31:16 AM EDT
[#2]
Too Long; Didn't Read.



Proof that ADD is rampant in GD.




Link Posted: 8/3/2013 8:31:20 AM EDT
[#3]
Too long, didnt read



Lock er down!!
Link Posted: 8/3/2013 8:31:38 AM EDT
[#4]
Link Posted: 8/3/2013 8:32:01 AM EDT
[#5]
Link Posted: 8/3/2013 8:33:00 AM EDT
[#6]

Twat licked; dick ready.

Link Posted: 8/3/2013 8:35:01 AM EDT
[#7]
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Is google broke?
View Quote


As usual, FPNI. I came to post this.
Link Posted: 8/3/2013 8:35:25 AM EDT
[#8]
5 years and 2600 posts later?

Good morning!



Link Posted: 8/3/2013 8:35:28 AM EDT
[#9]


Discussion ForumsJump to Quoted PostQuote History
Quoted:



Is google broke?
View Quote






Why should the OP go through that trouble - when he can spend 4X as long to ask GD schmucks ?





 
Link Posted: 8/3/2013 8:35:57 AM EDT
[#10]
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Is google broke?
View Quote


Yes it is. I Googled smartass and all it came up with was this gif.


Link Posted: 8/3/2013 8:36:15 AM EDT
[#11]
Discussion ForumsJump to Quoted PostQuote History
Quoted:

Twat licked; dick ready.

View Quote


Now I wil no longer read it as "too long, didn't read"

Posted Via AR15.Com Mobile
Link Posted: 8/3/2013 8:37:12 AM EDT
[#12]
Discussion ForumsJump to Quoted PostQuote History
Quoted:


Why should the OP go through that trouble - when he can 4X as long to ask GD schmucks ?
 
View Quote View All Quotes
View All Quotes
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Quoted:
Is google broke?


Why should the OP go through that trouble - when he can 4X as long to ask GD schmucks ?
 



Ain't nobody got time for dat either, apparently.  

Link Posted: 8/3/2013 8:38:17 AM EDT
[#13]

Discussion ForumsJump to Quoted PostQuote History
Quoted:


5 years and 2600 posts later?



Good morning!
View Quote


Poor OP. Imagine all of those boring walls of text that he had to struggle through because he didn't know how to tl;dr.



 
Link Posted: 8/3/2013 8:40:37 AM EDT
[#14]
Discussion ForumsJump to Quoted PostQuote History
Quoted:

Twat licked; dick ready.

View Quote

Link Posted: 8/3/2013 8:41:45 AM EDT
[#15]

Link Posted: 8/3/2013 8:42:47 AM EDT
[#16]

Discussion ForumsJump to Quoted PostQuote History
Quoted:
Yes it is. I Googled smartass and all it came up with was this gif.

http://www.ar15.com/media/images/xAvatar/195010.GIF



View Quote View All Quotes
View All Quotes
Discussion ForumsJump to Quoted PostQuote History
Quoted:



Quoted:

Is google broke?




Yes it is. I Googled smartass and all it came up with was this gif.

http://www.ar15.com/media/images/xAvatar/195010.GIF



BOOM!



 
Link Posted: 8/3/2013 8:42:50 AM EDT
[#17]











Too long; didn't read (TL;DR)




Overly long unformatted statements present fellow editors a dilemma:
spend excessive time parsing out what you mean or being mildly rude in
not actually reading what you wrote. It is more collegial and
collaborative to take an extra few moments to distill your thoughts into
bite size pieces.






Traditionally, the phrase too long; didn't read (abbreviated tl;dr or simply tldr)
has been used on the Internet as a reply to an excessively long
statement. It indicates that the reader did not actually read the
statement due to its undue length.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-2][2][/url]
This essay especially considers the term as used in Wikipedia
discussions, and examines methods of fixing the problem when found in
article content.






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




Many people who post on Arfcom 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.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-3][3][/url]
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 Arfcom 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 problems can be seen elsewhere.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-4][4][/url]






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 to reduce the length of the work. If this process is stopped
prematurely, the result is needlessly long (as shown by Pascal's quote).
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. His remark 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 may spur lengthy exposition,
often to account for the corner cases.






A venerable aphorism is that "brevity is the soul of wit."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-5][5][/url] A similar sentiment advises would-be skilled writers to "omit needless words."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-6][6][/url] 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 readers in comprehension. Many readers
may not use English as a primary language or may have other
"unarticulated needs".[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-7][7][/url]






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 WP:Walls of text is frequently used to describe overlong, unformatted contributions.






Reducing wordiness




If you encounter excessively long text in a Arfcom post, 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




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.






Lastly, shear laziness
or excessively concise may miss an important set of details necessary
to include a well branched entry despite lacking the requisite patience.
.



References







  1. ^ Lettres Provinciales (1656-1657), no. 16.


  2. ^ "Too long didn't read". Urban Dictionary. Retrieved 2008-05-13.


  3. ^ "Study: Simple Writing Makes You Look Smart". Livescience.com. 2005-10-31. Retrieved 2012-04-13.


  4. ^ McCullagh, Declan. "FTC says current privacy laws aren't working," CNET News. June 22, 2010.


  5. ^ Shakespeare, William (1992). Hamlet. New York: Washington Square Press. p. 89. Act 2, Scene 2, line 90: "Therefore, since brevity is the soul of wit..."


  6. ^ Strunk, William (1918). "Elementary Principles of Composition". The Elements of Style. Bartleby.com. Retrieved 2008-05-13.


  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."


  8. ^ "Is 'Y' a Generation of entitled little shits". Pedestrian TV. 10 July 2013. Retrieved 15 July 2013.






External links

Tim Dowling, "Arfcom long-winded for you? Try the simple version," The Guardian,14 January 2008.

See also

{{Very long}} a.k.a. {{Tldr}}—Template used to flag articles or sections that need trimming.





 
Link Posted: 8/3/2013 8:43:16 AM EDT
[#18]
Discussion ForumsJump to Quoted PostQuote History
Quoted:



Too long; didn't read (TL;DR)

Overly long unformatted statements present fellow editors a dilemma: spend excessive time parsing out what you mean or being mildly rude in not actually reading what you wrote. It is more collegial and collaborative to take an extra few moments to distill your thoughts into bite size pieces.

Traditionally, the phrase too long; didn't read (abbreviated tl;dr or simply tldr) has been used on the Internet as a reply to an excessively long statement. It indicates that the reader did not actually read the statement due to its undue length.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-2][2][/url] This essay especially considers the term as used in Wikipedia discussions, and examines methods of fixing the problem when found in article content.

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.

Contents



Reasons for length, good or bad

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.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-3][3][/url] 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 problems can be seen elsewhere.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-4][4][/url]

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 to reduce the length of the work. If this process is stopped prematurely, the result is needlessly long (as shown by Pascal's quote). 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. His remark 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 may spur lengthy exposition, often to account for the corner cases.

A venerable aphorism is that "brevity is the soul of wit."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-5][5][/url] A similar sentiment advises would-be skilled writers to "omit needless words."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-6][6][/url] 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 readers in comprehension. Many readers may not use English as a primary language or may have other "unarticulated needs".[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-7][7][/url]

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 WP:Walls of text is frequently used to describe overlong, unformatted contributions.

Reducing wordiness

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

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.

Lastly, shear laziness or excessively concise may miss an important set of details necessary to include a well branched entry despite lacking the requisite patience. .

References[div style='list-style-type: decimal;']
  1. ^ Lettres Provinciales (1656-1657), no. 16.
  2. ^ "Too long didn't read". Urban Dictionary. Retrieved 2008-05-13.
  3. ^ "Study: Simple Writing Makes You Look Smart". Livescience.com. 2005-10-31. Retrieved 2012-04-13.
  4. ^ McCullagh, Declan. "FTC says current privacy laws aren't working," CNET News. June 22, 2010.
  5. ^ Shakespeare, William (1992). Hamlet. New York: Washington Square Press. p. 89. Act 2, Scene 2, line 90: "Therefore, since brevity is the soul of wit..."
  6. ^ Strunk, William (1918). "Elementary Principles of Composition". The Elements of Style. Bartleby.com. Retrieved 2008-05-13.
  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."
  8. ^ "Is 'Y' a Generation of entitled little shits". Pedestrian TV. 10 July 2013. Retrieved 15 July 2013.

External links

Tim Dowling, "Arfcom long-winded for you? Try the simple version," The Guardian,14 January 2008.

See also

{{Very long}} a.k.a. {{Tldr}}—Template used to flag articles or sections that need trimming.
View Quote


TL;DR



Link Posted: 8/3/2013 8:44:17 AM EDT
[#19]
Discussion ForumsJump to Quoted PostQuote History
Quoted:

Twat licked; dick ready.

View Quote



Link Posted: 8/3/2013 8:44:53 AM EDT
[#20]
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Too long, didnt read

Lock er down!!
View Quote


Link Posted: 8/3/2013 8:44:55 AM EDT
[#21]
Quoted:
I didn't get the memo.
View Quote


tl:dr
Link Posted: 8/3/2013 8:45:04 AM EDT
[#22]
Better Nate than Lever
Link Posted: 8/3/2013 8:45:09 AM EDT
[#23]
Discussion ForumsJump to Quoted PostQuote History
Quoted:


TL;DR

View Quote View All Quotes
View All Quotes
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Quoted:



Too long; didn't read (TL;DR)

Overly long unformatted statements present fellow editors a dilemma: spend excessive time parsing out what you mean or being mildly rude in not actually reading what you wrote. It is more collegial and collaborative to take an extra few moments to distill your thoughts into bite size pieces.

Traditionally, the phrase too long; didn't read (abbreviated tl;dr or simply tldr) has been used on the Internet as a reply to an excessively long statement. It indicates that the reader did not actually read the statement due to its undue length.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-2][2][/url] This essay especially considers the term as used in Wikipedia discussions, and examines methods of fixing the problem when found in article content.

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.

Contents



Reasons for length, good or bad

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.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-3][3][/url] 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 problems can be seen elsewhere.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-4][4][/url]

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 to reduce the length of the work. If this process is stopped prematurely, the result is needlessly long (as shown by Pascal's quote). 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. His remark 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 may spur lengthy exposition, often to account for the corner cases.

A venerable aphorism is that "brevity is the soul of wit."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-5][5][/url] A similar sentiment advises would-be skilled writers to "omit needless words."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-6][6][/url] 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 readers in comprehension. Many readers may not use English as a primary language or may have other "unarticulated needs".[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-7][7][/url]

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 WP:Walls of text is frequently used to describe overlong, unformatted contributions.

Reducing wordiness

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

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.

Lastly, shear laziness or excessively concise may miss an important set of details necessary to include a well branched entry despite lacking the requisite patience. .

References[div style='list-style-type: decimal;']
  1. ^ Lettres Provinciales (1656-1657), no. 16.
  2. ^ "Too long didn't read". Urban Dictionary. Retrieved 2008-05-13.
  3. ^ "Study: Simple Writing Makes You Look Smart". Livescience.com. 2005-10-31. Retrieved 2012-04-13.
  4. ^ McCullagh, Declan. "FTC says current privacy laws aren't working," CNET News. June 22, 2010.
  5. ^ Shakespeare, William (1992). Hamlet. New York: Washington Square Press. p. 89. Act 2, Scene 2, line 90: "Therefore, since brevity is the soul of wit..."
  6. ^ Strunk, William (1918). "Elementary Principles of Composition". The Elements of Style. Bartleby.com. Retrieved 2008-05-13.
  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."
  8. ^ "Is 'Y' a Generation of entitled little shits". Pedestrian TV. 10 July 2013. Retrieved 15 July 2013.

External links

Tim Dowling, "Arfcom long-winded for you? Try the simple version," The Guardian,14 January 2008.

See also

{{Very long}} a.k.a. {{Tldr}}—Template used to flag articles or sections that need trimming.


TL;DR



Well shit, who didn't see that coming.  


Link Posted: 8/3/2013 8:46:31 AM EDT
[#24]
Discussion ForumsJump to Quoted PostQuote History
Quoted:


TL;DR



View Quote View All Quotes
View All Quotes
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Quoted:



Too long; didn't read (TL;DR)

Overly long unformatted statements present fellow editors a dilemma: spend excessive time parsing out what you mean or being mildly rude in not actually reading what you wrote. It is more collegial and collaborative to take an extra few moments to distill your thoughts into bite size pieces.

Traditionally, the phrase too long; didn't read (abbreviated tl;dr or simply tldr) has been used on the Internet as a reply to an excessively long statement. It indicates that the reader did not actually read the statement due to its undue length.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-2][2][/url] This essay especially considers the term as used in Wikipedia discussions, and examines methods of fixing the problem when found in article content.

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.

Contents



Reasons for length, good or bad

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.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-3][3][/url] 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 problems can be seen elsewhere.[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-4][4][/url]

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 to reduce the length of the work. If this process is stopped prematurely, the result is needlessly long (as shown by Pascal's quote). 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. His remark 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 may spur lengthy exposition, often to account for the corner cases.

A venerable aphorism is that "brevity is the soul of wit."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-5][5][/url] A similar sentiment advises would-be skilled writers to "omit needless words."[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-6][6][/url] 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 readers in comprehension. Many readers may not use English as a primary language or may have other "unarticulated needs".[url=http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read#cite_note-7][7][/url]

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 WP:Walls of text is frequently used to describe overlong, unformatted contributions.

Reducing wordiness

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

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.

Lastly, shear laziness or excessively concise may miss an important set of details necessary to include a well branched entry despite lacking the requisite patience. .

References[div style='list-style-type: decimal;']
  1. ^ Lettres Provinciales (1656-1657), no. 16.
  2. ^ "Too long didn't read". Urban Dictionary. Retrieved 2008-05-13.
  3. ^ "Study: Simple Writing Makes You Look Smart". Livescience.com. 2005-10-31. Retrieved 2012-04-13.
  4. ^ McCullagh, Declan. "FTC says current privacy laws aren't working," CNET News. June 22, 2010.
  5. ^ Shakespeare, William (1992). Hamlet. New York: Washington Square Press. p. 89. Act 2, Scene 2, line 90: "Therefore, since brevity is the soul of wit..."
  6. ^ Strunk, William (1918). "Elementary Principles of Composition". The Elements of Style. Bartleby.com. Retrieved 2008-05-13.
  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."
  8. ^ "Is 'Y' a Generation of entitled little shits". Pedestrian TV. 10 July 2013. Retrieved 15 July 2013.

External links

Tim Dowling, "Arfcom long-winded for you? Try the simple version," The Guardian,14 January 2008.

See also

{{Very long}} a.k.a. {{Tldr}}—Template used to flag articles or sections that need trimming.


TL;DR






Ditto.
Link Posted: 8/3/2013 8:51:48 AM EDT
[#25]
How about fify.
Link Posted: 8/3/2013 8:53:14 AM EDT
[#26]
Discussion ForumsJump to Quoted PostQuote History
Quoted:
How about fify.
View Quote


You're being called a small bitchy dog with curly hair.
Link Posted: 8/3/2013 8:55:42 AM EDT
[#27]
Discussion ForumsJump to Quoted PostQuote History
Quoted:
How about fify.
View Quote


2003 and you hadn't figured out "Fixed It For You"? You'll notice it usually follows a "correction".
Link Posted: 8/3/2013 9:02:18 AM EDT
[#28]
By the way. Years ago when I started seeing this symbol <3 on the intertubes I misinterpreted it as meaning "teabag".


In retrospect, it's obvious I was a dolt for not figuring it out sooner, but it really put some interesting spin on most internet conversations.
Link Posted: 8/3/2013 9:02:51 AM EDT
[#29]
Link Posted: 8/3/2013 9:03:36 AM EDT
[#30]
I thought "Too long didnt read" was easier just to say "Cliff notes".
Link Posted: 8/3/2013 9:05:12 AM EDT
[#31]

Discussion ForumsJump to Quoted PostQuote History
Quoted:
2003 and you hadn't figured out "Fixed It For You"? You'll notice it usually follows a "correction".
View Quote View All Quotes
View All Quotes
Discussion ForumsJump to Quoted PostQuote History
Quoted:



Quoted:

How about fify.




2003 and you hadn't figured out "Fixed It For You"? You'll notice it usually follows a "correction".




Thanks.



 
Link Posted: 8/3/2013 9:05:16 AM EDT
[#32]
IIRC TL;DR is for the lazy YMMV
Link Posted: 8/3/2013 9:07:31 AM EDT
[#33]
Discussion ForumsJump to Quoted PostQuote History


Fuckin GD is on a roll today!
 
Link Posted: 8/3/2013 9:10:48 AM EDT
[#34]
Discussion ForumsJump to Quoted PostQuote History
Quoted:
IIRC TL;DR is for the lazy YMMV
View Quote


QFT
Link Posted: 8/3/2013 9:12:01 AM EDT
[#35]
Discussion ForumsJump to Quoted PostQuote History
Quoted:


Now I wil no longer read it as "too long, didn't read"

Posted Via AR15.Com Mobile
View Quote View All Quotes
View All Quotes
Discussion ForumsJump to Quoted PostQuote History
Quoted:
Quoted:

Twat licked; dick ready.



Now I wil no longer read it as "too long, didn't read"

Posted Via AR15.Com Mobile



LOL, same same.
Link Posted: 8/3/2013 9:16:17 AM EDT
[#36]
Discussion ForumsJump to Quoted PostQuote History
Quoted:

Twat licked; dick ready.

View Quote


Comments like that are the reason I come to this place
Close Join Our Mail List to Stay Up To Date! Win a FREE Membership!

Sign up for the ARFCOM weekly newsletter and be entered to win a free ARFCOM membership. One new winner* is announced every week!

You will receive an email every Friday morning featuring the latest chatter from the hottest topics, breaking news surrounding legislation, as well as exclusive deals only available to ARFCOM email subscribers.


By signing up you agree to our User Agreement. *Must have a registered ARFCOM account to win.
Top Top