'geometry in code' james o. coplien columns: in space: the final frontier he is talking about how to find beauty in a code:

'... And of course Conway's Law says that you'll find the structure of the program mirrored in the structure of the organization that built it. Giving good space to objects gives good "space" to the programmers who maintain them: independence of development, local control.'

'... if one had to choose a type of entity of which it could be said that it is the only component, the essential and single component of all computer programs, what is it? Is it a function? Is it a list? Is it (probably) something else? Could one say that every successful program is a function of functions? Could one say that every successful program is a list of lists (lambda calculus)?'

'Data is about structure; instructions (control) are about time. The program counter visits instruction after instruction in turn. The locality of visitation (or lack thereof) sometimes leads to a spatial structure in its own right. Functions are locales of control. So are loops--chunks of time folded onto each other and expressed in compact form.'

'To Alexander, these issues of geometry aren't just about models of perception. To him, they grapple with the very structure of matter, with how the world really is. If I ask the analogous question for software, whether it really does live in some multi-dimensional world in the same sense that buildings do, they'll probably take away my license to do real work and suggest I go write poetry or something.'