summary ;;Quote: programmers should have access to source code just as an auto mechanic can look at the engine

66 ;;Quote: a source-full environment, like Lisp, includes access to all functions; yet usually no access to operating system, compiler, or applications

67 ;;Quote: source code is the truth about a system; defines its worldview, underlying assumptions, and hidden limitations and strengths

67 ;;Quote: an abstract interface can not capture the essence of a program; due to an unbridgeable semantic gap

68 ;;Quote: source-sparse programs is like kitchen appliances with only vague labels to distinguish them

69 ;;Quote: programs are inevitably richer than their mathematical description; e.g., integer data type is not the same as a mathematical integer

69 ;;Quote: if we have complete source code then the correctness of a system is completely knowable

69 ;;Quote: an abstract interface is not a fact; it attempts to bridge a gap between two very different worlds

70 ;;Quote: complete source code substantially contributes to understanding a system and its place in our lives

70 ;;Quote: people are used to dealing with a rich and deceptive environment, e.g., driving on an expressway

70 ;;Quote: while comments may be incorrect they still provide useful information about program history and quality

71 ;;Quote: the first automobile manufacturers where secretive about their designs and methods; used unique screws and parts; eventually opened up

71 ;;Quote: access to source code does not violate information hiding because access is to people, not modules

73 ;;Quote: instead of researching abstract interfaces ought to study source code to find out what makes programs easier to reuse