Lesson plan

Dreaming in Code

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software is a (2007) Random House literary nonfiction book by Salon.com editor and journalist Scott Rosenberg. It documents the workers of Mitch Kapor's Open Source Applications Foundation as they struggled with collaboration and the software development task of building the open source calendar application Chandler. Rosenberg spent time observing the organization at work and wrote about its milestones and problems. The book combines narrative with explanations of software development philosophy, methodology, and process, referring to The Mythical Man-Month and other texts of the field. In a review published in the Atlantic, James Fallows compared the book to Tracy Kidder's The Soul of a New Machine. At the time of the book's publication, OSAF had not yet released Chandler 1.0. Chandler 1.0 was released on August 8, 2008.

Back to article

Article summary

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software is a (2007) Random House literary nonfiction book by Salon.com editor and journalist Scott Rosenberg. It documents the workers of Mitch Kapor's Open Source Applications Foundation as they struggled with collaboration and the software development task of building the open source calendar application Chandler. Rosenberg spent time observing the organization at work and wrote about its milestones and problems. The book combines narrative with explanations of software development philosophy, methodology, and process, referring to The Mythical Man-Month and other texts of the field. In a review published in the Atlantic, James Fallows compared the book to Tracy Kidder's The Soul of a New Machine. At the time of the book's publication, OSAF had not yet released Chandler 1.0. Chandler 1.0 was released on August 8, 2008.

Key claims

  1. release date: 2008-08-08 — source: Wikipedia · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the release date is "2008-08-08". What evidence would count against this claim?
  3. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  4. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.