Our Intellectual Powers Are Rather Geared To Master Static Relations And That Our Powers To Visualize Processes Evolving In Time Are Relatively Poorly Developed. For That Reason We Should Do (as Wise Programmers Aware Of Our Limitations) Our Utmost To Shorten The Conceptual Gap Between The Static Program And The Dynamic Process, To Make The Correspondence Between The Program (spread Out In Text Space) And The Process (spread Out In Time) As Trivial As Possible.

-Edsger Dijkstra

Please Wait....
Translating....

Our Intellectual Powers Are Rather Geared To

Edsger Dijkstra

Our Intellectual Powers Are Rather Geared To Master Static Relations And That Our Powers To Visualize Processes Evolving In Time Are Relatively Poorly Developed. For That Reason We Should Do (as Wise Programmers Aware Of Our Limitations) Our Utmost To Shorten The Conceptual Gap Between The Static Program And The Dynamic Process, To Make The Correspondence Between The Program (spread Out In Text Space) And The Process (spread Out In Time) As Trivial As Possible.

Topic

Wise

Learning

Space

In This Respect A Program Is Like A Poem: You Cannot Write A Poem Without Writing It. Yet People Talk About Programming As If It Were A Production Process And Measure "programmer Productivity" In Terms Of "number Of Lines Of Code Produced". In So Doing They Book That Number On The Wrong Side Of The Ledger: We Should Always Refer To "the Number Of Lines Of Code Spent".

Book

Writing

Numbers