Considering the drawbacks of speed-reading (it's not just "reading, but faster") are really counter-productive in programming, I don't think actual speed-readin

Considering the drawbacks of speed-reading (it's not just "reading, but faster") are really counter-productive in programming, I don't think actual speed-reading techniques are helpful when reading code. I certainly do find myself "skimming" code in larger code bases but then I'm also not speed-reading but simply looking at the visual structure (which is where consistent formatting matters) and looking at words in fixed locations (e.g. names in function definitions). When you actually have to read code (rather than just skim it by looking at structure and words in fixed locations) that usually means you need to focus and carefully follow each expression -- the bottleneck in this case is comprehension, not reading speed (unless you have to keep track of each character, such as when dealing with short and confusing variable names or intentionally obfuscated code).