Engineers often meet the present in its most compressed form: a framework, an API, a cloud service, a board, a model, a protocol. Everything seems available now, as if technology were only a succession of updates. History of Computer Systems teaches the opposite. It shows that computing is cumulative, that technical environments are layered, and that every generation of tools sits on older scientific, industrial and political decisions.
01 Why history belongs in an engineering curriculum
At DSTI, we follow a classic scientific and engineering conviction: humanities belong inside technical education. A good engineer is not only someone who can implement a method. A good engineer can also situate a method, recognise its assumptions, and understand the historical horizon from which it comes. History does not weaken technical formation; it gives it depth.
That matters especially in computing because the field moves quickly but remembers more than it seems. The fashionable surface may change, yet many of the central structures of digital life remain inherited: programming paradigms, operating-system ideas, database models, network architectures, administrative systems and even organisational habits.
02 Computer systems are layered inheritances
The course makes visible a reality every practitioner eventually encounters: technology is built on layers of earlier advances. Students can think of the 1970s alone and immediately meet foundations that still shape contemporary practice — the C language, UNIX, the relational model, packet-switched networking, microprocessors and new software-engineering habits. These are not museum pieces. They are still embedded in the present.
The same is true of enterprise computing. Mainframe environments, virtualisation logic, COBOL, PL/I, JCL and other legacy ecosystems continue to operate critical infrastructures. What later appeared in micro-computing and what is now called cloud computing often replicate, repackage or redistribute capacities that were already developed in earlier large-scale systems. History gives students a map of these continuities.
Technical memory matters
Many supposedly “new” environments are better understood as reorganisations of older capabilities. That is why historical literacy makes technical transitions easier to read.
03 AI, networks, large-scale data systems and connected objects all have genealogies
Artificial intelligence is often described as if it began yesterday. In reality, AI is a long conversation between symbolic reasoning, statistics, optimisation, cybernetics, machine learning and the availability of computing power and data. Networks, too, are not only cables and protocols: they are institutional agreements, standards bodies, military and academic histories, and later commercial infrastructures.
Large-scale data systems and connected objects should also be read historically. Databases evolve from distinct theoretical and engineering traditions. Distributed systems emerge from practical needs for resilience, throughput and coordination. Connected objects belong to a wider story of embedded systems, telecommunications, industrial control and platform integration. When students see these genealogies, contemporary buzzwords become intelligible.
04 Technology is also social and political history
The course is not a parade of machines. It places computing, AI, networks, data infrastructures and connected devices in their social and political contexts. Who funded key developments? Which institutions standardised them? How did national strategies, industrial competition, public administrations and military priorities influence the direction of innovation?
Those questions matter because engineering is never isolated from society. System design shapes labour, administration, security, access to knowledge and even citizenship. Understanding the historical relationship between technology and power helps students develop judgement — especially when they later work on data governance, platform design, cyber security or AI deployment.
05 Why Pr Pierre Mounier-Kuhn is an especially relevant voice
DSTI is fortunate to have this course taught by Pr Pierre Mounier-Kuhn, an authoritative historian of computing whose work is widely recognised. His trajectory brings together historical depth, international visibility and a rare capacity to explain the specific place of France in the broader history of digital technologies.
That perspective is particularly valuable. France’s attempts to position itself in computing and the digital sector reveal how technical ambitions, state strategy, industrial structures and scientific ecosystems interact. For students in France — but preparing for international careers — this is an excellent way to understand that digital history is not abstract. It is also institutional, territorial and strategic.
06 What BSc students gain at DSTI
Students leave the course with more than chronology. They gain conceptual orientation. They become better at connecting present-day architectures to prior generations of systems. They understand why some legacy technologies survive, why standards matter, why infrastructure decisions endure, and why the future of AI or cloud engineering cannot be understood without their pasts.
That is precisely why the course belongs in the BSc programme. It complements programming, systems, mathematics and engineering practice by giving students a wider frame. It helps them read innovation without naïveté, recognise hype without cynicism, and imagine future technical change with better historical grounding.
07 What the course states, in one sentence
History of Computer Systems studies the development of computing, AI, networks, large-scale data systems and connected objects in their social and political contexts. At DSTI, we teach it because engineers should not inherit technology blindly. They should know where it comes from, what it carries forward and what responsibilities come with building its next layer.
The result is an engineer with memory as well as skill — someone better equipped to work on present systems and more lucid when helping define future ones.
Editorial note. This DSTI TechBlog article explains the educational rationale for the BSc course “History of Computer Systems”. It is an editorial presentation of the course and its importance within the curriculum; it does not attribute the editorial wording to Pr Pierre Mounier-Kuhn.