Software as History: Towards an Historical Understanding of the Software Crisis

Software as History explores the origins and development of what became known as the "software crisis" in the computer industry of the 1950s-1970s. Through archival research and organizational analysis, Ensmenger traces how software development evolved from a craft-like practice into an engineering discipline. The book investigates key factors that contributed to ongoing challenges in software production, including labor shortages, reliability issues, and struggles to establish professional standards. The narrative follows the perspectives of programmers, managers, and industry leaders as they grappled with the growing complexity of software systems. Major conflicts emerge between differing approaches to software development methodology and competing visions for the future of computing. The text examines how these technical and organizational tensions shaped both the industry and the emerging profession of software engineering. At its core, this study reveals broader themes about the relationship between technological change and professional identity, while raising questions about the nature of engineering disciplines and organizational management that remain relevant to modern software development.

There are not enough internet reviews to create a summary of this book. Instead, here is a summary of reviews of Nathan Ensmenger's overall work: Readers frequently cite Ensmenger's clear writing style and ability to explain complex technical history without getting bogged down in jargon. His "Computer Boys Take Over" receives particular attention for making programming history accessible to non-technical audiences. What readers liked: - Detailed research and extensive primary sources - Balance of technical and social history - Clear explanations of how gender shaped early computing - Connection of historical patterns to current tech industry issues What readers disliked: - Academic tone in some sections - Limited coverage of international developments - Focus primarily on US corporate computing - Some repetition between chapters Ratings across platforms: Goodreads: 4.0/5 (87 ratings) Amazon: 4.3/5 (28 ratings) One reader noted: "Finally, a computing history that explains why the field evolved the way it did, not just what happened." Another mentioned: "Could have used more international perspective, but the US corporate history is thoroughly researched."

The Computer Boys Take Over by Thomas Haigh This text examines the evolution of computer programming as a profession and its impact on organizational structures from the 1950s to 1990s.

Programmed Inequality by Marie Hicks This work traces the connection between British computing labor practices, gender discrimination, and the nation's technological decline from 1944-1979.

The Bug by Ellen Ullman This historical narrative follows debugging culture and programmer psychology through the lens of a Y2K-era software crisis.

From Counterculture to Cyberculture by Fred Turner The book maps the transformation of computing culture from military-industrial origins to its integration with countercultural movements and Silicon Valley ideologies.

Code by Lawrence Lessig This work presents the relationship between software architecture, legal frameworks, and social control through computing history.

📚 Despite the term "software crisis" being coined in 1968, many of the core challenges it described—project delays, cost overruns, and reliability issues—remain prevalent in software development today. 💻 The book reveals that early computer programmers were often women, particularly in the 1940s and 1950s, with programming initially being considered clerical work similar to typing or telephone operation. 🎓 Author Nathan Ensmenger is an Associate Professor at Indiana University's School of Informatics, Computing, and Engineering, where he specializes in the social and cultural history of computing. ⚡ The transformation of programming from a craft-like activity to a professional engineering discipline was largely driven by corporate managers seeking to gain more control over the software development process. 📊 During the 1960s, studies showed that the ratio of programming costs to hardware costs was rapidly inverting—from 20:80 in the early 1960s to 80:20 by the decade's end, creating new pressures on the industry.