Start reading Dreaming in Code on the free Kindle Reading App or on your Kindle in under a minute. Don't have a Kindle? Get your Kindle here.
Programming Books C Java PHP Python Learn more Browse Programming Books

Deliver to your Kindle or other device

Enter a promotion code
or gift card

Try it free

Sample the beginning of this book for free

Deliver to your Kindle or other device

Sorry, this item is not available in
Image not available for
Image not available

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software [Kindle Edition]

Scott Rosenberg
3.8 out of 5 stars  See all reviews (94 customer reviews)

Print List Price: $15.00
Kindle Price: $11.84
You Save: $3.16 (21%)
Sold by: Random House LLC

Free Kindle Reading App Anybody can read Kindle books—even without a Kindle device—with the FREE Kindle app for smartphones, tablets and computers.

To get the free app, enter your email address or mobile phone number.

Audible Narration

Switch back and forth between reading the Kindle book and listening to the Audible narration with Whispersync for Voice. Add narration for a reduced price of $4.49 when you buy the Kindle book.


Amazon Price New from Used from
Kindle Edition $11.84  
Hardcover --  
Paperback $12.50  
Audible Audio Edition, Unabridged $15.95 or Free with Audible 30-day free trial
Shop the new
New! Introducing the, a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Book Description

Their story takes us through a maze of dead ends and exhilarating breakthroughs as they and their colleagues wrestle not only with the abstraction of code but with the unpredictability of human behavior,
especially their own. Along the way, we encounter black holes, turtles, snakes, dragons, axe-sharpening, and yak-shaving—and take a guided tour through the theories and methods, both brilliant and misguided, that litter the history of software development, from the famous “mythical man-month” to Extreme Programming. Not just for technophiles but for anyone captivated by the drama of invention, Dreaming in Code offers a window into both the information age and the workings of the human mind.

From the Hardcover edition.

Editorial Reviews Review

In the 80s, Tracy Kidder's The Soul of a New Machine attempted to define the story of the development of a minicomputer: from the new science to the business and nascent culture of electronic hardware and software that was characteristic of that time. Scott Rosenberg's Dreaming in Code draws on Kidder's model as it attempts to document the state of software, the Internet, and everything circa 2006 through the lens of Chandler, an as-yet-unfinished software application for the management of personal information.

The Chandler project--driven by Mitch Kapor, the founder of Lotus Development and main author of its 1-2-3 spreadsheet, and later co-founder of the Electronic Frontier Foundation--isn't the primary point of Dreaming in Code, though reading about software people and their social behavior is at least as interesting as reading about that of meerkats or monkeys. Rather, Chandler is a rhetorical device with which Rosenberg takes on the big questions: How do software development teams work (or not)? Why does the reuse of software modules rarely work altogether correctly? Does open-source development by volunteers on the Internet lead to innovation or just insanely bifurcated chaos? Chandler helps his readers think more clearly about all of these issues; however, "answers" to these questions are, of course, not to be had, which is one of his points.

The problem with books about technical subjects that aspire to appeal to a general audience, particularly computers and software, is that such subjects are so far outside the realm of familiarity of most people that the prose bogs down in analogy and metaphor. Rosenberg manages to avoid too much of that and deliver a readable account of software development and culture. --David Wall

From Publishers Weekly

Software is easy to make, except when you want it to do something new," Rosenberg observes—but the catch is that "the only software worth making is software that does something new." This two-tiered insight comes from years of observing a team led by Mitch Kapor (the creator of the Lotus 1-2-3 spreadsheet) in its efforts to create a "personal information manager" that can handle to-do lists as easily as events scheduling and address books. Rosenberg's fly-on-the-wall reporting deftly charts the course taken by Kapor's Open Source Applications Foundation, while acknowledging that every software programmer finds his or her own unique path to a brick wall in the development process. (The software is still in development even now.) With equal enthusiasm, Rosenberg digs into the history of the computer industry's efforts to make programming a more efficient process. Though there's a lot of technical information, it's presented in very accessible terms, primarily through the context of project management. Even readers whose computer expertise ends at retrieving their e-mail will be able to enjoy digressions into arcane subjects like object-oriented programming. (Jan.)
Copyright © Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.

Product Details

  • File Size: 348 KB
  • Print Length: 418 pages
  • Page Numbers Source ISBN: 1400082471
  • Publisher: Crown (January 16, 2007)
  • Sold by: Random House LLC
  • Language: English
  • Text-to-Speech: Enabled
  • X-Ray:
  • Word Wise: Not Enabled
  • Lending: Not Enabled
  • Amazon Best Sellers Rank: #134,375 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
  •  Would you like to give feedback on images?

