“The best way to prepare [to be a programmer] is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and fished out listings of their operating system.”

—  Bill Gates

Interview from Programmers at Work (1986)

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 "The best way to prepare [to be a programmer] is to write programs, and to study great programs that other people have w…" by Bill Gates?
Bill Gates photo
Bill Gates 92
American business magnate and philanthropist 1955

Related quotes

John Backus photo

“Much of my work has come from being lazy. I didn't like writing programs, and so, when I was working on the IBM 701 (an early computer), writing programs for computing missile trajectories, I started work on a programming system to make it easier to write programs.”

John Backus (1924–2007) American computer scientist

Quoted in the IBM employee magazine Think in 1979. Cited by his Associated Press obituary http://www.msnbc.msn.com/id/17704662/

Linus Torvalds photo

“To kind of explain what Linux is, you have to explain what an operating system is. And the thing about an operating system is that you're never ever supposed to see it. Because nobody really uses an operating system; people use programs on their computer. And the only mission in life of an operating system is to help those programs run. So an operating system never does anything on its own; it's only waiting for the programs to ask for certain resources, or ask for a certain file on the disk, or ask to connect to the outside world. And then the operating system steps in and tries to make it easy for people to write programs.”

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

Interview in Revolution OS http://www.imdb.com/title/tt0308808/, documentary, 2001.
2000s, 2000-04

“I like the observation that Forth is an amplifier: a good programmer can write a great program; a bad programmer a terrible one. I feel no need to cater to bad programmers.”

Charles H. Moore

Quoted in Naomi Hamilton, "The A-Z of Programming Languages: Forth," http://www.computerworld.com.au/index.php/id;766897508 Computerworld (2008-06-27)

Richard Stallman photo

“I have met bright students in computer science who have never seen the source code of a large program. They may be good at writing small programs, but they can't begin to learn the different skills of writing large ones if they can't see how others have done it.
In any intellectual field, one can reach greater heights by standing on the shoulders of others. But that is no longer generally allowed in the software field—you can only stand on the shoulders of the other people in your own company.”

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

Why Software Should Be Free (1991) http://www.gnu.org/philosophy/shouldbefree.html
1990s

“Computer science is still a young field. The first computers were built in the mid 1940s, since when the field has developed tremendously. Applications from the early years of computerization can be characterized as follows: the programs were quite small, certainly when compared to those that are currently being constructed; they were written by one person; they were written and used by experts in the application area concerned. The problems to be solved were mostly of a technical nature, and the emphasis was on expressing known algorithms efficiently in some programming language. Input typically consisted of numerical data, read from such media as punched tape or punched cards. The output, also numeric, was printed on paper. Programs were run off-line. If the program contained errors, the programmer studied an octal or hexadecimal dump of memory. Sometimes, the execution of the program would be followed by binary reading machine registers at the console.”

Hans van Vliet (1949) Dutch computer scientist

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

“We have come through a strange cycle in programming, starting with the creation of programming itself as a human activity. Executives with the tiniest smattering of knowledge assume that anyone can write a program, and only now are programmers beginning to win their battle for recognition as true professionals.”

Gerald M. Weinberg (1933–2018) American computer scientist

Cited in: Michael Jay Quinn (2006) Ethics for the information age. p. 415
The Psychology of Computer Programming, 1971

Richard Dawkins photo

“In fact writing a computer program is a pretty good way to summarize knowledge about any set of rules.”

Richard Dawkins book Climbing Mount Improbable

Source: Climbing Mount Improbable (1996), Chapter 2, “Silken Fetters” (p. 58)

Nicholas Negroponte photo

“When you write a computer program you've got to not just list things out and sort of take an algorithm and translate it into a set of instructions. But when there's a bug — and all programs have bugs — you've got to debug it. You've got to go in, change it, and then re-execute … and you iterate. And that iteration is really a very, very good approximation of learning.”

Nicholas Negroponte (1943) American computer scientist

Nicholas Negroponte: A 30-year history of the future http://www.ted.com/talks/nicholas_negroponte_a_30_year_history_of_the_future, July 2014, TED Talks (about 13:40 into 19:43 video).
A 30-year history of the future, TED Talk (2014)

Seymour Papert photo

“Should the computer program the kid or should the kid program the computer?”

Seymour Papert (1928–2016) MIT mathematician, computer scientist, and educator

Spacewar http://wheels.org/spacewar/stone/rolling_stone.html ROLLING STONE · 7 DECEMBER 1972

Richard Stallman photo

“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)]
2010s

Related topics