The Computer History Museum’s 2017 report shows how preserving the history of computing involves more than collecting machines. The work also includes protecting software, documenting the people who created and used technology, and explaining how computing has changed society. For engineers, system integrators and operations leaders, that perspective offers a useful reminder: today’s technical systems become tomorrow’s history, and their context matters as much as their hardware.
Why the Computer History Museum looks beyond hardware
A computer is not defined solely by its physical components. Software determines what a system does, while the decisions, teams and circumstances behind that software help explain how it developed and why it mattered. The Museum’s Center for Software History, launched in 2017, was established to collect and preserve historical software and related archives, and to interpret software’s effects on society.
The center’s work combines several forms of preservation: collecting artifacts, preserving code, recreating systems that can run, and recording oral histories. These activities address different parts of the historical record. A physical artifact can show how a technology was built; preserved software can reveal how it behaved; and interviews and documents can capture the experience and reasoning of the people involved.
The report describes software as something that must be understood in action as well as in code. That distinction is relevant wherever technical systems are used: a program’s significance often becomes clearer when it is connected to its operating environment, users and purpose. The center planned to make this history accessible through research, publications, exhibitions and public events.
Exhibitions connect computing concepts to real applications
The Museum opened Make Software: Change the World!, a 6,000-square-foot exhibition designed around software applications and their effects. Rather than relying primarily on a chronological timeline, the exhibition used case studies to connect technical ideas with broader social impact. Its examples included Photoshop, MP3, MRI, car-crash simulation, Wikipedia, texting and World of Warcraft.
The exhibition also included the Stata Family Software Lab, where visitors could explore coding hands-on. Its approach illustrates a central challenge in technical communication: explaining software requires making an abstract process tangible. Interactive demonstrations and specific applications can help visitors see how code relates to activities and outcomes they recognize.
For industrial organizations, the underlying lesson is not that every system needs a public exhibition. It is that technical knowledge is easier to retain and share when it is connected to concrete examples. Documentation that explains both how a system works and what it enables can be more informative than a list of components or milestones alone.
Preserving the people and decisions behind technology
Oral histories are another important part of the Museum’s preservation strategy. The 2017 report lists interviews with people whose work spanned programming, computer architecture, software design, human-computer interaction and entrepreneurship. These accounts add perspective that may not be apparent from an artifact or technical document by itself.
One example is Leslie Lamport, whose work on reliability in distributed computer systems became fundamental to modern distributed computing. Another is Ann Hardy, whose career included work on timesharing systems and operating systems. Their interviews preserve accounts of technical development while documenting how ideas and careers unfolded over time.
The Museum also recognized computing contributors through its Fellow Awards. The 2017 honorees included Margaret Hamilton, recognized for her software work on Department of Defense and NASA Apollo missions and contributions to software engineering; Alan Cooper, recognized for work in visual development environments and interaction design; Cleve Moler, creator of MATLAB; and Larry Roberts, whose contributions included a role in ARPANET development. The program paired recognition with the collection of documents and personal papers, helping preserve records alongside individual achievements.
Collections reveal different paths through computing history
The report’s featured artifacts show how varied the material record can be. A Tektronix Model 4052 combined a vector display with a built-in BASIC interpreter. The Salisbury Hand, developed as part of Kenneth Salisbury’s mechanical-engineering research, used three fingers, 12 motors and independent joint control. A collection of Cromemco product drawings documents engineering through schematics, circuit-board artwork and mechanical plans.
Other objects illuminate the relationship between technology and its broader context. A PDS 1020 brochure described digital computing as a way to move technical staff beyond repetitive calculation and toward creative engineering problems. The Computer History Museum also acquired the Google Founders Collection, bringing together artifacts, documents, photographs and video from the company’s first decade.
These examples underline why preservation benefits from multiple formats. Hardware, drawings, software, business records and first-person accounts each provide different evidence. Together, they can show not only what a system was, but how it was designed, used and understood.
Education turns preserved knowledge into shared understanding
The Museum’s education program connected collections and exhibitions with tours, workshops and programs for students, families, educators and community groups. The report records student tours, school visits and hands-on activities including coding workshops. Construction also began on a new education center intended to support classes, workshops, live events, presentations and research into computing technology and learning.
This educational work reflects the Museum’s broader aim: to make computing history meaningful to people with different backgrounds and levels of technical experience. For industrial organizations, the same principle applies to internal knowledge transfer. Training is more effective when it links technical processes to real tasks, decisions and outcomes rather than presenting technology in isolation.
Practical implications for today’s technical teams
The Computer History Museum’s 2017 initiatives point to several useful practices for organizations managing complex technical systems:
- Preserve context alongside equipment. Keep relevant software, drawings, documents and system records with the hardware they describe.
- Capture practitioner knowledge. Interviews and documented experience can explain decisions that formal specifications may not cover.
- Make systems understandable through examples. Connect technical concepts to applications, users and operational outcomes.
- Plan for long-term access. Preserving code and recreating running systems can help future audiences examine how technology worked, not just how it looked.
These points do not guarantee that every legacy system can be recreated or that every technical record will remain usable. They do show why preservation requires more than storing physical objects: it involves collecting, documenting and interpreting the relationships between technology and the people who shaped it.
Conclusion
The Computer History Museum’s 2017 report presents computing history as a combination of machines, software, people and social impact. Its exhibitions, research, collections and education programs worked together to make that record accessible. For industrial automation teams, the practical takeaway is to treat technical knowledge as an asset worth preserving: document how systems operate, retain the materials that explain their design, and capture the experience of the people who maintain and use them. That context can help future teams understand not only what a system is, but how it came to be.