- Audible Audio Edition
- Listening Length: 12 hours and 2 minutes
- Program Type: Audiobook
- Version: Unabridged
- Publisher: Audible Studios
- Audible.com Release Date: December 18, 2012
- Whispersync for Voice: Ready
- Language: English
- ASIN: B00AQ5DOCA
- Amazon Best Sellers Rank:
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software Audiobook – Unabridged
Customers who bought this item also bought
Would you like to tell us about a lower price?
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
The book is about 2/3 following the day-to-day of the development team, 1/3 philosophizing about what programmers do and should do. The team started to grate on me after a while...maybe it was the whole "change the world" holier-than-thou approach they took to their project. It's just a calendar, and if you do a little research, it is utterly underwhelming. The history and philosophy of programming as the author sees it was very interesting, since I'm something of a code monkey myself. A reader from the general public might not appreciate that part so much, but this book will give most people a better sense of why software is buggy and takes so long to develop.
Kidder's book was successful because it reached a definite conclusion: the new machine was completed, and it met its goal of beating the VAX. During the course of the book, the reader vicariously became a hardware hacker, a power tool, pedal to the metal - you could feel the tension, the long nights into morning, the frustration.
In contrast, Chandler does not get finished in Dreaming; it's barely alpha test. Of course that's not the author's fault, but in that respect alone this book falls far short of Kidder's. As far as style, Rosenberg is not nearly as effective as Kidder in conveying to the reader the mentality, the spirit, the verve, the je ne sais quoi that embodies the software hacker. And I say that as someone who has had to hack software to the wee hours. In other words, I know what it's like, and Dreaming didn't really bring back wistful memories of the quest to get it working; how would a lay person get it?
That said, Dreaming is a start, but IMHO it still leaves a void for a book that really is a software version of Soul of a New Machine.
Mr. Rosenberg delves beyond the Chandler Project to put this effort into perspective with the history of computer software development. He tries to show why, despite the advances in computer hardware and the development of advanced programming languages, the creation of a new application remains so challenging. He shows how many of the challenges facing software development in the 1960's as outlined by Fredrick Brooks in "The Mythical Man-Month" are still facing programmers today, such as, adding more programmers to a project behind schedule, only makes it farther behind schedule. He explains why managing creative programmers whether it is for the Chandler Project, or for the FBI's Virtual Case File, is terribly difficult and can frequently lead to abject failure.
"Dreaming in Code" is written as much for the non-technicial reader as for a technical one. It does not require an advanced degree in computer programming to be understood. It is more of a epic travelog through the shoals of modern software development. Can the visionary communicate that vision to managers and programmers so they can bend technology to create the application? In some cases they can and in others the vision must be modified.
The reason I did not give this it's fifth star is that the story remains incomplete. This is not the fault of the author, but rather due to the delays in completing the Chandler project itself. A preview version of the Chandler application is due out this Spring, several years beyond the original schedule. But dispite this frustration, I would recommend this book to anyone interested in the complexity of technology development.