A History of Modern Computing
Source: https://mitpress.mit.edu/9780262532037/a-history-of-modern-computing/ ↗
Ceruzzi's textbook became the standard academic reference for the history of computing from the 1940s through the early internet era.
As a curator at the Smithsonian National Air and Space Museum, he had direct access to the machines and the people who built them, which gives the book a materiality that purely intellectual histories lack.
The narrative moves from ENIAC and UNIVAC through the minicomputer revolution, the microprocessor, the personal computer, and the emergence of networking, treating each transition not as inevitable progress but as a series of contingent choices made by specific institutions under specific pressures.
Ceruzzi is particularly strong on the business and organizational dimensions — how IBM's decisions shaped an industry, how the minicomputer created new kinds of companies, how software became a separate commodity.
The second edition, published in 2003, remains useful as a foundation even though it predates the smartphone era and the cloud.
Central argument
Ceruzzi argues that the major transitions in computing history — from mainframes to minicomputers to microprocessors to networked personal computers — were not the inevitable march of technological progress but the outcome of contingent decisions made by specific organizations under specific competitive and institutional pressures. IBM's strategic choices, for instance, didn't just reflect the market; they constituted it, shaping what kinds of companies could exist and what kinds of products were conceivable. A secondary but persistent thesis is that software's emergence as a separable, commodifiable layer was itself a historical accident rooted in business decisions, not a natural property of the technology.
Critique
The book's institutional and organizational lens, while genuinely illuminating, can reduce individual engineers and user communities to supporting actors in a drama driven largely by corporate strategy and procurement decisions — understating how grassroots technical cultures (the hobbyist networks, the university labs, the counterculture computing movements) generated pressures that institutions then had to respond to rather than simply direct. There is also a structural limitation acknowledged by Ceruzzi himself: the 2003 cutoff means the book cannot account for the platform dynamics, network effects, and software-as-a-service architectures that would define the next two decades, leaving its organizational lessons partly stranded before the conditions that most CPOs actually operate in today.
Why it matters for product
Ceruzzi's central insight — that industry structure is made, not found, through a sequence of organizational bets under uncertainty — is directly applicable to product leaders deciding whether to build platform capabilities, open APIs, or vertically integrated experiences: the choice is never purely technical, it forecloses or enables entire categories of future products. His account of how the minicomputer created new organizational forms (smaller teams, closer to the user, faster iteration) is a historical precedent for understanding why cloud infrastructure didn't just change delivery costs but reorganized who could own a product decision and at what cadence.