|
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
|
List Price:
$13.95
Homebizpc.com Price:
$11.16
Your Savings: $ 2.79 ( 20% )
Subject To Change Without Notice
Availability: Usually ships in 24 hours
Manufacturer: Three Rivers Press
|
Average Customer Rating:  
|
|
Binding: Paperback
Dewey Decimal Number: 650
EAN: 9781400082476
ISBN: 1400082471
Label: Three Rivers Press
Manufacturer: Three Rivers Press
Number Of Items: 1
Number Of Pages: 416
Publication Date: 2008-02-26
Publisher: Three Rivers Press
Release Date: 2008-02-26
Studio: Three Rivers Press
|
|
|
|
|
|
Editorial Reviews:
|
Our civilization runs on software. Yet the art of creating it continues to be a dark mystery, even to the experts. To find out why it’s so hard to bend computers to our will, Scott Rosenberg spent three years following a team of maverick software developers—led by Lotus 1-2-3 creator Mitch Kapor—designing a novel personal information manager meant to challenge market leader Microsoft Outlook. Their story takes us through a maze of abrupt
dead ends and exhilarating breakthroughs as they wrestle not only with the abstraction of code, but with the unpredictability of human behavior— especially their own.
|
|
|
Spotlight customer reviews:
|
Customer Rating:
Summary: Best behind-the-scenes book since "Hackers"
Comment: I've not enjoyed a book this much since I read Steven Levy's "Hackers" - the behind-the-scenes stories and discussions are just great. I'm not a programmer by trade, but I dabbled a bit in high school and got some more in-depth training in college, but it wasn't my major... a book like this makes me realize not only the fun I may have missed but also the stress I may have dodged. The book definitely provides the ups and downs of the software development business. I especially enjoyed getting a deeper understanding of the Open Source movement and discovering that it too has its built-in problems and isn't the wonder-tech that some books and articles might try to paint it.
The best part of the book was reading along with each release of Chandler... .4 then .5 then .6... and now I visit the actual website and see that they did make their 1.0 release! The book just made my investigation of the actual product and its support/help/website that much more fun.
Great book! I'd love to see similar books done like this down the line.
Customer Rating:
Summary: hard to catagorize but a worthwhile read
Comment: i'm a sucker for any book on the margins between philosophy, social issues and computers, how and why they are shaping us and our communities.
this is kind of what the book is about.
to get a decent quick view of it, read chapter 10- engineers and artists, i think that the main points are on display here.
a few new words like dogfoodable.
a few new ideas i want to follow up on: leaking abstractions
it is a watchful eye on a software projection-chandler with the other eye on what it all means. why is interfacing people with machines hard? what is slippage and why it always happens? but basically a beginning analysis of why writing software poses some curious philosophic and practical issues.
i liked the book, a worthwhile read, look at chapter 10 and see if it warrants your time as well.
thanks for reading this review.
Customer Rating:
Summary: Best book ever about what software development is REALLY like
Comment:
I just finished reading an amazing book: "Dreaming in Code" by Scott Rosenberg. Like many good, recent non-fiction books, it alternates between a specific narrative with colorful real people, and general background information. In this case, it's the story of Chandler, a personal information management tool, and the team who are building it, led by Mitch Kapor.
The general background explains far more about real, contemporary software, how it is built, and what it's all about, than anything I've read before. Everyone learning to be a software engineer, or who wants to understand what software engineers actually do, should read this book.
In only 355 pages, Rosenberg discusses, in clear language that's easy to follow, at least the following:
* What working on a software project in a team is like, the subjective experience
* Open software, and the "Cathedral vs. Baazar" concept
* Doug Englebart's ideas (very germane to Chandler)
* Famous software fiascoes
* Computer languages, especially Python and how it compares to others
* Reusable software, software libraries, build versus buy
* What "geek" really means
* CVS, Bugzilla, and Wikis
* Why user interfaces are so hard to design
* Dependencies between parts of a system and how they block work
* Release management and scheduling
* Specifications and their nature
* Layers of abstraction
* Scaffolding
* Code reviews
* WebDAV and CalDAV
* Microsoft FUD
* Requirements analysis
* Methodologies: waterfall, agile
* The gist of No Silver Bullet and The Mythical Man-Month
* Ruby on Rails
* Software engineering, its history and what it means
* Complexity
* Late binding
* Object-oriented programming
* Recursion
* The halting problem
The story of Chandler and the team is compelling and instructive. On page 173 of the book, he says: "By now, I know, any software developer reading this volume has likely thrown it across the room in despair, thinking, `Stop the madness! They're making every mistake in the book!'" I did indeed feel that way by page 173. Here's my sense of what went wrong, based on the account in the book:
* They did not have one architect (Brooks makes a very good point about why there should be a single person)
* They didn't work out the architecture in advance, and they went back and changed it many times
* They had a very flexible data concept/model, in which items change type frequently in a user-visible way, which they didn't work out until quite late
* They kept changing their mind about their UI substrate: wxWidgets? Mozilla internals?
* The software ecosystem changed around them after all those years, and using a Web UI now made sense, but it was too late for them
* They could not figure out what database technology to use (they finally decided not to use the Zope Object Database, although their reasons for that decision don't impress me)
* It was originally supposed to be peer-to-peer, but they could not figure out how to make that work, so they changed it to be server-based, a major change very late in the design
* They had to design a security model for all this
* It was all extensible, which is great but takes a lot of work to do right
* There were complicated semantic issues with sharing, "chain-sharing", etc. which were not worked out early.
* They wanted to have extensional and intensional collections, like iTunes, but also wanted to combine the two (the so-called "exclude Bob Marley" feature), which makes the semantics a lot harder
* Their internal terminology was inconsistent, symptomatic of a lack of architectural integrity
* They did serious requirement analysis only late in the project
* It was putatively open-source, but it was much too immature to really get outside developers involved
* They were too focused on doing "the right thing" instead of getting something out fast; see Gabriel's "Worse is Better" paper
* They released much too early, partly because of the glare of publicity due to Mitch Kapor's involvement
I see that they are still in "preview" releases. This has been going on for six years now! They have no projected release date for 1.0. It will be free, under the Apache license.
I have always wanted a good personal information manager, and a lot about Chandler looks very promising. Someday I may be a happy user. Right now, I think I'll wait until release 1.0.
I hope they have moved beyond the problems illustrated in the book and are running smoothly now. Kudos to the whole Chandler team for letting Rosenberg be so involved, being so honest with him, and letting him produce this unique, spectacular book.
Customer Rating:
Summary: Excellent story about the complexity of software development
Comment: If you are interested in software development...read this book.
If you aren't interested in software development...read this book.
If you've always wondered why software development is such a tough thing to manage and predict completion...read this book.
Did I say that you should read this book? :)
The book is not a detailed "how to"...it is a story that follows the development of "Chandler", a software product that was going to 'change the world'....but of course, the product never really materialized. The team worked on the product for more than 5 years and never produced what the founder, Mitch Kapor of Lotus 1-2-3 fame, had envisioned. 5 years, over 4700 bugs and two dozen programmers with very little to show for the effort.
Take a look at the Related Articles below...you'll see that Chandler is just now coming to be a "1.0" release after 7 years of development. Interested story and a great book.
If you find yourself perplexed about the process of software development, this book might help you move a little closer to understanding the complexity of this process.
Definitely recommended reading.
Customer Rating:
Summary: Depressing
Comment: After the first chapter I was skeptical. After the second I was depressed.
This is the kind of humour that I imagine really motivates low level techies who assemble computers for a living and makes them feel superior to the entire world because they can plug in a video card. Remember the tech guy that insults you from "Saturday Night Live"? To be clear its intellectual arrogance about stuff that's not that intellectual.
This is the field I'm going to base my life's work on. I don't need to read how hard it is. I want to read about successful projects and how ppl coded great applications. I mistook this book for "Beautiful Code" which I'm guessing is a lot closer to something I'd like to read.
I wish I could send this book back but it was bought as a gift for me in an airport. Its seriously demotivating for an aspiring programmer and I imagine that the author is quite pompus for somone stating some pretty obvious stuff.
|
|
|
|
|
|
|
|
