The Minds Behind COBOL – 7 People Redefining Software
COBOL emerged from an unusually collaborative effort to make business programs readable, portable, and less dependent on one manufacturer's machine. Its history spans Grace Hopper's FLOW-MATIC influence, Mary Hawes's call for a common language, Jean Sammet's committee work, and the designers, implementers, and standards advocates who turned that idea into a durable business-computing platform.
TL;DR
COBOL grew out of a 1959 push to create a common business language that could move across manufacturers instead of locking organizations to one machine family. Mary Hawes helped trigger the effort; Grace Hopper’s FLOW-MATIC supplied a powerful precedent for English-like data-processing notation; Jean Sammet and other committee members turned requirements into language statements; Betty Holberton helped edit the emerging specification; Howard Bromberg helped implement and standardize it; Bob Bemer contributed major language ideas and terminology; and William Selden participated in the small Short Range Committee that hammered out the first design.[1][2][6]
Why you should read it anyway
You should read COBOL’s origin story because it is a rare case where portability was a political and economic objective before it became a technical slogan. Government agencies and businesses were buying expensive computers from competing vendors, and programs were expensive assets. A language that could express payroll, inventory, records, and reports in a common form promised to loosen the bond between software and one machine. The astonishing part is that this was attempted by bringing competitors into the same process and producing a specification quickly enough to matter.[1][5]
Imagine where COBOL would be without them
Without these people, business computing would still have developed, but it might have remained fragmented among vendor-specific languages for longer. That would have increased migration costs and slowed the creation of a shared workforce of business programmers. COBOL’s longevity is often mocked, yet that longevity is evidence that the committee solved a durable problem: businesses needed stable ways to describe records, files, reports, and decimal data independently of a particular computer generation.[5][6]
Time Estimate of how many years we would be hindered without them for human progress
Counterfactual estimate: 3–8 years. This is an editorial estimate rather than a historical measurement. Commercial languages such as FLOW-MATIC and COMTRAN already existed, so a business language would have appeared. The larger delay would likely have been in agreement: getting manufacturers, government users, and standards bodies to converge on a portable common language with enough momentum to become an industry norm.
The 7 people behind COBOL
1. Grace Hopper
Why they matter: Hopper’s importance to COBOL is best described as foundational influence and advocacy rather than solitary invention. Her earlier FLOW-MATIC work demonstrated that business data processing could be expressed with English-like statements, and she strongly promoted machine-independent languages. The COBOL effort drew from FLOW-MATIC alongside other systems. Hopper therefore supplied a working precedent and a persuasive vision that shaped what the committee believed a business language could be.[1][5]
2. Jean Sammet
Why they matter: Sammet was one of the central technical participants in the 1959–60 language-design process. The IEEE Computer Society records her membership in the CODASYL COBOL committee and leadership of the Short Range Subcommittee, which was responsible for developing the language statements. She later became a leading historian and classifier of programming languages, but here her importance is immediate: she helped convert broad requirements for business portability into a coherent language design.[2][6]
3. Mary Hawes
Why they matter: Hawes helped create the conditions in which COBOL could happen. Smithsonian history credits her with recognizing the need for a common business language and pressing for a meeting that brought government and industry together in 1959. Her contribution was catalytic: rather than designing one vendor’s next product, she framed language incompatibility itself as a problem that competitors had to solve collectively.[1]
4. Betty Holberton
Why they matter: Holberton brought the perspective of an experienced programmer and language designer to the COBOL process. Historical papers place her on the editing committee that turned the Short Range Committee’s work into the COBOL 60 report, helping resolve wording and presentation in a specification that would be implemented by multiple manufacturers. Her role highlights an underappreciated part of standards work: precise editing is technical infrastructure when independent teams must interpret the same document.[7][5]
5. Howard Bromberg
Why they matter: Bromberg represented RCA in the COBOL effort and then helped prove the specification could become working software. IEEE history credits him with participation in the committee, leadership of RCA’s first COBOL compiler work, and later chairmanship in standards activities. He stands for the implementation-and-standardization side of COBOL: a language becomes portable only when competing systems can implement the same semantics reliably.[3]
6. Bob Bemer
Why they matter: Bemer brought IBM’s commercial-language experience into the process. IEEE history credits him with Commercial Translator, with major COBOL features such as the IDENTIFICATION and ENVIRONMENT divisions and the PICTURE clause, and with coining the names COBOL and CODASYL. His work made the language’s business orientation concrete: data description, environment description, and formatted records became first-class concerns rather than afterthoughts.[4]
7. William Selden
Why they matter: Selden was one of the small group identified in Charles Babbage Institute historical material as the committee that developed the initial COBOL design. His name is less famous than Hopper’s or Sammet’s, which is exactly why he belongs in a people-first account. Standards are often built by working groups whose members perform the detailed synthesis between competing proposals, and Selden represents that collaborative design labor.[6][5]
How they each differ from one another
Hopper supplied an influential predecessor and public vision; Hawes created the institutional opening; Sammet helped lead language design; Holberton helped make the report precise enough to implement; Bromberg linked specification to compiler construction and standards; Bemer contributed concrete language mechanisms and terminology; Selden was part of the small committee doing the synthesis. COBOL was therefore simultaneously an idea, a negotiation, a specification, and an implementation project.[1][2][6]
Final Take
COBOL’s most important invention may have been social as much as syntactic: competitors agreed that business software should outlive individual machines. The seven people here did not all contribute in the same way, and none should be turned into a single mythical ‘inventor.’ Together they show how a standard language actually emerges—from prior systems, a clearly stated economic need, intense committee work, precise editing, working compilers, and continued standardization. That combination helped make software an organizational asset rather than disposable code tied permanently to one computer.[1][5]
Works Cited
- 01Smithsonian American Women's History Museum — COBOL womenshistory.si.edu
- 02IEEE Computer Society — Jean E. Sammet history.computer.org
- 03IEEE Computer Society — Howard Bromberg history.computer.org
- 04IEEE Computer Society — Robert W. Bemer computer.org
- 05CODASYL — COBOL Report, April 1960 bitsavers.trailing-edge.com
- 06
- 07Computer History Museum — COBOL Historical Papers Collection archive.computerhistory.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead