I visualize graphs sometimes or draw them on paper for particularly tricky pieces of code.
I was subvocalizing things to remember to do before learning to use task tracking software for that.
You might want to benchmark yourself e.g. with http://www.readingsoft.com/ (I ranked 398 wpm and I know my bottleneck is eye movements)
Also I think code reading speed is only a part of a larger process (e.g. code review or making a fix). For both of these external tools are available making reading speed not as important (iterative development / unit tests for fixing + static code analysis tools for reviews)
I was subvocalizing things to remember to do before learning to use task tracking software for that.
You might want to benchmark yourself e.g. with http://www.readingsoft.com/ (I ranked 398 wpm and I know my bottleneck is eye movements)
Also I think code reading speed is only a part of a larger process (e.g. code review or making a fix). For both of these external tools are available making reading speed not as important (iterative development / unit tests for fixing + static code analysis tools for reviews)