Dreaming in code

About the book

Dreaming in Code is a reported account of the Chandler project, an open-source effort to build a tool for organizing email, calendars and notes. Rosenberg traces how a group of experienced programmers set out to make something new and found themselves negotiating schedules, specifications and shifting priorities. The book uses that single project to examine a wider puzzle: why software development resists the tidy planning that other kinds of engineering take for granted.

The narrative moves between the team's working life and the history of software engineering as a discipline. Rosenberg draws on figures and debates from the field to explain ideas such as complexity, estimation and the gap between what users ask for and what builders can deliver. The result is less a technical manual than a story about people trying to coordinate thought and labor under uncertainty.

The book captures a particular moment in open-source culture and project management. Its concerns about missed deadlines and scope creep remain recognizable, though the specific tools and companies it describes belong to their time.

How to read it

Approach the book as narrative reporting rather than instruction. Rosenberg builds his argument through scenes, conversations and the project's setbacks, so the ideas emerge from the team's experience. Readers who want a tidy methodology will need to follow the story's detours and tolerate unresolved questions.

The prose is accessible to non-programmers, though some passages assume familiarity with software terms. Watch how Rosenberg uses the Chandler team as a case study and where he steps back to discuss the field more broadly. The book rewards attention to its examples rather than a search for a single lesson.

Who it suits

This suits readers curious about how software gets made and why large projects go awry, including managers, students and people who work alongside developers. It will appeal to anyone interested in open-source communities and the human side of technical work. Readers seeking a practical project-management guide should look elsewhere.

Reading considerations

The book is anchored in one project and one period, so its lessons are illustrative rather than universal. Chandler's outcome and the tools described may feel dated to readers familiar with later software. Treat its generalizations about development as questions to test against other projects.