Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
by Scott Rosenberg
|
|
Sign in to Goodreads to see your friends' reviews of Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software.
discuss this book
friend reviews (0)
To see what your friends thought of this book, please sign up.
lists with this book
This book is not in any lists. Go add it to a list.
other reviews (showing 1-20 of 254)
Read in June, 2008
Dreaming In Code
----------------
This book was given to me as a present last Christmas with "Beautiful Code". Usually books about software engineering as a process bore me, most texts treat the subject dryly and are more about advocating the author's own process or beliefs than providing any kind of real insight as to how software is built by companies today. So when I receieved this as a present (apparently it was recommended by Amazon with the text above), I shelved it adding ...more
----------------
This book was given to me as a present last Christmas with "Beautiful Code". Usually books about software engineering as a process bore me, most texts treat the subject dryly and are more about advocating the author's own process or beliefs than providing any kind of real insight as to how software is built by companies today. So when I receieved this as a present (apparently it was recommended by Amazon with the text above), I shelved it adding ...more
Like this review?
yes
add a comment
Read in April, 2008
Unfortunately this book is quite boring. I have no idea why it sells so well. It's too fluffy for the technical reader who might be seriously interested in the issues, and it seems too heavy for the casual reader. So who's reading it? Well, I guess I am, because of some of the press it has gotten. Overblown if you ask me.
OK, for some reason I've read more computer science than the average Ph. D. and I've actually managed some computer projects in an era (1980's) when my company was still jus...more
OK, for some reason I've read more computer science than the average Ph. D. and I've actually managed some computer projects in an era (1980's) when my company was still jus...more
Like this review?
yes
add a comment
bookshelves:
read-in-2008
Read in April, 2008
In an effort to discover why software development is hard, Scott Rosenberg, one of the founders of Salon.com, spent time embedded with the development team for Chandler, a personal information management desktop application intended to compete with Microsoft Outlook. In tracing the team's progress - or rather its stunning lack of progress - over the 4 years between 2001 and 2005, Rosenberg is partially successful in illuminating the various pitfalls that can waylay this kind of effort.
Though...more
Though...more
Like this review?
yes
add a comment
Read in September, 2006
Dreaming in Code was an awful lot of fun, a good uplifting "Chicken Soup for the 3l33t Soul" kinda thing. I bought copies for everyone in my office. On the other hand, the first two chapters (after a strong, catchy Introduction, sigh) are downright painful, any code company that allows loud, messy dogs into the bowels of their austere Rigorium is obviously destined to fail, and what's up with all these girls writing code? I don't know how they do it on the West Coast, but I quote Ed Po...more
Like this review?
yes
(1 person liked it)
add a comment
This book had some interesting anecodetes, but overall, it sounded like a software engineering after-school special. Rosenberg made the software development lifecycle sound like it's as mystical experience, akin to studying the Kabballah (it's not), and he missed the mark on defining certain programming concepts (eg "late-binding") in a way that made me suspect he was trying to overdress his comprehension of the subject.
The truth is, this book does not describe a typical software ...more
The truth is, this book does not describe a typical software ...more
Like this review?
yes
(1 person liked it)
add a comment
bookshelves:
tech-books
Read in January, 2008
The book follows the development of an open-source application, Chandler -- a personal information manager (PIM) conceived with the intent of being a Microsoft Outlook killer. The author is both a programmer and one of the founders of and writers for Salon.com. With this background, he covers the fits and starts of the project in both an entertaining and insightful manner. The book expands on the Chandler project to discuss development in general -- the choices made during design and implementat...more
Like this review?
yes
add a comment
Read in March, 2008
While this book sounds like it is targeted for programmers, it really is written to the non (or semi) tech crowd. If you (or someone you know) needs/wants to understand why quality software, delivered quickly, is so difficult (or impossible) to achieve then this book will help. For tech types, it will provide a deja vu of most of your professional past that gives you the sort of twist in the stomach feeling you get from a pleasant roller coaster ride. It is a quick and pleasant read, contains so...more
Like this review?
yes
add a comment
bookshelves:
software-engineering
Read in December, 2007
The author intended to write a book about a successful software project but instead got a multi-year, spiralling project experience. He was imbedded with the software team and relates the successes and roadblocks encountered by them. In a third-person sort-of-way, he experienced what many software team members experience: a protracted, question-laden journey where organizational influences and individual's agendas can wreak havoc on an ill-defined software goal.
Hmm. As an industry insider, thi...more
Hmm. As an industry insider, thi...more
Like this review?
yes
add a comment
bookshelves:
non-fiction
Read in September, 2007
recommends it for:
non-programmers
I have a degree in computer science, and my thesis in remote sensing involves a lot of programming. Despite that, I wouldn't ever describe myself as a programmer. I can do a little programming, I can do a little admin work, but I am not a normal computer professional.
It was refreshing to see other people having the same issues I do. I have an idea...I spec out how long it ought to take......and it is consistently only 1/2 (at best!) the time I need.
Computers are either insanely complex o...more
It was refreshing to see other people having the same issues I do. I have an idea...I spec out how long it ought to take......and it is consistently only 1/2 (at best!) the time I need.
Computers are either insanely complex o...more
Like this review?
yes
(1 person liked it)
add a comment
Has a copy to sell/swap
Scott Rosenberg captures many of the challenges faced in software development projects, which is amazingly accurate. The book focuses in on the development of an open source PIM (personal information manager) system over the course of several years. The book does have a few faults though; there are a few chapters of the book that seem somewhat out place and the book never truly concludes - it should have offered some advice, insight, or reflection from the OSAF team. The software being develop...more
Like this review?
yes
add a comment
bookshelves:
nonfiction,
nontech
Read in May, 2008
Mostly disheartening. This wasn't a very inspirational or enlightening read for a techie who already reads other process books, articles, and blogs. I'd like to say it would be better as a read for non-techies, but I think they'd mostly come away from it still thinking we just need to get our heads out of our butts and do things right.
I think it's a relatively good, fair, and balanced book, but I think people outside the industry still just won't understand what makes software so hard withou...more
I think it's a relatively good, fair, and balanced book, but I think people outside the industry still just won't understand what makes software so hard withou...more
Like this review?
yes
add a comment
Read in October, 2007
recommends it for:
code monkeys
A very deep look into the chaos that is the software development lifecycle. Shows how software engineering is less engineering and more of an art. And it also brings home the point that software development simply cannot be managed using today's standard practices. You simply cannot speed up a project by throwing money and/or people at it, nor could you ever make a decent estimate of the completion date.
Despite the feeling of doom and gloom this book gives, however, I came away desperatel...more
Despite the feeling of doom and gloom this book gives, however, I came away desperatel...more
Like this review?
yes
add a comment
bookshelves:
have-read-and-loved-it
Read in May, 2008
I work in an office that makes software. This book has helped me grasp the dynamics of the personalities in the office. It has helped me understand the friction, and the impediments to writing good software. I have given this book to a friend at the office. Hopefully he will understand that time estimates for fixing bugs is more art than science. If I was a rich man, I would buy a copy of this book and put it on everyone's desk at the office that I work at. That is how applicable I found t...more
Like this review?
yes
add a comment
bookshelves:
computers
Read in November, 2007
It's been about seven months since I read Dreaming in Code, and I can't remember much of anything about it. But that's sort of the point, I guess. I mean, nothing happens -- or at least not much -- underscoring the author's thesis that writing great software is really hard, and writing great software quickly is nearly impossible. Does that sort of thesis, though, deserve a whole book? Hmmm...
Like this review?
yes
add a comment
This book is really pretty great!
The author stayed with a company for three years as they try to build a software program, chronicling the ups & downs.
He does a great job of addressing why the progress is so slow, the history of programs that lead up to current debates / decisions, and placing the entire process in the context of explaining why some people are just motivated to do this.
The author stayed with a company for three years as they try to build a software program, chronicling the ups & downs.
He does a great job of addressing why the progress is so slow, the history of programs that lead up to current debates / decisions, and placing the entire process in the context of explaining why some people are just motivated to do this.
Like this review?
yes
add a comment
Read in January, 2008
This is definitely written for the lay-person, not a coder, but if someone you love writes code for a living, this will definitely give you a better idea what it is they're doing! My only problem with it is that it makes software development seem like a real drag, when for those of us who do it for love, it is exhilarating.
Like this review?
yes
add a comment
Read in May, 2008
Pretty good read about the difficulties of software. "Software is hard," as the author and many people he quotes says, and it's true. The book does a good job of explaining just why this is. Vindication of why my brain hurts at the end of most of my work days.
Like this review?
yes
add a comment
Read in February, 2008
Discusses somewhat of how being a programmer works. Really interesting reading. Kinda gets boring in the middle when it goes into the different methodologies for running a software project but over all very good read.
Like this review?
yes
add a comment
Interesting coverage of the Chandler open source project in particular and software development in general. As a software developer myself, I enjoyed it, and I like to think my projects compare favorably with Chandler.
Like this review?
yes
add a comment
bookshelves:
programming
Read in April, 2007
Entertaining, but flawed. The level of detail the author wrote at is less than what a programmer would be intereted in, but more detailed than an average reader would enjoy. So who is the audience exactly?
Like this review?
yes
add a comment
book data (includes all editions)
avg rating (all editions): 3.62 (148 ratings) avg rating (this edition): 3.61 (140 ratings) number of reviews: 34Goodreads is hiring!
If you like books like these and love to build cool products, we may be looking for you.
Check it out!
















