The majority of computer users are unaware of FOCS. They won’t be aware that every fall, a few hundred theoretical computer scientists congregate in a hotel ballroom in Berkeley or a university auditorium in Chicago to debate complexity classes and prove things that won’t be relevant for business for another twenty years, if at all. However, many of the things we take for granted today, such as the algorithms that shape search results and the cryptography that powers banking apps, can be traced back, either directly or indirectly, to papers that were presented at this conference.
The FOCS Steering Committee sits silently above it all. This is the type of organization that doesn’t send out press releases. It lacks a slick, happy-looking website. Every year, it makes decisions about the conference’s organizers, venue, and priorities. You begin to notice something when you look at the lengthy Wikipedia entry that lists program chairs dating back to 1975: the same names appear repeatedly. Yannakakis, Tarjan, Sipser, and Hopcroft. These are not your typical scholars. Every theory student has these authors’ textbooks on their shelf.
| Detail | Information |
|---|---|
| Conference Name | IEEE Annual Symposium on Foundations of Computer Science |
| Common Acronym | FOCS |
| Sponsor | IEEE Computer Society |
| Founded | 1960 (as Symposium on Switching Circuit Theory) |
| Current Name Since | 1975 |
| Sister Conference | STOC (ACM) |
| Governance | Steering Committee + rotating Program Committee Chairs |
| Notable Awards | Knuth Prize, Best Paper, Machtey Award |
| Code of Conduct Oversight | Steering Committee + annual organizers |
| Cover Artwork | “Synapse” by Alvy Ray Smith |
| Test of Time Award | Administered by separate committee under steering oversight |
| Recent Host Cities | Berkeley, Chicago, Denver, and others across North America |
Reading the conference’s history gives the impression that the committee prioritizes continuity over disruption. In 1986, Ashok Chandra presided over the Technical Committee on Mathematical Foundations. By 1989, Christos Papadimitriou was in charge. Outsiders can hardly see the handoffs. It’s possible that FOCS’s unwavering, almost archaic dedication to the long term, while other areas of computer science follow whatever is popular at the time, is what gives it its distinctive character.
The committee’s function goes beyond ceremonial duties. The same sentence can be found on any of the most recent FOCS code of conduct pages from 2019, 2022, or 2023: the steering committee and the year’s organizers are jointly responsible for making the conference inclusive and respectful. That wording is important. It indicates that someone should be paying attention outside of the program. To be honest, it also means that things haven’t always been ideal and that the field has had to consider more carefully who is allowed to participate.
Another silent but powerful piece is the Test of Time Award. In accordance with the steering committee’s recommendations, the award committee evaluates nominations throughout particular target years, honoring papers whose significance didn’t become apparent until ten years later. The award is strangely modest. Being ostentatious does not win you the prize. Eventually, you win because you were correct.
There are criticisms that are worth sharing. The steering committee, like many academic governing bodies, has been accused by some of being slow to update. Concerns regarding acceptance rates, PC member submissions, and decision-making processes are sometimes brought up in discussions on theory blogs. These are not scandals. These are the typical, grinding conflicts that arise when a small community tries to run its affairs in an equitable manner.
When observing FOCS over the years, it’s difficult to ignore how stable the entire organization seems. Alvy Ray Smith’s “Synapse,” which was given to the Simons Institute in 2023, has been the cover art for all time. In 1975, the acronym underwent one change. The locations, which are primarily American, alternate. The committee continues to select chairs, approve locations, and attend meetings. It’s not a glamorous job. Despite its abstraction, theoretical computer science relies more on these unglamorous structures than it typically wants to acknowledge.
