HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kragen
knuth-interview-2006
Learning & Reference2010–2024
kragen / knuth-interview-2006

knuth-interview-2006

The transcript of a Donald Knuth interview in 2006

11Distinct people
17Mentions
0Explicit recommenders
229GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The transcript of a Donald Knuth interview in 2006

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2010-05-31 02:09:31 UTC to 2024-07-26 22:53:13 UTC.

01232010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC110
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC202
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC000
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC110
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

17 sources
Donald Knuth interviews are so interesting, but would like to particularly highlight this little piece of advice, out of this great playlist: "Donald Knuth - My advice to young people": https://youtu.be/75Ju0eM5T2c Complete Playlist - "Donald Knuth (Computer scientist)" [97 videos]: https://www.youtube.com/playlist?list=PLVV0r6CmEsFzeNLngr1Jq... Also the "Oral History of Donald Knuth" from the Computer History Museum is great. "Oral History of Donald Knuth Part 1": https://youtu.be/Wp7GAKLSGnI "Oral History of Donald Knuth Part 2": https://www.youtube.com/watch?v=gqPPll3uDa0 Plus.. "Donald Knuth Interview 2006": https://github.com/kragen/knuth-interview-2006 "An Interview with Donald Knuth": https://www.ntg.nl/maps/16/14.pdf "Interview with Donald Knuth": https://www.informit.com/articles/article.aspx?p=1193856 This somewhat "colourful" p
Read the rest
age also tracks a few: http://www.softpanorama.org/People/Knuth/donald_knuth_interv... PS: The story that he told Steve Jobs he was "Full of shit" is not true. "Donald Knuth never told Steve Jobs that he was full of shit" https://news.ycombinator.com/item?id=2634635
In Donald Knuth on work habits, problem solving, and happiness (2020)
(I started writing this comment when the submitted title was “The Summer Of 1960 (Time Spent with don knuth)” and the url was specifically the section http://ed-thelen.org/comp-hist/B5000-AlgolRWaychoff.html#7 , but it still applies I guess.) There's a PDF version at https://www.computerhistory.org/collections/catalog/10272464... which incidentally is a scan from a copy given to the Computer History Museum by Donald Knuth himself — before the title “Stories about the B5000…” he has added, in pencil, “Half-true”. :-) Knuth tells his side of this story in video 27 (of 97) of his Web of Stories oral history: https://www.youtube.com/watch?v=QeiuVNDQg4k&list=PLVV0r6CmEs... — transcript (thanks to https://github.com/kragen/knuth-interview-2006): > Some people from Thompson Ramo Wooldridge approached me and said, Don, we understand that you can
Read the rest
write compilers. We’re going to put in a proposal to Burroughs to write a compiler for their machine, the Burroughs 205, for a language called ALGOL, which was just being invented at that time […] made a proposal to Burroughs for I believe it was $70,000, to create an ALGOL compiler for the Burroughs 205. The people who made this proposal really, though, were clueless about how to write compilers, so they hired me, a Case senior, to do the job, because they had heard that I knew how to do it. I had done this RUNCIBLE and a couple of versions of other software at Case, […] but Burroughs turned them down; they didn’t give them the contract. > So after Burroughs said no, […] maybe I’ll write to Burroughs on my own, and I sent them a letter and said, I’ll, you know, for $5,000 I can write you an ALGOL compiler. Now $5,000 was a huge amount of money in 1959, 1960. I mean a college professor was making $8,000 a year or something like this. So I thought $5,000 was an incredibly rich thing, you know, to do. […] > […] I spent the summer writing this compiler for ALGOL, for the Burroughs 205, and I wrote it, but really I had it only in pencil and paper, I didn’t have it ready to go, and then I would take it with me on, as I went out to Pasadena, and work on it there when I was at the Burroughs plant in Pasadena. > So on my way out West; I had a little Volkswagen, that I had gotten from my parents, and I drove 100 miles a day, and got a motel, and sat down, and wrote code, wrote software, and took 30 days to drive from Milwaukee to Pasadena, every day writing a little bit of this software. Then I got to Pasadena, and had all my code, had all my notes, and started putting it on to punched cards, and you know, debugging it and by Christmas time I had their compiler for them […] I heard for the next ten years that people in Brazil were still using it a lot. > And so it was a, it was an interesting experience for me, but the most important, from my point of view, was I had $5,500, which was enough to get married. And so in the summer of ‘61 Jill and I got married, and it paid for our honeymoon trip in Europe, which was our first time seeing the world. The actual compiler “source code” (written in pencil, assembly language and flowcharts) seems to be this one: http://archive.computerhistory.org/resources/text/Knuth_Don_... There's also 43-page “documentation” of the compiler http://archive.computerhistory.org/resources/text/Knuth_Don_... which starts with “How does this compiler work? Frankly, it's a miracle if it does”. Also in the same interview, he reveals something about how he ended up getting a master's degree (as mentioned in the story here): > […] second half of my freshman year, I started having a little problem with my grades, and so I had to give up ping-pong. > But starting in my sophomore — junior year, I found out that you could take graduate courses at Case, and they were easier than the undergraduate courses. The reason is that Case had really strict admissions requirements for undergrads, but they were fairly loose about admitting graduate students. […] > And as a result, I had accumulated also, by the time I was a senior, I had accumulated lots and lots of graduate credits. Now, as a result then, Case did, on Graduation Day, Case did an unprecedented thing that had never been done before, they awarded me a Master’s Degree, simultaneously with my Bachelor’s Degree. And this, the faculty had gotten together and [voted] unanimously that this should happen, and I remember, you know, that was another thing that got into the newspapers at the time […] I had taken these graduate courses because they were easier. I didn’t, I don’t know if I’ve ever told anybody else this before today, but that was one of the reasons I could do so many other things.
In Stories about the B5000 and people who were there (1979)
A lot of novices think that, but it turns out that there are many problems that are easy to find by code reviews that are hard to find by testing. (And vice versa — testing is very valuable, especially with things like Hypothesis.) I'm skeptical that the scope of things you can get working at all by mindlessly banging on tests without thinking about the problem is very large, and when you add other aspects of the software development lifecycle, your prospects seem very slender indeed. If reading your code takes "ages", how are you going to figure out how to extend it next week when you need to change what it does? How are you going to debug it when it crashes once you put in production? I have written compilers in a somewhat test-driven fashion, and I am especially skeptical that you can purely TDD a compiler. Certainly I've never see
Read the rest
n it done. I'm far more skeptical that you could TDD a compiler written in assembly language that achieves the kind of performance this scenario implies. (But tests, especially regression tests, are extremely valuable for writing compilers.) The particular compiler we're talking about here was one Knuth wrote during a summer-long road trip for US$5500 (roughly US$120 000 today). So the situation was actually considerably more extreme than you're imagining — not only did he not have punch cards when he wrote the compiler, he'd never seen the computer. So he had to spend a few months debugging it after he actually finished driving to the other side of the continent where the computer was. https://github.com/kragen/knuth-interview-2006#27---writing-...
In Advice on Getting Better from an Accomplished Piano Player (2011)
This is in fact one of several oral histories that Knuth has done over the last few years: * 2001, 2 hours audio (http://purl.umn.edu/96227), 27-page transcript (https://conservancy.umn.edu/handle/11299/107413) (partial I guess?) * 2006, Web of Stories, 7.5 hours video in 97 short parts https://www.youtube.com/playlist?list=PLVV0r6CmEsFzeNLngr1Jq... , transcript (https://github.com/kragen/knuth-interview-2006) * 2007, interview by Ed Feigenbaum, 3 hours (https://www.youtube.com/watch?v=Wp7GAKLSGnI) + 4 hours (https://www.youtube.com/watch?v=gqPPll3uDa0), 73-page transcript (https://archive.computerhistory.org/resources/access/text/20...) * 2018, this one (https://purl.stanford.edu/jq248bz8097), about 4.5 hours, 177-page transcript (but 50 pages of those are Knuth's CV!) * 2018, by the Computer History Museum, 1.5 hours, specifically about
Read the rest
the earliest programs he wrote as an undergrad when he first encountered computers (https://www.youtube.com/watch?v=Q9JOrmgHw28): the programs themselves are here: https://www.computerhistory.org/collections/search/?s=X8738.... (in machine language / assembly) I've watched the Web of Stories one fully (and the others not yet fully)… they are a delight. You can see the way his mind works, and he's someone whose career has spanned basically the entirety of computer science as a separate academic discipline.
In Donald E. Knuth: An Oral History (2018) [video]
Knuth has an interesting take on this, as he learned by reading programs. He claims if the programs he first saw were too good, he wouldn't have bothered with programming: https://github.com/kragen/knuth-interview-2006/blob/master/R... "I read the manuals that came from IBM, and it had; the manuals had example programs in there, and I thought of better ways to write those programs. I thought of, you know, well, okay, this program works, but if you did it this way, it would be even better. And so that’s given me some confidence that maybe I had a talent for programming. Now, if the manual hadn’t had these bad examples in it, I probably would not have gotten interested in programming, because I wouldn’t have this confidence, and I would have been scared and say, oh, I would never think of this.But the fact is, the manuals were pretty stupi
Read the rest
d, and that’s what gave me the confidence that I should think a little more about programming, because I might be, you know, I might be good at it."
In Learning from Code vs. Plagiarism
Knuth talks about this video in his "Web of Stories" interview: https://www.youtube.com/watch?v=RnMkW8M1ZGk&list=PLVV0r6CmEs... > I was manager of the basketball team, at Case. > And I’ll say a few words about that, because after I got into computers later on, I combined that with my managing the Basketball team. So I devised a strange formula that I don’t believe in much any more, but anyway, I had it at the time, where you could compute each basketball player’s real contribution to the game. > [...] So I calculated a huge number of statistics for every player, and I had a spotter, who would call to me, and I could write it down, every little thing, and after the game I would go and punch cards that recorded all these statistics, and fed them into a little computer program [...] > So Case’s Coach, Nip Heim, loved this system, and you kno
Read the rest
w, he posted these numbers, and the Case News Service was always good at trying to plant interesting stories in the local paper, so they sent reporters out [...] and IBM heard about it. So IBM sent out [a camera crew] to make a film of me spotting a game, [...] our Case team playing basketball [...] how I would punch the cards, you know, and put it into the IBM computer. Before they took the shot of the IBM computer, they planted a great, big IBM sign on the machine, so that nobody could fail to miss it [...] and it’s getting printed out on the IBM printer, and then the Coach is looking at it and posting this up. > So this was a little movie that I was in, about two or three minutes long. IBM supplies this movie to CBS, and they put it on the Sunday Evening News with Walter Cronkite, and all my relatives in Florida can see me on TV. This was very exciting. Also US News and World Report ran a story about it, and so this was my connection between computing and sports, when I was at Case. This was also a clever way for IBM to get their advertisements in there, rather subtly, but it was fun. > That was when I first realized how hard it must be to be a movie star, because I had to walk through these scenes six times everything, you know, punch those cards over and over again. How could Audrey Hepburn possibly look so beautiful after the sixth take, you know? (Thanks to https://github.com/kragen/knuth-interview-2006 for transcribing the videos.)
In The Electronic Coach (1959) [video]
I like these two quotes of Knuth where he lets us know how hard he worked. -- From this small interview [1]: "When I'm working on a research problem I generally begin by filling dozens of sheets of scratch paper with partial calculations. When I eventually get to a point where I can think about the problem while swimming, then I'm often ready to solve it." -- From this other interview [2]: "So I went to Case, and the Dean of Case says to us, says, it’s a all men’s school, says, “Men, look at, look to the person on your left, and the person on your right. One of you isn’t going to be here next year; one of you is going to fail.” So I get to Case, and again I’m studying all the time, working really hard on my classes, and so for that I had to be kind of a machine. I, the calculus book that I had, in high school we — in high school, as I sai
Read the rest
d, our math program wasn’t much, and I had never heard of calculus until I got to college. But the calculus book that we had was great, and in the back of the book there were supplementary problems that weren’t, you know, that weren’t assigned by the teacher. The teacher would assign, so this was a famous calculus text by a man named George Thomas, and I mention it especially because it was one of the first books published by Addison-Wesley, and I loved this calculus book so much that later I chose Addison-Wesley to be the publisher of my own book. But Thomas’s Calculus would have the text, then would have problems, and our teacher would assign, say, the even numbered problems, or something like that. I would also do the odd numbered problems. In the back of Thomas’s book he had supplementary problems, the teacher didn’t assign the supplementary problems; I worked the supplementary problems. I was, you know, I was scared I wouldn’t learn calculus, so I worked hard on it, and it turned out that of course it took me longer to solve all these problems than the kids who were only working on what was assigned, at first. But after a year, I could do all of those problems in the same time as my classmates were doing the assigned problems, and after that I could just coast in mathematics, because I’d learned how to solve problems. So it was good that I was scared, in a way that I, you know, that made me start strong, and then I could coast afterwards, rather than always climbing and being on a lower part of the learning curve." [1] http://authenticinquirymaths.blogspot.pt/2015/11/maths-in-sc.... [2] Transcript from here: https://github.com/kragen/knuth-interview-2006
In The Yoda of Silicon Valley
Upvoted for careful scholarship and a useful addendum (I'm OP)! I sometimes wonder whether a lot of Knuth's greatness comes from doing more of the stuff everyone knows they should do but don't. If you read this interview (https://github.com/kragen/knuth-interview-2006) with Knuth, he talks about how he was nervous he wouldn't be able to learn calculus so just decided to do all the problems instead of just the assigned ones. Unsurprisingly, partly because he's Knuth and we all know Knuth can do math, he ends up really good at calculus: > But Thomas’s Calculus would have the text, then would have problems, and our teacher would assign, say, the even numbered problems, or something like that. I would also do the odd numbered problems. In the back of Thomas’s book he had supplementary problems, the teacher didn’t assign the supplementary prob
Read the rest
lems; I worked the supplementary problems. I was, you know, I was scared I wouldn’t learn calculus, so I worked hard on it, and it turned out that of course it took me longer to solve all these problems than the kids who were only working on what was assigned, at first. But after a year, I could do all of those problems in the same time as my classmates were doing the assigned problems, and after that I could just coast in mathematics, because I’d learned how to solve problems. So it was good that I was scared, in a way that I, you know, that made me start strong, and then I could coast afterwards, rather than always climbing and being on a lower part of the learning curve.
In Nobody's just reading your code
I like these two quotes of Knuth where he lets us know how hard he worked. -- From this other small interview [1]: "When I'm working on a research problem I generally begin by filling dozens of sheets of scratch paper with partial calculations. When I eventually get to a point where I can think about the problem while swimming, then I'm often ready to solve it." -- From OP's interview [2]: "So I went to Case, and the Dean of Case says to us, says, it’s a all men’s school, says, “Men, look at, look to the person on your left, and the person on your right. One of you isn’t going to be here next year; one of you is going to fail.” So I get to Case, and again I’m studying all the time, working really hard on my classes, and so for that I had to be kind of a machine. I, the calculus book that I had, in high school we — in high school, as I sai
Read the rest
d, our math program wasn’t much, and I had never heard of calculus until I got to college. But the calculus book that we had was great, and in the back of the book there were supplementary problems that weren’t, you know, that weren’t assigned by the teacher. The teacher would assign, so this was a famous calculus text by a man named George Thomas, and I mention it especially because it was one of the first books published by Addison-Wesley, and I loved this calculus book so much that later I chose Addison-Wesley to be the publisher of my own book. But Thomas’s Calculus would have the text, then would have problems, and our teacher would assign, say, the even numbered problems, or something like that. I would also do the odd numbered problems. In the back of Thomas’s book he had supplementary problems, the teacher didn’t assign the supplementary problems; I worked the supplementary problems. I was, you know, I was scared I wouldn’t learn calculus, so I worked hard on it, and it turned out that of course it took me longer to solve all these problems than the kids who were only working on what was assigned, at first. But after a year, I could do all of those problems in the same time as my classmates were doing the assigned problems, and after that I could just coast in mathematics, because I’d learned how to solve problems. So it was good that I was scared, in a way that I, you know, that made me start strong, and then I could coast afterwards, rather than always climbing and being on a lower part of the learning curve." [1] http://authenticinquirymaths.blogspot.pt/2015/11/maths-in-sc... [2] Transcript from here: https://github.com/kragen/knuth-interview-2006
In Donald Knuth speaks about his life [video]

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.