Customer Reviews

Most Helpful Customer Reviews
67 of 67 people found the following review helpful
4.0 out of 5 stars All Too Familiar February 21, 2007
If you're in software development in any capacity, you'll find almost everything in this book is depressingly familiar: schedules dragging on endlessly, vague ideas standing for clear feature descriptions, and a remarkable lack of interest in learning from the past. You meet the indecisive manager, the frustrated designer, and the cowboy coder (the one who loses interest in things as soon as they finally work, determined to gut and rewrite thousands of lines of code for the sake of incremental "elegance").

"Dreaming in Code" really isn't a description of the act of programming, it's more about the difficulty of designing software with other people. It's not at all like designing, say, a new car, where real-world constraints (like the laws of physics and the behavior of materials) come into play. In software, nearly anything is possible. Unfortunately, or a "what comes out of that isn't usually the thrill of possibility, but the paralysis of choice. And that's what Rosenberg captures so well here: the endless, endless meetings discussing what *could* be done, how features *might* work, or what sorts of things "users" *might* want. And it is always that nebulous term "the user" here, the Chandler project never seems to bother thinking much about exactly who will use their product, under what circumstances.

It's not giving anything away to mention that the Chandler project doesn't end at the end of the book. Amazingly, the project is *still* grinding away after four years, releasing incremental versions of their calendar application (each loudly proclaiming that it's an "experimentally usable version"), even as they get passed by on a regular basis by new, fully-usable, web-based calendars like the one from Google.

It's not exactly a fun read--it is essentially a case study of a very long series of meetings--but it should be required reading for anyone involved in software development.
Comment | 
Was this review helpful to you?
116 of 131 people found the following review helpful
4.0 out of 5 stars Good writing, hobbled by bad choice of project January 18, 2007
By Yaron
Santa came through this year with a slightly advance copy of "Dreaming in Code", which tries to do for software engineering what "The Soul of a New Machine" did for computer engineering, following a single project through to its attempted conclusion. Software development is a story that's very rarely told, considering how dramatically software has changed all of our lives in the last 30 years. Author Scott Rosenberg does a good job of conveying the difficulties in software engineering, and the inevitable headaches and drama that come with incomplete plans and shifting specs (and they're always incomplete and shifting).

Where Rosenberg went wrong, unfortunately, is his choice of project to follow. Mitch Kapor's Chandler is quite atypical of software projects: it's driven entirely by one man's quixotic vision, and never has to encounter the usual give-and-take with VC's or upper management that help to clarify a plan. Kapor comes off as an untethered idealist (Al Gore makes the obligatory cameo at the office), and his project is afflicted by the same we-are-the-world unseriousness as his politics. Most notably, Kapor decides there should be no central repository for data (because, hey, down with authority and all that): instead, every item will just be represented, Napster-style, across users' personal computers. It's a costly decision that I don't think would have been made if it were more than just Kapor running the show.

Actually, I think the strongest part of the book is when Rosenberg abandons the project entirely in the middle section to delve into the history of the programming discipline, noting everyone from Donald Knuth to 37signals' Jason Fried. It's a useful, lucid introduction to the field that contains stories I hadn't seen before.
Read more ›
Was this review helpful to you?
43 of 46 people found the following review helpful
5.0 out of 5 stars recommended for non programmers January 23, 2007
Format:Hardcover|Verified Purchase
Ansel Adams wrote, "There is nothing worse than a sharp image of a fuzzy concept." And such is the case with the Chandler project. After four years of development, they have delivered only a 0.6 release with no general availability in sight.

In Dreaming in Code, author Scott Rosenberg follows a group of programmers tasked with creating a new product over a three-year stint. Along the way the book explores disciplines in development (and the lack of), the history of computing (particularly its truths and folklore), and explains why software engineering isn't a science but an art. A common misconception even among developers is that software is similar to construction when, as becomes clear in the book, developing software is more like cooking. Programming methodologies are as plentiful as cookbooks but both are limited by the realities of artistry. A chef can make miracles from a pantry full of ingredients; a cook cannot.

