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 6-9)


Go back to the first Endnotes page (chapters 0-5). See notes for chapters 10-11.

CHAPTER 6
GETTING DESIGN DONE

  • 149 — “No one is speaking for the poor user”: From Mitchell Kapor’s “Software Design Manifesto” in Terry Winograd, Bringing Design to Software (Addison Wesley, 1996), and at http://hci.stanford.edu/bds/1-kapor.html.
  • 159 — “A favorite story at management meetings”: Peter Drucker, The Essential Drucker (Harper Business, 2001), p. 113.
  • 165 — David Allen, Getting Things Done (Viking Penguin, 2001).

DETAIL VIEW

  • 184 — “Simple things should be simple”: This quotation is widely attributed to Alan Kay. I have been unable to trace its original source. It is also occasionally attributed to Larry Wall.
  • 196 — “Because people read these names”: Ward Cunningham’s talk at the OOPSLA Conference, October 2004,Vancouver, B.C.
  • 204 — “Born with a silver spoon in its mouth”: Esther Dyson’s comment about On Technology was in “On Technology Gets on Track,” Forbes, June, 1991.

CHAPTER 8
STICKIES ON A WHITEBOARD

  • 209 — “We use what we build”: Robert Taylor, quoted in Thierry Bardini, Bootstrapping (Stanford University Press, 2000), p. 154.
  • 211 — “Allows users to collaboratively edit”: Description from the main WebDAV site at http://www.webdav.org/.

CHAPTER 9
METHODS

  • 240 — “Each program layer is to be understood”: Dijkstra, “Notes on Structured Programming.”
  • 241 — “Most discussions of the knowledge worker’s task”: Peter Drucker, “The Effective Executive,” (1966), in The Essential Drucker (Harper Business, 2001), p. 225.
  • 242 — Watts Humphrey’s account of his IBM experience is from his “Reflections on a Software Life” in In the Beginning: Recollections of Software Pioneers, Robert L. Glass, ed. (IEEE Computer Society Press, 1998), p. 29 and ff.
  • 244 — “An organization at Level 1″: Humphrey’s informal description is quoted in Mark Minasi, The Software Conspiracy: Why Software Companies Put Out Faulty Products, How They Can Hurt You, and What You Can Do About It (McGraw-Hill, 2000), pp. 48-49.
  • 246 — Minasi, The Software Conspiracy
  • 249 — Jon Ogg’s talk was at the Systems & Software Technology Conference, Salt Lake City, April 2004.
  • 249 — “The amount of software the Department of Defense”: Barry Boehm at the Systems & Software Technology Conference, 2004. For more on the software patterns movement, see Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software (Addison Wesley, 1995).
  • 250 — “These have the advantages”: From Kent Beck and Ward Cunningham, “A Laboratory for Teaching Object-Oriented Thinking,” from the OOPSLA ’89 Conference Proceedings, October 1989, New Orleans, at http://c2.com/doc/oopsla89/paper.html.
  • 251 — Barry Boehm, “A Spiral Model of Software Development and Enhancement,” in ACM SIGSOFT Software Engineering Notes, August 1986.

On to the notes for chapters 10-11.