As a technical writer, I think it’s important to understand speed reading and design for it when writing docs. I’m not saying that all developers are formalled

As a technical writer, I think it’s important to understand speed reading and design for it when writing docs. I’m not saying that all developers are formalled trained in and intentionally doing speed reading, but when you think about your own “information foraging” habits when browsing docs in order to get something done, you’ll find that your habits probably resemble speed reading a lot more than slow reading. At least in the initial phase, when you’re hunting for relevant information. In general, I’d say that speed reading is handy when you’re hunting for relevant information, and slow reading could be handy once you’re reasonably sure that you’ve found it. But up until that point, slow reading would be a waste of time (I.e. spending too much time on irrelevant information).