If you're involved with a development team as a marketer, there is much here that will illuminate your team's dysfunction. Rosenberg reintroduces us to concepts that have been known since The Mythical Man Month and The Soul of a New Machine but apparently not understood, remembered, or believed. Strongly recommended.
Comment | 
Was this review helpful to you?
40 of 47 people found the following review helpful
2.0 out of 5 stars Confusing February 3, 2007
I have been following the Chandler project with interest from the beginning and have checked out most of the releases. Even to a distant observer,the glacial progress of the project, the lack of clarity about the objectives, and the mid-course changes that have reduced it to a pale shadow of the original vision, have been baffling.So, when I noticed Rosenberg's book, I immediately bought it and devoured it in a couple of hours. While the main focus of the book is on Chandler, the OSAF and the personalities there, it does talk quite a bit about the difficulties of software development, history of programming languages, methodologies etc quite a bit. I suspect the actual Chandler & OSAF content page wise might be only 50-60%. The book's general approach is like this - start out with something that the OSAF tried to do, then drift into a related topic from the history of software development; it alternates between discussions of the development of Chandler and various other topics. Very rarely does Scott Rosenberg actually examine why certain development efforts at OSAF failed in depth - he relies too much on failures of 'proprietary' software projects as a way of explaining the failures of the Chandler project. There is no open source context to the discussion most of the time - examining some aspect of software development of an open source project and drawing parallels from the failure of some proprietary software development effort is confusing. One of the most puzzling things about a lot of software doomsday scenario books is that, in spite of the fact that not all projects fail, they never try to figure out what made the successful ones work. Maybe nothing sells like a disaster. This book is no exception. Read more ›
Comment | 
Was this review helpful to you?
Most Recent Customer Reviews
3.0 out of 5 stars What happens in most software development projects
More suitable for someone who is just starting their career in software development.
For anyone else who has been in the industry for a while, the stories in this book are all... Read more
Published 1 month ago by Charles Chan
4.0 out of 5 stars Even the best have issues on major projects
Interesting book. Even the best have issues on major projects!
Published 6 months ago by LHO
5.0 out of 5 stars Should Be Required Reading
This book should be required reading for anyone thinking of making programming a career. It is an easy read, but has some real insights on the real world and coding. Read more
Published 12 months ago by Ken
3.0 out of 5 stars Less A Lesson, More An Anecdote
A story about one specific software development project that went off the rails, with very little to say about software projects in general, why they fail, or why they succeed. Read more
Published 13 months ago by Amazon Customer
2.0 out of 5 stars booooring
Didn't care for this - found the project alternately boring and gossipy and just painful to witness. I didn't finish the book. Read more
Published 14 months ago by Erica Robinson
5.0 out of 5 stars Great book for everyone who is interested in programming
This book is fun to read, very imformative , and touches many of the major problems that contemporary software engineers face. Read more
Published 23 months ago by Shai Aharoni
5.0 out of 5 stars Good Read
Was a good book for showing the travesty through the years of computer evolution. This book is very well written and an easy read. Read more
Published on February 23, 2013 by Jason M. Bartholomai
5.0 out of 5 stars In a world crazy for software start ups this is a must read for...
At the beginning of the book I thought Scott Rosenberg was going to fail in his narrative of a software development project. Read more
Published on December 31, 2012 by Jon
4.0 out of 5 stars A good writer tackles the story of how we build software
Scott Rosenberg wrote some great technology articles at Salon, and I've always enjoyed his writing style. Read more
Published on November 25, 2012 by Moe Zilla
5.0 out of 5 stars Creating
Upgrading a platform makes the author, the founder of SALON, cringe since there are so many things, (some unknown), that can go wrong. Read more
Published on September 29, 2012 by Mary E. Sibley
Search Customer Reviews
Search these reviews only

More About the Author

I grew up in Queens, NY, and first experienced the joys of self-publishing in close proximity to a hand-cranked mimeograph machine. Spent my 20s as a theater and movie critic, first for the Boston Phoenix, then the SF Examiner. Fell under the spell of the Bay Area's techno-culture just in time to experience the joys of self-publishing on the Web in its earliest days. Helped found in 1995, edited its technology coverage through 1999, then became managing editor. Took a leave from Nov 2004 to Dec. 2005 to write DREAMING IN CODE.

What Other Items Do Customers Buy After Viewing This Item?


Topic From this Discussion
Dreaming in streams
Verioning systems did not make you're life easier? My God, man, a source control system is one of the Must-Have tools in any devlopers toolbox! Some are better and less intrusive than others though - I'm a fan of Subversion/TortoiseSVN. (BTW I too am a fan of Agile and 'Extreme' programming... Read More
Jan 18, 2007 by Amazon Customer |  See all 2 posts
Have something you'd like to share about this product?
Start a new discussion
First post:
Prompts for sign-in

Search Customer Discussions
Search all Amazon discussions

Look for Similar Items by Category