Quotessence
Home / Authors / Edsger Dijkstra
Edsger Dijkstra

Edsger Dijkstra Quotes

Computer Scientist

Filter quotes by topic

AllProgrammingProgrammersComputerIfsProgramming LanguagesComputer ProgrammingProgramShouldThinkingLearningUseComputer LanguageComputer ScienceLanguagePeopleProblemDesignEleganceMathematicsMind

Famous Edsger Dijkstra Quotes

“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.”

ShouldReasonProcessSpaceLearningWiseMastersIntellectualProgramRelationSpreadLimitationEvolveProgrammingGapsProgrammersStaticCorrespondence
Author:Edsger Dijkstra
Create image

“Yes, I share your concern: how to program well -though a teachable topic- is hardly taught. The situation is similar to that in mathematics, where the explicit curriculum is confined to mathematical results; how to do mathematics is something the student must absorb by osmosis, so to speak. One reason for preferring symbol-manipulating, calculating arguments is that their design is much better teachable than the design of verbal/pictorial arguments. Large-scale introduction of courses on such calculational methodology, however, would encounter unsurmoutable political problems.”

WellsReasonProblemPoliticalCoursesSpeakResultsSituationLearningShareDesignStudentsTaughtConcernProgramArgumentMathematicsScalesSymbolsMathematicalEncountersProgrammingTopicsIntroductionConfinedCurriculumExplicitMethodologyCalculatingLarge ScalePictorialTeachableOsmosis
Author:Edsger Dijkstra
Create image

“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".”

PeopleIfsShouldWritingBookProcessSidesTermLinesNumbersProgramProductionsProductivityCodeProgrammingProgrammers
Author:Edsger Dijkstra
Create image