I am still working on a good explanation. Here&#x27;s what I&#x27;ve come up with so far:<p>I have noticed every page I scroll causes a comprehension loss of around 90%, so in reading something that is 10 pagefuls long, I might only be able to reproduce a tiny part of the program.<p>I find not scrolling, and just moving my eyes, I rapidly absorb the program, and I find most bugs just by reading the code. This practice is absolutely impossible for me if I have to scroll very far and made difficult by scrolling at all.<p>A lot of J&#x2F;K&#x2F;Q&#x2F;KDB programmers do this because it is similar to APL, but I don&#x27;t have an APL background. I simply do not know how to do this except to write horizontally.<p>I learned a lot about this method by studying Arthur&#x27;s code (example[1]). He frequently recommends Iverson&#x27;s paper[2]. I just try to make every character count because it&#x27;s still taking up space.<p>Maybe keeping that in mind will help you read each word carefully -- maybe even out loud, if it helps.<p>[1]: <a href="http:&#x2F;&#x2F;www.nsl.com&#x2F;papers&#x2F;origins.htm" rel="nofollow">http:&#x2F;&#x2F;www.nsl.com&#x2F;papers&#x2F;origins.htm</a><p>[2]: <a href="http:&#x2F;&#x2F;www.jsoftware.com&#x2F;papers&#x2F;tot.htm" rel="nofollow">http:&#x2F;&#x2F;www.jsoftware.com&#x2F;papers&#x2F;tot.htm</a>