“A large fraction of the flaws in software development are due to programmers not fully understanding all the possible states their code may execute in.”

Quoted in "Functional programming in C++" http://gamasutra.com/view/news/169296/Indepth_Functional_programming_in_C.php

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "A large fraction of the flaws in software development are due to programmers not fully understanding all the possible s…" by John D. Carmack?

John D. Carmack31

American computer programmer, engineer, and businessman 1970

Related quotes

“The programmers who write improvements to GCC (or Emacs, or Bash, or Linŭ, or any GPL-covered program) are often employed by companies or universities. When the programmer wants to return his improvements to the community, and see his code in the next release, the boss may say, "Hold on there — your code belongs to us! We don't want to share it; we have decided to turn your improved version into a proprietary software product."
Here the GNU GPL comes to the rescue. The programmer shows the boss that this proprietary software product would be copyright infringement, and the boss realizes that he has only two choices: release the new code as free software, or not at all. Almost always he lets the programmer do as he intended all along, and the code goes into the next release.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

1990s, Copyleft: Pragmatic Idealism (1998)

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”

Kent Beck (1961) software engineer

Source: Refactoring: Improving the Design of Existing Code, 1999, p. 15

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”

Martin Fowler (1963) British programmer

Source: Refactoring: Improving the Design of Existing Code, 1999, p. 15

“Creating a modeling language that is also an executable language has long been a goal of the software community. Many years ago, in 1968 to be exact, while working with software components to successfully develop a telecommunications system, we created a modeling language that was the forerunner to UML. To model components we used sequence diagrams, collaboration diagrams, and state transition diagrams (a combination of state charts and activity diagrams). Our modeling language then seamlessly translated the component models into code. Each code component was in its turn compiled into an executable component that was deployed in our computer system. The computer system was a component management system—thus we had "components all the way down."”

Stephen J. Mellor (1952) British computer scientist

Source: Executable Uml: A Foundation for Model-Driven Architecture, 2002, p. xxiii: Foreword.

“We may understand why the species of the same genus, or genera of the same family, resemble each other more nearly in their embryonic than in their more fully developed state, or how it is that”

Charles Lyell (1797–1875) British lawyer and geologist

Source: The Geological Evidences of the Antiquity of Man (1863), Ch.21, p. 415
Context: We may understand why the species of the same genus, or genera of the same family, resemble each other more nearly in their embryonic than in their more fully developed state, or how it is that in the eyes of most naturalists the structure of the embryo is even more important in classification than that of the adult, 'for the embryo is the animal in its less modified state, and in so far it reveals the structure of its progenitor. In two groups of animals, however much they may at present differ from each other in structure and habits, if they pass through the same or similar embryonic stages, we may feel assured that they have both descended from the same or nearly similar parents, and are therefore in that degree closely related. Thus community in embryonic structure reveals community of descent, however much the structure of the adult may have been modified.

“Software engineering concerns methods and techniques to develop large software systems. The engineering metaphor is used to emphasize a systematic approach to develop systems that satisfy organizational requirements and constraints.”

Hans van Vliet (1949) Dutch computer scientist

Source: Software Engineering: Principles and Practice, 2007, p. 2

“Computers and music are converging in a new era of digital Renaissance as more and more musicians such as will. i. am are learning how to code while an increasing number of software programmers are learning how to play music.”

Newton Lee American computer scientist

Digital Da Vinci: Computers in Music, 2014

“You see, some people have a talent for programming. At ten to thirteen years old, typically, they're fascinated, and if they use a program, they want to know: “How does it do this?” But when they ask the teacher, if it's proprietary, the teacher has to say: “I'm sorry, it's a secret, we can't find out.” Which means education is forbidden. A proprietary program is the enemy of the spirit of education. It's knowledge withheld, so it should not be tolerated in a school, even though there may be plenty of people in the school who don't care about programming, don't want to learn this. Still, because it's the enemy of the spirit of education, it shouldn't be there in the school.
But if the program is free, the teacher can explain what he knows, and then give out copies of the source code, saying: “Read it and you'll understand everything.” And those who are really fascinated, they will read it! And this gives them an opportunity to start to learn how to be good programmers.
To learn to be a good programmer, you'll need to recognize that certain ways of writing code, even if they make sense to you and they are correct, they're not good because other people will have trouble understanding them. Good code is clear code that others will have an easy time working on when they need to make further changes.
How do you learn to write good clear code? You do it by reading lots of code, and writing lots of code. Well, only free software offers the chance to read the code of large programs that we really use. And then you have to write lots of code, which means you have to write changes in large programs.
How do you learn to write good code for the large programs? You have to start small, which does not mean small program, oh no! The challenges of the code for large programs don't even begin to appear in small programs. So the way you start small at writing code for large programs is by writing small changes in large programs. And only free software gives you the chance to do that.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

A Free Digital Society - What Makes Digital Inclusion Good or Bad? http://www.gnu.org/philosophy/free-digital-society.html#education; Lecture at Sciences Po in Paris (19 October 2011)] <br class="br">2010s

“Bad programmers worry about the code. Good programmers worry about data structures and their relationships.”

Linus Torvalds (1969) Finnish-American software engineer and hacker

https://lwn.net/Articles/193245/

“I would dramatically reduce the safeguards for software — from the ordinary term of 95 years to an initial term of 5 years, renewable once. And I would extend that government-backed protection only if the author submitted a duplicate of the source code to be held in escrow while the work was protected. Once the copyright expired, that escrowed version would be publicly available from the copyright office.
Most programmers should like this change. No code lives for 10 years, and getting access to the source code of even orphaned software projects would benefit all. More important, it would unlock the knowledge built into this protected code for others to build upon as they see fit. Software would thus be like every other creative work — open for others to see and to learn from.”

Lawrence Lessig (1961) American academic, political activist.

May the Source Be With You (2001)

“A large fraction of the flaws in software development are due to programmers not fully understanding all the possible states their code may execute in.”

Help us to complete the source, original and additional information

John D. Carmack31

Related quotes

Related topics