Dreaming in Code

Dreaming in Code follows the ambitious journey of Mitch Kapor's Open Source Applications Foundation as they attempt to create Chandler, a revolutionary calendar application. The narrative tracks a team of programmers over three years as they face the complexities and challenges of software development. Rosenberg embeds himself within the development team, documenting their daily struggles with coding, collaboration, and project management. The book interweaves their story with essential context about software development principles, drawing from foundational works like The Mythical Man-Month and examining why creating software remains such a difficult endeavor. The author chronicles OSAF's effort to build something truly innovative in the open-source space, while illuminating the human dynamics of large-scale software projects. The team confronts technical obstacles, scheduling conflicts, and the fundamental uncertainty inherent in creating complex systems. At its core, this is a book about the gap between technological dreams and practical reality, exploring why software projects so often fall short of their initial vision. Through the lens of one project, it reveals universal truths about innovation, collaboration, and the persistent challenge of turning ideas into working code.

Most readers describe the book as an authentic look into the challenges of software development through the story of Mitch Kapor's Chandler project. The narrative mirrors many readers' own experiences with failed or delayed software projects. Readers appreciated: - Clear explanations of technical concepts for non-programmers - Realistic portrayal of why software projects go wrong - Historical context and industry examples - Writing style that makes technical material engaging Common criticisms: - Story becomes repetitive in later chapters - Too much focus on the Chandler project's failures - Some technical explanations go into unnecessary detail - Pacing slows in the middle sections Ratings: Goodreads: 3.7/5 (2,800+ ratings) Amazon: 4/5 (120+ reviews) Multiple readers noted the book could have been shorter. One Amazon reviewer wrote: "The first third is fantastic, but it loses steam." Several Goodreads reviews praised the author's ability to "capture the human drama of coding" while maintaining technical accuracy.

The Soul of a New Machine by Tracy Kidder This narrative follows a team of engineers racing to build a next-generation computer in the 1970s, documenting the technical challenges and human drama inside the nascent computing industry.

Coders at Work by Peter Seibel Through interviews with fifteen programming pioneers, this book reveals the thought processes, approaches, and experiences behind significant programming achievements and innovations.

The Mythical Man-Month by Fred Brooks Drawing from experiences managing IBM's System/360 project, this book examines the complexities and challenges of software development through real-world case studies and observations.

Code Complete by Steve McConnell This comprehensive examination of software construction presents the practical realities of creating complex software systems through detailed examples and case studies from real projects.

Hackers: Heroes of the Computer Revolution by Steven Levy The book chronicles the history of computer programming through the stories of programming pioneers who shaped the digital revolution from the 1950s to the 1980s.

🔹 Mitch Kapor, the central figure in the book, previously created Lotus 1-2-3, one of the first killer apps that helped establish the IBM PC as a business standard in the 1980s. 🔹 The Chandler project, which the book chronicles, ultimately didn't achieve its ambitious goals despite $5 million in funding and years of development—exemplifying the "mythical man-month" principle discussed in the book. 🔹 Author Scott Rosenberg co-founded Salon.com, one of the first major online magazines, and spent years as a technology journalist before writing this deep dive into software development. 🔹 The book's title references Frederick P. Brooks' seminal work "The Mythical Man-Month," which established that adding more programmers to a late software project makes it later. 🔹 The programming team's struggles documented in the book helped popularize the term "software crisis," highlighting how even experienced developers frequently struggle to estimate project timelines accurately.