4 ms·

How to spot the guy that didn't read the article.

by akuji1993 9y ago

ringaroundthetx 9y ago
I skimmed Skimmed really fast looking for something related to the title
- lsc 9y ago
  It's interesting; none of the 'speed reading' wisdom has worked for me. When I 'skim' I seem to be way slower than most people who 'skim' - even though I'm quite competitive when 'reading' - but I also seem to usually have some idea of what the text was about, while I find it is quite common for people skimming to not have absorbed much at all from the text. That's interesting too, because I find that in 'reading' my reading comprehension is not better if you compare me to others who have the level of education implied by my profession. When I skim, my focus is on reading faster, pushing myself through the document, and I let my unconscious deal with what information is dropped. It does move things along much faster than 'reading' at regular speed, and it does lower comprehension, but it does these things in a sort of incremental way. Most of the time when I've read about 'speed reading' it talks a lot about consciously managing that information drop, and managing where your eyes go, which for me, slows me down quite a lot, and usually ends up making my retention all but useless.
OtterCoder 9y ago
It's a disingenuous title. The article is cool, but not what I was lead to believe.
- freehunter 9y ago
  It really is. There is nothing "software development" about the speed of his text-to-speech other than he uses it for reading code in addition to reading normal sentences. The more accurate title would be "Software developer reads at 450WPM". Still interesting enough to get people to click to find out how, but "development at 450wpm" really really does sound like he's typing at 450wpm. Reading code is not "software development", and reading is all he does at 450wpm.
  - OtterCoder 9y ago
    A very skilled reader can read text at around 400wpm with good comprehension, so I can believe he can listen to code at those speeds. A professional typist is somewhere around 80wpm, and a stenographer can reach up to 250wpm. 450 would have to represent an enormous innovation in typing methods. Frankly, even if you could, 450wpm would be an irresponsible speed to code at. As mediocre as my own typing speed is, it's never the limiting factor when I code. There's just too much to consider.

How to spot the guy that didn't read the article.

ringaroundthetx 9y ago

I skimmed Skimmed really fast looking for something related to the title

lsc 9y ago
It's interesting; none of the 'speed reading' wisdom has worked for me. When I 'skim' I seem to be way slower than most people who 'skim' - even though I'm quite competitive when 'reading' - but I also seem to usually have some idea of what the text was about, while I find it is quite common for people skimming to not have absorbed much at all from the text. That's interesting too, because I find that in 'reading' my reading comprehension is not better if you compare me to others who have the level of education implied by my profession. When I skim, my focus is on reading faster, pushing myself through the document, and I let my unconscious deal with what information is dropped. It does move things along much faster than 'reading' at regular speed, and it does lower comprehension, but it does these things in a sort of incremental way. Most of the time when I've read about 'speed reading' it talks a lot about consciously managing that information drop, and managing where your eyes go, which for me, slows me down quite a lot, and usually ends up making my retention all but useless.

OtterCoder 9y ago

It's a disingenuous title. The article is cool, but not what I was lead to believe.

freehunter 9y ago
It really is. There is nothing "software development" about the speed of his text-to-speech other than he uses it for reading code in addition to reading normal sentences. The more accurate title would be "Software developer reads at 450WPM". Still interesting enough to get people to click to find out how, but "development at 450wpm" really really does sound like he's typing at 450wpm. Reading code is not "software development", and reading is all he does at 450wpm.
- OtterCoder 9y ago
  A very skilled reader can read text at around 400wpm with good comprehension, so I can believe he can listen to code at those speeds. A professional typist is somewhere around 80wpm, and a stenographer can reach up to 250wpm. 450 would have to represent an enormous innovation in typing methods. Frankly, even if you could, 450wpm would be an irresponsible speed to code at. As mediocre as my own typing speed is, it's never the limiting factor when I code. There's just too much to consider.