> Windows might not be trendy among developers, but it’s where accessibility works best. I don’t have to worry about whether I can get audio working reliably. The NVDA screen reader works on Windows and is free and open source, actively maintained, and designed by people who are screen reader users themselves.
> That said, I’m not actually developing on Windows in the traditional sense. WSL2 gives me a full Linux environment where I can run Docker containers, use familiar command-line tools, and run the same scripts and tools that my colleagues use. Windows is just the accessibility layer on top of my real development environment.
> I use VS Code. Microsoft has made accessibility a core engineering priority, treating accessibility bugs with the same urgency as bugs affecting visual rendering. The VS Code team regularly engages with screen reader users, and it shows in the experience.
His comments on VS Code reminds me of the quote "Good accessibility design is mostly just good design":
> Consistent keyboard shortcuts across all features, and the ability to jump to any part of the interface by keyboard
This is something I notice and appreciate about VS Code as a fully sighted person. Just like I appreciate slopped sidewalk cutouts when I'm walking with luggage.
A11y is a big commitment and cost, and of course not all a11y features benefit everyone equally, but it has a larger impact than most people realize.
MS has to make accessibility a priority because it's mandated by government (its customer).
Smaller companies would benefit from better libraries and design systems that make it easier to incorporate accessibility. Make accessible the default.
If you compare different languages, the speed people tend to speak (measured in syllables per second) varies significantly. However, the number of possible syllables also varies significantly. Once you account for that, the speed of speaking in terms of information is fairly consistent across languages.
I'm not aware of any specific research directly on point to what the author of the posted blog describes. But his hypothesis that having a consistent speaker reduces the cognitive overhead of decoding seems to be part of the story.
However, we would expect a similar effect in people who read, as the writing is also highly standardized. However, I've generally seen silent reading speads for English estimated at around 250. Getting up to 800 WPM puts you well within the realm of speed reading territory.
The relatively high structure of code and rote emails probably helps too.
I've been using Optimal Recognition Point (ORP) style apps (I use Balto Speed Reader) to comfortably read at 800wpm or more - for fact books and materials I can keep this up for quite some time - though for fiction I find it too fast to parse all the characters and tones of voice (https://www.researchgate.net/figure/Spritz-display-The-Optim... )
I was referring to how synthetic speech always talk in exactly the same way down to inflection and pauses whenever it encounters the same phrase, which isn't how people talk. So this helps a lot with comprehension. Structure of the content does help as well.
Great post. When you're reading a Mermaid diagram, do you just happen to have memorised that "dash dash greater than" means "arrow"? I assume the screen reader doesn't understand ASCII art.
And how painful is reading emails? HTML email is notoriously limited compared to HTML (and CSS) in the browser, but it's pretty hard to add structure to a plain text email too. How annoying is it when I do so using e.g. a "line" made out of repeated dashes?
The interesting part for me was that you can recognize synthetic voice much faster than human speech. Is there a specific voice you are using for 800wpm or it can be any TTS? Also, I think older voices sound more robotic that the newer ones (I mean pre AI, like the default on android is newer for me). Is there a difference for how fast you can listen to the newer more nicely sounding ones or the older more robotic ones?
Great article. I was of course surprised to learn that it's possible to learn to understand the super-fast TTS, since videos and podcasts start to get very tough to follow around 2.5x and higher. I've been wondering: surely better algorithms for generating high-speed speech are possible, especially as we have more and more compute around to throw at it. It's not easy to search for, since "speed" for most tools is about speed of generation rather than wpm. As normal-speed neural net TTS models get incredibly good, I am hoping to see more attention paid to the high-speed use case.
I was wondering what TTS voices you use? I've heard from other blind people that they tend to prefer the classic, robotic voices rather than modern ML-enhanced voices. Is that true in your experience, too?
After read about the poor scenario where the Linux accessibility tools is today (https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-d...), I was wondering: if maybe the developers start to use these accessibility tools to improve their speed reading (and productivity as well), this could also helps to prioritize the accessibility features and bug fixes in Gnome, KDE, Qt, etc.
This is really interesting. I wonder–would it be possible to listen to an audiobook or PDF at 800 wpm once one learns how to understand the screenreader "language"? Presumably the cognitive load would get heavy if the content were a stream of unstructured prose as opposed to code.
Yes, that is how I usually consume my content. Cognitive load is actually lower for unstructured prose compared to code, think about fiction for example. Code is much denser.
When I read to relax, it is for enjoyment, so I don't aim to read as fast as possible. This is why I still listen to human narrated audiobooks, since a good narrator adds to the experience.
I worked with a developer briefly who would produce code at an extremely high speed (this was before LLMs) and I've observed them write 50% of the code for two projects in the matter of a few days.
While I never got around to asking them how they coded so fast, this was probably one of the tools in their arsenal.
I can imagine it's practice and self-disciplilne; pick and know a language/tool instead of reinventing the wheel or doing research first, write like you've always written, do new projects in that same toolkit multiple times, and (self discipline), just get on with it.
I struggle with that tbh, every time I'm on a new project I get into a "beginner's mindset" and look up the basics for a tool again instead of trusting myself that I know enough and what I write will be good enough.
FYI in case you didn't read the article - it's not about LLM coding but about a blind software developer who uses a screenreader at 800wpm to read code. It's really astounding to hear how fast that is I recommend checking it out!
This gave me new perspective. Both on what's possible with our ears/cognition and what our eyes do for us (for example seeing the extra quote so easily). Appreciate this very much and Thank you for what you do Neurrone!
I'm getting intense deja vu reading this. I remember a very similar article from 3-5 years ago. Even the title feels like I've seen it before. I thought this was a repost from that one but I remember the previous post had a photo of the author's desk with a keyboard, desktop, and no monitor.
It looks like it's not the article you were looking for, but there was also this similar article about one of the original authors of NVDA, who hits 900 WPM, also including an audio sample: https://www.9news.com.au/national/the-secret-language-only-b...
For anyone wanting to trying this out on YouTube, select your video, open the Web Developer Tools with Ctrl+Shift+I, then type this (followed by a carriage-return):
document.getElementsByClassName("video-stream html5-main-video")[0].playbackRate = 5; // Or whatever speed you choose
ok, so you can understand the words at 800wpm...can you really comprehend what's being said? When I listen to youtube videos at 2x speed I can usually pick apart all the words just fine but I often have to slow it down to properly process the meaning behind those words.
I think it’s about different modes of operation. If I’m skimming an academic text, it’s not that I’m reading faster, I’m just jumping between text to find interesting keywords and sentences. A way to pick out raisins from the cookie.
When listening to a podcast or reading a book the pleasure is important, so I almost never speed up. If the pacing (or information density) is too low, I just don’t listen. On the contrary I’ve read books that are so dense I have to slow down and repeat. Those can be great works.
One mode is for navigation, one is for embedding the brain in the story, the knowledge, or whatever it is. It’s like looking out the window on a train, I’m not thinking ”wow I have seen these cows for 1.3 seconds, what a waste of time, I could have processed them in less than a second”.
Not to speak for the blind, but I assume an enormous utility need of navigating and structuring information from a linear medium into whatever is the representation in our brains.
It's a matter of practice and progression. I listen to podcasts and audiobooks in English at 3x speed, but it took me maybe 2-3 years to get to this level.
I understand all casual and technical content just fine. The only thing tripping me is fiction where I struggle with character names that I don't know how to spell (my visual memory needs it!). That's an English-only problem though. I don't have any of those issues with content in my native language (Bulgarian).
I don't know exactly what top speeds I used, above 2.5x, under 5x, but I listened to some lectures on youtube as a background process to doing some work. I would be sure I have missed something, as I worked so I had this practice of just setting the video time back and checking if it is stuff that I already know. I was amazed to see that mostly all data was retained already and I had the feeling of listening to the same stuff twice.
These speeds were already non-comprehensive to my colleagues, but I thought there is no point in trying to get used to higher speeds, and to see the author processing these kinds of flows of data is just inspiring and amazing, Ill try to get better. But I am not planing on listening to code :D
I adjust its speed based on cognitive load. For routine tasks like reading emails, documentation, or familiar code patterns, 800 WPM works perfectly and allows me to process information far faster than one can usually read. I’m not working to understand what the screen reader is saying, so I can focus entirely on processing the meaning of the content. However, I slow down a little when debugging complex logic or working through denser material. At that point, the limiting factor isn’t how fast I can hear the words but how quickly I can understand their meaning.
I can read at speeds higher than 800wpm and comprehend everything. It's about practice. Although, yes, simpler material is easier to read at higher speeds.
i've always wondered about the possibility of hybrid visual-audio interfaces for sighted users. a screen reader producing lots of words at the same time that you're looking around the screen—perhaps the visual ui would have to privilege symbols over words, to not force you to perform two language processing tasks at once
Just FYI OP (assuming OP is the author of the post) there's no margin on your blog. Text goes all the way to the edges.
As a related sidenote, I wonder how quickly ChatGPT replaces much of the customized tools here? ChatGPT is probably pretty proficient at being able to describe the contents of eg a screenshare, or a screenshot of a website.
thunderbong|7 months ago
> Windows might not be trendy among developers, but it’s where accessibility works best. I don’t have to worry about whether I can get audio working reliably. The NVDA screen reader works on Windows and is free and open source, actively maintained, and designed by people who are screen reader users themselves.
> That said, I’m not actually developing on Windows in the traditional sense. WSL2 gives me a full Linux environment where I can run Docker containers, use familiar command-line tools, and run the same scripts and tools that my colleagues use. Windows is just the accessibility layer on top of my real development environment.
> I use VS Code. Microsoft has made accessibility a core engineering priority, treating accessibility bugs with the same urgency as bugs affecting visual rendering. The VS Code team regularly engages with screen reader users, and it shows in the experience.
mbb70|7 months ago
> Consistent keyboard shortcuts across all features, and the ability to jump to any part of the interface by keyboard
This is something I notice and appreciate about VS Code as a fully sighted person. Just like I appreciate slopped sidewalk cutouts when I'm walking with luggage.
A11y is a big commitment and cost, and of course not all a11y features benefit everyone equally, but it has a larger impact than most people realize.
esafak|7 months ago
Smaller companies would benefit from better libraries and design systems that make it easier to incorporate accessibility. Make accessible the default.
gizmo686|7 months ago
If you compare different languages, the speed people tend to speak (measured in syllables per second) varies significantly. However, the number of possible syllables also varies significantly. Once you account for that, the speed of speaking in terms of information is fairly consistent across languages.
I'm not aware of any specific research directly on point to what the author of the posted blog describes. But his hypothesis that having a consistent speaker reduces the cognitive overhead of decoding seems to be part of the story.
However, we would expect a similar effect in people who read, as the writing is also highly standardized. However, I've generally seen silent reading speads for English estimated at around 250. Getting up to 800 WPM puts you well within the realm of speed reading territory.
The relatively high structure of code and rote emails probably helps too.
ljf|7 months ago
Neurrone|7 months ago
poulpy123|7 months ago
Fokamul|7 months ago
"I use my computer during natural pauses in the conversation or presentation."
Casually dropping that everyone is speaking so slow. That you must use the time between sentences for something meaningful, pretty funny. :-)
Neurrone|7 months ago
Didn't mean it that way . But that is truly the only way that I can use the computer while in a meeting.
Neurrone|7 months ago
Happy to answer any questions.
Vinnl|7 months ago
And how painful is reading emails? HTML email is notoriously limited compared to HTML (and CSS) in the browser, but it's pretty hard to add structure to a plain text email too. How annoying is it when I do so using e.g. a "line" made out of repeated dashes?
c6401|7 months ago
The interesting part for me was that you can recognize synthetic voice much faster than human speech. Is there a specific voice you are using for 800wpm or it can be any TTS? Also, I think older voices sound more robotic that the newer ones (I mean pre AI, like the default on android is newer for me). Is there a difference for how fast you can listen to the newer more nicely sounding ones or the older more robotic ones?
dcre|7 months ago
xiande04|7 months ago
I was wondering what TTS voices you use? I've heard from other blind people that they tend to prefer the classic, robotic voices rather than modern ML-enhanced voices. Is that true in your experience, too?
dherikb|7 months ago
After read about the poor scenario where the Linux accessibility tools is today (https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-d...), I was wondering: if maybe the developers start to use these accessibility tools to improve their speed reading (and productivity as well), this could also helps to prioritize the accessibility features and bug fixes in Gnome, KDE, Qt, etc.
ray__|7 months ago
Neurrone|7 months ago
When I read to relax, it is for enjoyment, so I don't aim to read as fast as possible. This is why I still listen to human narrated audiobooks, since a good narrator adds to the experience.
supriyo-biswas|7 months ago
While I never got around to asking them how they coded so fast, this was probably one of the tools in their arsenal.
Cthulhu_|7 months ago
I struggle with that tbh, every time I'm on a new project I get into a "beginner's mindset" and look up the basics for a tool again instead of trusting myself that I know enough and what I write will be good enough.
elevaet|7 months ago
narmiouh|7 months ago
Neurrone|7 months ago
ferfumarma|7 months ago
There were browser extensions that would present web content at 800 WPM, and they were fantastic. I wish they hadn't disappeared.
mtlynch|7 months ago
I tried searching algolia, but I can't find it.
Ndymium|7 months ago
Sadly the audio samples are gone. I'll need to pester someone to fix that.
Vinnl|7 months ago
spyrja|7 months ago
markasoftware|7 months ago
klabb3|7 months ago
When listening to a podcast or reading a book the pleasure is important, so I almost never speed up. If the pacing (or information density) is too low, I just don’t listen. On the contrary I’ve read books that are so dense I have to slow down and repeat. Those can be great works.
One mode is for navigation, one is for embedding the brain in the story, the knowledge, or whatever it is. It’s like looking out the window on a train, I’m not thinking ”wow I have seen these cows for 1.3 seconds, what a waste of time, I could have processed them in less than a second”.
Not to speak for the blind, but I assume an enormous utility need of navigating and structuring information from a linear medium into whatever is the representation in our brains.
photios|7 months ago
I understand all casual and technical content just fine. The only thing tripping me is fiction where I struggle with character names that I don't know how to spell (my visual memory needs it!). That's an English-only problem though. I don't have any of those issues with content in my native language (Bulgarian).
brna-2|7 months ago
These speeds were already non-comprehensive to my colleagues, but I thought there is no point in trying to get used to higher speeds, and to see the author processing these kinds of flows of data is just inspiring and amazing, Ill try to get better. But I am not planing on listening to code :D
smusamashah|7 months ago
precompute|7 months ago
nottorp|7 months ago
Tbh even closing your eyes should.
raincole|7 months ago
thewileyone|7 months ago
evertedsphere|7 months ago
imagine the bandwidth
Unirely01|7 months ago
[deleted]
collectedparts|7 months ago
As a related sidenote, I wonder how quickly ChatGPT replaces much of the customized tools here? ChatGPT is probably pretty proficient at being able to describe the contents of eg a screenshare, or a screenshot of a website.
Neurrone|7 months ago
I didn't post this onto HN, so I only just found out about this thread.
Thanks for mentioning the margin issue, I've tried fixing it now. Let me know if its still an issue.
> I wonder how quickly ChatGPT replaces much of the customized tools here?
Probably not many. It is prone to Hallucinations, and the latency involved for getting a response means that I only use it when I have to.