Alan Perlis quotes
From Motley Bytes Wiki
Alan Jay Perlis. (1922 - 1990). American computer scientist, software engineer, educator, ACM Turing award recipient.
Contents
- 1 Fit and Try
- 2 Simulation Becomes System
- 3 Iterative Simulation Design
- 4 Human Communication Limits
- 5 Software Engineering Competence
- 6 Useful Software Systems
- 7 First Software Engineering Conference
- 8 Training
- 9 Program Parts Recurse
- 10 Understanding Code
- 11 Understanding Programs
- 12 Reading Programs
- 13 Program Sameness
- 14 Program Purpose
- 15 Listening
- 16 Programming Language
- 17 Modularity
- 18 Optimization
- 19 Command Language
- 20 Complex Information in the Mind
- 21 Programming Special Cases
- 22 Simplicity Follows Complexity
- 23 Ingenuity and Analysis
- 24 Programming the Excluded Muddle
- 25 Error-Free Programs
- 26 Ideas and the Semantic Gulf
- 27 Specifications
- 28 Complexity
- 29 Parameters
- 30 God and AI
- 31 Programming Language Wish
- 32 Responsible Ideas
- 33 Failure and Success
- 34 Formal
- 35 Complexity Communication
- 36 Neuroscience, Psychology, and Software
- 37 Unnatural Natural Language
- 38 Programming Impossible for Most
- 39 Learning Knowledge and Programming
- 40 Programming Education
- 41 Programming Unnatural
- 42 Simplicity Gets in the Way
- 43 Computing Fun
- 44 Knowledge and Wisdom
- 45 Balance Efficiency and Generality
Fit and Try
“Fundamentally, the procedure you mention, which is ‘fit-and-try’, will work very well with three or four people. If you have a hundred people the ‘fit-and-try’ process diverges because of lack of control.”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 29.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Fit_and_Try
Simulation Becomes System
“The critical point is that the simulation becomes the system.”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 31.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Simulation_Becomes_System
Iterative Simulation Design
“1. A software system can best be designed if the testing is interlaced with the designing instead of being used after the design.
2. A simulation which matches the requirements contains the control which organizes the design of the system.
3. Through successive repetitions of this process of interlaced testing and design the model ultimately becomes the software system itself.
I think that it is the key of the approach that has been suggested, that there is no such question as testing things after the fact with simulation models, but that in effect the testing and the replacement of simulations with modules that are deeper and more detailed goes on with the simulation model controlling, as it were, the place and order in which these things are done.”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 32.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Iterative_Simulation_Design
- Keywords: Software_quotes System_quotes Design_quotes Process_quotes Interlace_quotes Testing_quotes Usage_quotes Simulation_quotes Match_quotes Requirements_quotes Control_quotes Organize_quotes Repetition_quotes Iteration_quotes Model_quotes Key_quotes Approach_quotes Suggestion_quotes Question_quotes After_quotes Fact_quotes Effect_quotes Replace_quotes Module_quotes Deep_quotes Detail_quotes Order_quotes Place_quotes Do_quotes Ultimate_quotes
Human Communication Limits
“A man can communicate with about five colleagues on a software project without too much difficulty. Likewise he can supervise about five people and know pretty well what they are doing. One would structure 120 people in three levels, in which no man is talking to more than about eight people, both across his level and up and down”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 51.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Human_Communication_Limits
Software Engineering Competence
“It is a fact that there are software engineers around today who are quite competent. There are systems in many places which are quite stable and which provide magnificent service. It is also the case that there are large numbers of efforts, containing large numbers of programs and programmers, which have no software engineers on them, that is that people function as though they did not know how to build software.”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 73.
- Note: Un-indexed continuation of quote: “I have a number of questions: 1. Is it possible to have software engineers in the numbers in which we need them, without formal software engineering education? 2. Is software engineering the same as Computer Science? 3. Is software engineering best provided by baccalaureate programs in universities? Or by adult education courses? Or by two year courses following the standard grade school education? 4. Do the people educated in these programs have a growing and future role in our society? 5. Will they be useful enough in a firm or government or university, and is their value such that they can distribute their talents in other activities, or must they always remain programmers? 6. What curriculum do we have in mind for software engineers, regardless of what level we choose to educate them? 7. Is software engineering really different from what we now call systems engineering?”
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Software_Engineering_Competence
- Keywords: Fact_quotes Software_Engineering_quotes Competence_quotes System_quotes Place_quotes Stable_quotes Provide_quotes Magnificent_quotes Service_quotes Effort_quotes Large_quotesProgram_quotes Programmer_quotes People_quotes Knowledge_quotes Build_quotes Software_quotes Development_quotes Engineering_quotes
Useful Software Systems
“We recognize that a practical problem of considerable difficulty and importance has arisen: The successful design, production and maintenance of useful software systems. The importance is obvious and the more so since we see only greater growth in demands and requirements in the future. The consequences of poor performance, poor design, instability and mismatching of promise and performance are not going to be limited to the computing fraternity, or even their nearest neighbors, but will affect considerable sections of our society whose ability to forgive is inversely proportional to their ignorance of the difficulties we face. The source of difficulty is distributed through the whole problem, easy to identify, and yet its cure is hard to pinpoint so that systematic improvement can be gotten.”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 78, Keynote address.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Useful_Software_Systems
- Keywords: Usefulness_quotes Practical_quotes Problem_quotes Difficulty_quotes Importance_quotes Arise_quotes Success_quotes Design_quotes Production_quotes Maintain_quotes Software_quotes System_quotes Obvious_quotes Great_quotes Growth_quotes Demand_quotes Requirements_quotes Consequence_quotes Poor_quotes Performance_quotes Instability_quotes Mismatch_quotes Promise_quotes Go_quotes Limitation_quotes Computing_quotes Fraternity_quotes Near_quotes Neighbor_quotes Affect_quotes Considerable_quotes Section_quotes Society_quotes Ability_quotes Forgiveness_quotes Inverse_quotes Proportion_quotes Ignorance_quotes Face_quotes Source_quotes Distributed_quotes Easy_quotes Identify_quotes Cure_quotes Hard_quotes Pinpoint_quotes Improve_quotes
First Software Engineering Conference
“This is the first conference ever held on software engineering and it behooves us to take this conference quite seriously since it will likely set the tone of future work in this field”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 79, Keynote address.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/First_Software_Engineering_Conference
Training
“Our problems arise from demands, appetites, and our exuberant optimism. They are magnified by the unevenly trained personnel with which we work. In our deliberations we will not, I believe, be able to avoid the education problem — software engineering does not exist without software engineers.”
- Source: Alan Jay Perlis in a report entitled Software Engineering: Report of a Conference Sponsored by the NATO Science Committee. Chaired by Friedrich Ludwig Bauer. Edited by P. Naur; B. Randell. Conference held 1968-10-07 through 1968-10-11 in Garmisch, Germany. OCLC: 35337842. See http://homepages.cs.ncl.ac.uk/brian.randell/NATO/index.html ; http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF ; https://dl.acm.org/citation.cfm?id=1102020 ; https://books.google.com/books/about/Software_engineering.html?id=Uc9QAAAAYAAJ . Page 79, Keynote address.
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Training
- Keywords: Problem_quotes Arise_quotes Demand_quotes Appetite_quotes Exuberant_quotes Magnify_quotes Uneven_quotes Training_quotes Personnel_quotes Work_quotes Deliberation_quotes Belief_quotes Avoidance_quotes Education_quotes Software_Engineering_quotes Optimism_quotes Engineering_quotes Engineer_quotes Software_quotes
Program Parts Recurse
“Every program is a part of some other program...”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Program_Parts_Recurse
Understanding Code
“It is easier to write an incorrect program than understand a correct one.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Understanding_Code
Understanding Programs
“To understand a program you must become both the machine and the program.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Understanding_Programs
Reading Programs
“Perhaps if we wrote programs from childhood on, as adults we'd be able to read them.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Reading_Programs
Program Sameness
“If two people write exactly the same program, each should be put in microcode and then they certainly won't be the same.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Program_Sameness
Program Purpose
“Every program has (at least) two purposes: the one for which it was written and another for which it wasn't.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Program_Purpose
Listening
“If a listener nods his head when you're explaining your program, wake him up.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Listening
Programming Language
“A language that doesn't affect the way you think about programming, is not worth knowing.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_Language
Modularity
“Wherever there is modularity there is the potential for misunderstanding: Hiding information implies a need to check communication.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Modularity
Optimization
“Optimization hinders evolution.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Optimization
- Keywords: Optimization_quotes Hinder_quotes Evolution_quotes
Command Language
“A good system can't have a weak command language.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Command_Language
Complex Information in the Mind
“One can only display complex information in the mind. Like seeing, movement or flow or alteration of view is more important than the static picture, no matter how lovely.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Complex_Information_in_the_Mind
Programming Special Cases
“In programming, everything we do is a special case of something more general - and often we know it too quickly.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_Special_Cases
Simplicity Follows Complexity
“Simplicity does not precede complexity, but follows it.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Simplicity_Follows_Complexity
Ingenuity and Analysis
“Programmers are not to be measured by their ingenuity and their logic but by the completeness of their case analysis.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Ingenuity_and_Analysis
Programming the Excluded Muddle
“Structured Programming supports the law of the excluded muddle.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_the_Excluded_Muddle
Error-Free Programs
“There are two ways to write error-free programs; only the third one works.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Error-Free_Programs
Ideas and the Semantic Gulf
“So many good ideas are never heard from again once they embark in a voyage on the semantic gulf.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Ideas_and_the_Semantic_Gulf
Specifications
“It is easier to change the specification to fit the program than vice versa.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Specifications
Complexity
“Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Complexity
Parameters
“It is the user who should parametrize procedures, not their creators.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Parameters
God and AI
“A year spent in artificial intelligence is enough to make one believe in God.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/God_and_AI
Programming Language Wish
“When someone says ‘I want a programming language in which I need only say what I wish done,’ give him a lollipop.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_Language_Wish
Responsible Ideas
“Don't have good ideas if you aren't willing to be responsible for them.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Responsible_Ideas
Failure and Success
“Dealing with failure is easy: Work hard to improve. Success is also easy to handle: You've solved the wrong problem. Work hard to improve.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Failure_and_Success
Formal
“One can't proceed from the informal to the formal by formal means.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Formal
Complexity Communication
“You can't communicate complexity, only an awareness of it.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Complexity_Communication
Neuroscience, Psychology, and Software
“The only constructive theory connecting neuroscience and psychology will arise from the study of software.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Neuroscience_Psychology_and_Software
Unnatural Natural Language
“Within a computer natural language is unnatural.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Unnatural_Natural_Language
Programming Impossible for Most
Most people find the concept of programming obvious, but the doing impossible.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_Impossible_for_Most
Learning Knowledge and Programming
“You think you know when you learn, are more sure when you can write, even more when you can teach, but certain when you can program.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Learning_Knowledge_and_Programming
Programming Education
“It goes against the grain of modern education to teach children to program. What fun is there in making plans, acquiring discipline in organizing thoughts, devoting attention to detail and learning to be self-critical?”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_Education
Programming Unnatural
“Programming is an unnatural act.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Programming_Unnatural
- Keywords: Programming_quotes Unnatural_quotes Action_quotes
Simplicity Gets in the Way
“In seeking the unattainable, simplicity only gets in the way. If there are epigrams, there must be meta-epigrams.”
- Source: Perlis, A. J. (1982). Special Feature: Epigrams on programming. ACM SIGPLAN Notices, 17(9), 7–13. http://doi.org/10.1145/947955.1083808
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Simplicity_Gets_in_the_Way
Computing Fun
“I think that it's extraordinarily important that we in computer science keep fun in computing. When it started out, it was an awful lot of fun. Of course, the paying customers got shafted every now and then, and after a while we began to take their complaints seriously. We began to feel as if we really were responsible for the successful, error-free perfect use of these machines. I don't think we are. I think we're responsible for stretching them, setting them off in new directions, and keeping fun in the house. I hope the field of computer science never loses its sense of fun. Above all, I hope we don't become missionaries. Don't feel as if you're Bible salesmen. The world has too many of those already. What you know about computing other people will learn. Don't feel as if the key to successful computing is only in your hands. What's in your hands, I think and hope, is intelligence: the ability to see the machine as more than when you were first led up to it, that you can make it more.”
- Source: Quoted in The Structure and Interpretation of Computer Programs by Hal Abelson, Gerald Jay Sussman and Julie Sussman (McGraw-Hill, 2nd edition, 1996).
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Computing_Fun
- Keywords: Thinking_quotes Importance_quotes Computer_Science_quotes Computing_quotes Fun_quotes Pay_quotes Customer_quotes Shaft_quotes Complaint_quotes Serious_quotes Responsibility_quotes Success_quotes Error_quotes Error-Free_quotes Perfect_quotes Machine_quotes Quality_quotes Defect_quotes Stretch_quotes Innovation_quotes New_quotes Direction_quotes House_quotes Field_quotes Loss_quotes Sense_quotes Missionary_quotes Evangelism_quotes Bible_quotes Salesman_quotes World_quotes Knowledge_quotes Learning_quotes Feel_quotes Key_quotes Hand_quotes Intelligence_quotes Ability_quotes Sight_quotes First_quotes Extraordinary_quotes Science_quotes Learn_quotes
Knowledge and Wisdom
“Both knowledge and wisdom extend man's reach. Knowledge led to computers, wisdom to chopsticks.”
- Source: Perlis, A. J. (1966). The Synthesis of Algorithmic Systems. In ACM Turing award lectures Year Awarded 1966. http://doi.org/10.1145/1283920.1283921
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Knowledge_and_Wisdom
Balance Efficiency and Generality
“Our progress, then, is measured by the balance we achieve between efficiency and generality. As the nature of our involvement with computation changes — and it does — the appropriate description of language changes; our emphasis shifts. I feel that our successor model will show such a change. Computer science is a restless infant and its progress depends as much on shifts in point of view as on the orderly development of our current concepts.”
- Source: Perlis, A. J. (1966). The Synthesis of Algorithmic Systems. In ACM Turing award lectures Year Awarded 1966. http://doi.org/10.1145/1283920.1283921
- See Also:
- Alan_Perlis_quotes
- Alan_Perlis_quotes/Balance_Efficiency_and_Generality
- Keywords: Progress_quotes Measurement_quotes Balance_quotes Achievement_quotes Efficiency_quotes Generality_quotes Nature_quotes Involve_quotes Computation_quotes Change_quotes Appropriate_quotes Description_quotes Language_quotes Emphasis_quotes Shift_quotes Feel_quotes Successor_quotes Model_quotes Show_quotes Computer_Science_quotes Restless_quotes Infant_quotes Dependence_quotes Point_of_View_quotes Perspective_quotes Order_quotes Development_quotes Current_quotes Conceptual_quotes Science_quotes