Blog

Who was Maurice Wilkes, and why does Cambridge remember him?

Meet the Cambridge computing pioneer behind EDSAC, explore the work that followed, and understand the connection with the building at St John's Innovation Park.

Exterior of the Maurice Wilkes Building at St John's Innovation Park, Cambridge

Who Maurice Wilkes was

Maurice Wilkes was a Cambridge computer scientist whose work helped make electronic computing a practical service for researchers. He is closely associated with EDSAC, the stored-program computer built at the University of Cambridge after the Second World War. The name on the building at St John's Innovation Park therefore points to a much longer local story than the building's own development.

Wilkes was born in 1913 and came to Cambridge in 1931. According to the University's Department of Computer Science and Technology, he studied mathematical physics before undertaking experimental research at the Cavendish Laboratory. His work on radio waves and the ionosphere introduced him to difficult calculations and to the methods available for carrying them out. Computing was not a sudden change of subject so much as a response to a problem he already understood: how could a university calculate more reliably and usefully?

After wartime service, Wilkes returned to Cambridge in 1945 and took charge of the Mathematical Laboratory. The formal directorship is dated slightly differently across the University's own accounts, so it is clearer to describe the transition than to compress it into a single job title. At the time, the laboratory's purpose was to support research across the university. A machine that existed only as an impressive demonstration would not have met that purpose. Its programmes needed to run, its operators needed methods they could repeat, and researchers needed access to the results.

That practical focus explains why Wilkes remains relevant beyond a list of dates and awards. His contribution was not simply to help build a computer. He helped organise a way for a community of scientists to use one.

A laboratory for useful computing

The Mathematical Laboratory began before the electronic computer age. Cambridge's own history dates its foundation to 1937, when mechanical calculation and a university computing service were central concerns. The war interrupted that development. When civilian work resumed, the possibility of an electronic stored-program machine changed what the laboratory might offer.

In 1946 Wilkes attended the Moore School lectures on electronic computers in Philadelphia. Cambridge's short biography records that, after returning, he set about building EDSAC. The visit mattered because it brought new design ideas into an institution that already had a concrete need for computation. Wilkes and his team could ask a more useful question than whether such a machine was theoretically possible: what would it take to make one dependable enough for everyday academic work?

That question involved people as well as hardware. A research service needs programmes that others can understand, procedures for finding errors and a way to share limited machine time. The University of Cambridge's Whipple Museum describes EDSAC's design as deliberately practical, using reliable and proven features. The choice was not glamorous, but it helped the team bring a functioning machine into service.

It is easy to retell early computing history as a race to identify a single “first” computer. That label depends on what is being measured: electronic operation, stored instructions, general purpose, practical use or public availability. For a reader of this site, the more important point is specific. Wilkes's Cambridge team built a machine intended to support real research, and then worked on the programming practices needed to use it.

What EDSAC changed

EDSAC stands for Electronic Delay Storage Automatic Calculator. Cambridge's laboratory history records its first logged programme on 6 May 1949: a calculation of the squares of integers. The task sounds modest, but the event demonstrated that a programme held in the machine's memory could direct a useful calculation. Researchers could then prepare different programmes for different questions instead of treating the equipment as a fixed-purpose device.

The machine occupied a room and required specialist attention. It was nothing like a modern laptop. Its significance lies in the relationship between the laboratory and its users: EDSAC was built as a service for university work. The Whipple Museum notes that its output came to be used across Cambridge research. The promise of stored-program computing became meaningful when a scientist could bring a problem to the laboratory and receive a result that advanced their work.

This also changed the demands placed on programming. If more people were to use the machine, instructions had to be planned, recorded and checked. In 1951 Wilkes and two colleagues published a book on preparing programmes for electronic digital computers. Cambridge's biography identifies it as the first book on computer programming. The achievement is worth understanding in its own right: a working machine is only one part of a computing service; repeatable methods let others make use of it.

Visitors may encounter EDSAC in more than one Cambridge location or exhibition. The historical machine belonged to the University's Mathematical Laboratory. The Maurice Wilkes Building is a later building at St John's Innovation Park. They are connected by the story of Cambridge technology and Wilkes's name, not by an assertion that EDSAC was housed in the present-day office building.

Work beyond EDSAC

Reducing Wilkes to EDSAC would miss the way his questions evolved. Once a computer worked, designers still had to make it easier to control, faster to use and better connected to other machines. The University's biography places his proposals for microprogramming in the early 1950s. In broad terms, microprogramming provided a structured way to describe how a processor should carry out its more basic operations. Its later use in industry shows the distance his ideas travelled from the Cambridge laboratory.

The same biography records a 1965 paper on cache memories. A cache addresses a persistent difficulty in computing: the processor can work faster than data can always be fetched from slower storage. Keeping frequently needed information close at hand can reduce the wait. That is a simplified explanation of a broad design problem, not a claim that Wilkes alone invented every later form of cache used in today's machines.

Wilkes also considered networks. The Cambridge biography describes a 1970s design study that led to the Cambridge Ring and later work on a distributed system with Roger Needham. These projects reflected another practical shift. When computers served more people and tasks, moving information between systems mattered as much as making one machine calculate quickly. The exact technologies changed, but the underlying question remained familiar: how should a computing service be organised so people can use it?

This wider career helps explain why his legacy is discussed by computer historians, engineers and Cambridge institutions rather than only by collectors of early machines. It connects hardware design, programming methods and shared infrastructure. Readers interested in the local setting can use the location guide for the present-day park and transport context; the computing milestones belong to Wilkes's historical biography.

Recognition and legacy

The Association for Computing Machinery records Wilkes as the recipient of its 1967 A. M. Turing Award. The award is a marker of professional recognition, but it is not a substitute for understanding the work. EDSAC made stored-program computing useful to researchers; his programming and processor ideas addressed the challenges that usefulness created; later network work explored how computers could serve people together rather than in isolation.

Cambridge's Department of Computer Science and Technology remembers Wilkes as a former head of the laboratory and a pioneer of British computing. Its records place his death in 2010. The institution's account is valuable because it also preserves the team setting. EDSAC was the product of a laboratory, not one person's solitary invention. Describing Wilkes as its leader and a central designer leaves room for the engineers, programmers and researchers who made the service work.

That distinction matters when visiting a place carrying a person's name. A building name can prompt a question, but it cannot tell the complete story by itself. The most faithful way to answer that question is to return to the university's records, separate verified milestones from later interpretation and keep the contributions of the wider team in view.

The building and the person

St John's Innovation Park says the Maurice Wilkes Building was completed in June 2018 and stands at the gateway to the park. The park is owned by St John's College, Cambridge. Those are facts about the building and its setting. They do not establish who currently operates this website, who occupies any particular suite or whether space is available now.

Nor does a shared name prove a specific official naming rationale. The available park history and University biography support the connection between a Cambridge computing pioneer and a later building bearing his name; they do not supply a detailed record of the naming decision. It is reasonable to treat the name as an invitation to learn about Wilkes, while keeping that inference separate from a documented decision.

For practical information about the completed site, start with the building overview and the location page. For dated reports on the development, use the blog archive and read each account in its original period. If you need current visitor or occupancy information, the contact guidance explains where to check it without presenting historical claims as a current offer.

Wilkes's story makes the name easier to remember. In Cambridge, his work helped turn the emerging idea of electronic computing into a shared research tool. The building belongs to a later chapter of the city's technology landscape. Keeping those chapters distinct makes both more interesting—and more accurate.