>"Strive to eliminate comments in your code."
>
>But Jeff give ample justification for what seems like an outrageous statement:
>
>"Comments indicate that code is not communicating clearly. As others have said, 'Comments are lies.' . . . If I have to explain a method, it's not simple enough."
>
>"Mehods should be a dozen lines or less. Scrolling is bad. . . . Code that forces scrolling might work fine for the fortunate few with photographic memory, but for the rest of us, it is a taxing exercise."

I like code that I can see in one "eyefull," so the scrolling issue hits home for me. I like to put an outline of a more complicated process (such as a list of 5 things to do to clean dirty data) at the top though. Then when the Document View window shows the list of methods their names are easily associated with the steps in the outline.

Also, if the method name and variable names are good enough, you can read the code and know what's going on. I really like long file names.