> You never watch output that goes by faster than you can read, unless you're actively watching movies through aalib or libcaca. This is not true for me. Duri

> You never watch output that goes by faster than you can read, unless you're actively watching movies through aalib or libcaca. This is not true for me. During development I often run programs that spew an enormous quantity of log output, and I'm watching to see if I notice a pattern in the output visually, or if it just looks normal. Either some critical or warning message in a different colour or boldface, or a shape to the messages that I'd recognise. Although in principle I could use various output filters, grep etc., sometimes that's effort and I'd rather just run the thing and have it run quickly. Also it's convenient to have all the output readily available if I do want to look at something that happened, as I can scroll to that place and look at pages of surrounding context in detail. If I use output filters, then I have to faff about re-running the program with different filters, or with all outputs enabled so I can step through everything around the event of interest. Admittedly sometimes its better to output to a file and search the file, but sometimes visual output at 60Hz works quite well. I have been known to skim manuals very fast as well. I guess in the era when man pages were everything, I got used to scrolling really fast to look for things of interest. It's interesting that a brain is able to recognise particular word-forms that flick by extremely fast, much faster than reading them. I've had people tell me they cannot do this, so I guess it's a learned skill.