Two thoughts:
- I agree with cat2014. There is a certain beauty to "Good abstraction, elegant algorithms, and well written code...". I would only add that the less 'cluttered' the code is, the more beautiful it is.
- "The map is not the terrain." I think I read this in a book about golf, but the idea applies here. Any 'picture' you want to draw of a program will not be complete. This applies, even if your medium is text. A program when read may or may not be the same program when run.
So, I don't think it can be done (i.e., how to lay out the code so that with a glance you can know everything about the program), nor that we need to. If you figure out how to do it, however, I'ld like to know the trick. :-)