Elle voulait coder avec des mots. Le monde a suivi.

Elle voulait coder avec des mots. Le monde a suivi.

She wanted to code with words. The world followed.

Title history
  • Elle voulait coder avec des mots. Le monde a suivi. — observed on 20261110-0245 UTC (YouTube)

by CodingBiceps · View the channel on PSI

Humanities, Social Sciences & Thought Computing & Cybersecurity UBDigital and Information technology: general topicsUBBHistory of Computing, digital and information technologies
🎙 CodingBiceps 👥 8K 📅 October 13, 2026 ⏱ 13 min 👁 47K 📄 documentary 🧭 2026-11-10
Available in: English (current) Français

Keywords

COBOLGrace HopperMary HawesCODASYLlegacy systems

Summary

This video tells the story of COBOL, a programming language created in 1959 as a temporary solution but still powering critical banking and government systems today. The narrative begins by explaining the chaotic state of computing in the late 1950s, where each manufacturer had its own language, making code incompatible. The U.S. Department of Defense, as the largest buyer, pushed for a common language. Contrary to popular belief, Grace Hopper did not invent COBOL; she inspired it through her FLOW-MATIC language. The initiative actually came from Mary Hawes, an analyst at Burroughs, who proposed a common business language. A series of meetings, including a pivotal one at the Pentagon in May 1959, led to the formation of CODASYL. Over the summer, a short-term committee drafted the spec, and a group of six people, including Jean Sammet and Gertrude Tierney, finalized it in a two-week sprint. The resulting COBOL 60 was tested successfully across two different machines in 1960. The video explains COBOL’s readability, its precise decimal arithmetic on which banks rely, and its longevity. It also addresses criticism from Dijkstra and the Y2K bug, as well as why replacing COBOL is so difficult. The video concludes with modern relevance, noting that 43% of U.S. banking systems still run COBOL and that IBM is now using AI to maintain it.

219 words

Critical Evaluation

Value of the Information & Strength of the Argument

The video provides valuable insights into the history of computing, debunking common myths and highlighting the often-overlooked contributions of women like Mary Hawes and Jean Sammet. The argumentation is solid: the narrator supports claims with specific dates, participant names, and statistical references (e.g., 220 billion lines of code, 43% of banking systems). The explanation of why COBOL persists is coherent, emphasizing both technical reasons (exact decimals) and organizational inertia.

Scientific Rigor, Source Quality, Title Accuracy

The video demonstrates strong scientific rigor. It correctly states that Grace Hopper did not invent COBOL and gives credit to Mary Hawes. It refers to well-known events like the CODASYL meetings and the 1960 test. The title appropriately captures the theme of coding with words. While no external sources are cited directly in the description, the video’s reliance on historical records and the creator’s other videos on programming history lend it credibility. The title/content alignment is excellent.

161 words

Title / Content Match

The title accurately reflects the content, which focuses on the visionary idea of programming with words, leading to the creation of COBOL.

Quality & Reliability

9/10

The video is well-researched, accurately corrects the myth about Grace Hopper, and provides detailed historical context with specific dates, names, and statistics.

Key Moments

Markers derived by PSI from the transcript: the creator did not define chapters.

Cited Sources

Contribution & Novelties

The video offers a fresh perspective by emphasizing the role of Mary Hawes, who is often overlooked, and clarifying Grace Hopper’s indirect influence. It also explains COBOL’s persistent relevance in modern banking and the challenges of migration, making it both historically and technically informative.

Pour aller plus loin :

81 words

Radar Profile

The radar profile shows high scores across quality, quantity, and reliability, with slightly lower technical depth, indicating a well-balanced video that is both informative and accessible, suitable for a broad audience interested in computing history.

Reliability 9/10