Scott Rosenberg follows an ambitious software development team of Chandler led by Mitch Kapor who was already a big name in the valley after making $200MM from Lotus and later co-founding Electronic Frontier Foundation. Kapor is largely fascinated by the success of Open Source with Linus Torvald's personal project that turned into the mammoth software project Linux. It broke down multiple stereotypes and theories of software development, primarily that of Brook's Law (Fred Brooks' Mythical Man Month) that adding manpower to a software project delays it, which is a recurring meme through the book. Dreaming in Code is less about Chandler and more about addressing the questions like, "Why can't we make software like we make bridges?" which delve more into philosophy of software development than the specific project in sight. This outlook also makes Rosenberg sometimes loose sight of the ordinary and make mountain out of a molehill by exaggerating simple design decisions in the process into big questions about existence and creation.
Chandler keeps on missing deadlines through the book. Halfway through it started getting on my nerves. There were times when I felt like stopping and writing to Kapor right away. One could argue that Chandler wouldn't have been a vapourware if they had chosen the web over python but that's exactly the kind of information that development team didn't have access to when they made the decision and thus led them astray. In a way, this changing topology is what makes making solid structures in software industry a challenging problem. OSAF is incredibly ambitious and stoic about their aspirations to take forward the ideas of Ted Nelson and Doug Engelbart.
Overall, I found it a great introduction to this industry as an outsider. Although the book doesn't expect the reader to be a programmer, it'll definitely help. Dreaming in Code encourages discussion which is why this will give you a lot of fodder to put on the coffee table with any software engineers you may know.