Main menu:

Over at my Wordyard blog we're reading and discussing books and essays that shaped today's software world. Join the conversation.

Recent posts about Dreaming in Code from Scott's blog:

Endnotes (chapter 10-11)

Go back to the first Endnotes page (chapters 0-4). Go back to the second Endnotes page (chapters 5-8).


  • 270 — All quotes are from the 1968 NATO software engineering conference report: P. Naur and B. Randell, eds., “Software Engineering: Report of a Conference Sponsored by the NATO Science Committee,” Garmisch, Germany, October 7-11, 1968 (Scientific Affairs Division, NATO, 1969). The 1969 conference report: B. Randell and J. N. Buxton, eds., “Software Engineering Techniques: Report of a Conference Sponsored by the NATO Science Committee,” Rome, Italy, October 27-31, 1969 (Scientific Affairs Division,NATO, 1970). Both reports and background material are available at
  • 271 — The Texas dispute over programmers calling themselves engineers is chronicled in “An Engineer by Any Other Name: Legislature to Decide if Computer Programmers Can Legally Use the Title,” by R. G. Ratcliffe, Houston Chronicle, March 29, 2003.
  • 272 — “The phrase ‘software engineering’ was deliberately chosen”: 1968 conference report, p. 8.
  • 272 — “Unlike the first conference”: Randell, “The 1968/69 NATO Software Engineering Reports.”
  • 272 — “Bore little resemblance”: 1969 conference report, p. 8.
  • 273 — A definitive discussion of the art/science dichotomy can be found in the preface to Steven Johnson, Interface Culture (HarperEdge, 1997).
  • 283 — “A well-known scientist”: Stephen Hawking, A Brief History of Time (Bantam, 1988), p. 1.
  • 284 — Dr. Seuss, Yertle the Turtle and Other Stories (Random House, 1958).
  • 284 — “If builders built houses”: Quotation widely attributed to Gerald Weinberg and confirmed in email to author.
  • 285 — Description of Alan Kay’s presentation is from author’s observation at the O’Reilly Emerging Technology Conference (ETech), April, 2003. Lisa Rein recorded the event; see
  • 286 — “We just don’t know how”: Kay, ETech talk.
  • 287 — “It’s all air and glass”: Kay, OOPSLA 1997 keynote.
  • 288 — “We don’t have to build pyramids”: Kay, OOPSLA 2004 Turing Award lecture.
  • 288 — “Someday, we’re going to invent”: Alan Kay group interview at ETech 2003.
  • 288 — “Something like a computer”: Kay, OOPSLA 1997 keynote.
  • 289 — “I made up the term object-oriented”: Kay, OOPSLA 1997 keynote.
  • 290 — “At PARC, our idea was”: “A Conversation with Alan Kay,” ACM Queue.
  • 293 — “If you make a small change”: Lanier in Hess, “Coding from Scratch.”
  • 293 — “The world as our nervous systems,” “Try to be an ever better guesser,” and “When you de-emphasize protocols”: Lanier, “Gordian Software.”
  • 294 — “The moment programs grow beyond”: Lanier, “Gordian Software.”
  • 294 — “Little programs are so easy”: Jaron Lanier talk at OOPSLA Conference, October 2004.
  • 295 — “The fundamental challenge for humanity”: Jaron Lanier, interview with author, October 2005.
  • 295 — “I’m just sick of the stupidity”: Jaron Lanier at OOPSLA 2004.
  • 296 — “We are stuck with the evolutionary pattern”: Robert N. Britcher, The Limits of Software (Addison Wesley, 1999), p. 190.
  • 296 — “Essential property” and following: Frederick Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering,” Computer 20:4 (April 1987), pp. 10-19.
  • 299 — “With code, the computer tells you”: Bill Joy in a 2004 New York Times interview by Jon Gertner, June 6, 2004.
  • 300 — “I think we need to be ashamed” and “Everything we’ve done”: Richard Gabriel talk at the Software Development Forum, Palo Alto, California, January 23, 2003.
  • 302 — “Art meant something devised” and “The chief goal of my work”: Donald Knuth, “Computer Programming as an Art,” 1974 Turing Award lecture, in Communications of the ACM, December 1974.
  • 303 — “Couldn’t stand to write books”: Donald Knuth quoted in Steve Ditlea, “Rewriting the Bible in 0’s and 1’s,” Technology Review, September-October 1999.
  • 304 — “What were the lessons I learned”: Donald Knuth, Selected Papers on Computer Science (CSLI Publicational/Cambridge University Press, 1996), p. 161.
  • 305 — “A longer attention span is needed”: Knuth, Selected Papers on Computer Science, p. 145.
  • 306 — The information about the Piet Hein poem over Knuth’s entrance is from Ditlea, “Rewriting the Bible,” in Technology Review.
  • 306 — “Instead of imagining that our main task”: From Donald Knuth, “Literate Programming (1984)” in Literate Programming, Center for the Study of Language and Information, 1992, p. 99, as cited at


  • 320 — The line counts for Chandler were made by OSAF interns Brendan O’Connor and Arel Cordero.
  • 320 — The intern who compared joining Chandler to “moving to a new city” was Arel Cordero.
  • 328 — Douglas Hofstadter, Godel, Escher, Bach: An Eternal Golden Braid (Basic, 1979).
  • 329 — “Any recursive function will cause”: From Colin Allen and Maneesh Dhagat, LISP Primer, at My discussion of the halting problem is indebted to David Harel’s lucid explanations in his book Computers Ltd.: What They Really Can’t Do (Oxford, 2000).
  • 329 — “It is tempting to try and solve the problem”: David Harel, Computers Ltd., p. 53.
  • 330 — “Dashes our hope for a software system”: Harel, Computers Ltd., p. 50.
  • 331 — Hofstadter’s Law appears on p. 152 of his book, Godel, Escher, Bach.
  • 337 — “Software development lacks one key element”: Alan Cooper, The Inmates Are Running the Asylum (SAMS, 1999), p. 41.


  • 348 — “The hard thing about building software”: Frederick Brooks, “No Silver Bullet: “Essence and Accidents of Software Engineering,” Computer 20:4 (April 1987), pp. 10-19.
  • 349 — “Ultimately, information systems only give”: Jaron Lanier at OOPSLA 2004 Conference.
  • 350 — “Relief from the confusions of the world”: Ellen Ullman, The Bug (Nan A. Talese/Doubleday, 2003), p. 9.
  • 353 — “In the short term we always underestimate”: Kurzweil, Long Now Foundation talk.