technologybriefs
Saved
Software · Systems

COBOL

1959

COBOL didn’t democratise programming—it bureaucratized it.

Worth your time?3.5/5Yes.Study the whole thing.What works, what does not, who it is for ↓
9:26in productionCh. 1 · A language built for procurement/ 9:26 · ceiling 15 min
4 chapters · 9:26Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 9:26 planned

Read the brief

COBOL is a compiled, English-like programming language designed in 1959 by CODASYL for business data processing. Its first specification, COBOL 60, was approved on 8 January 1960 and published by the government printing office. A demonstration in December 1960 confirmed cross-platform compatibility between RCA and Univac systems. Its core objectives were portability, ease of migration, and accessibility to inexperienced programmers. Syntax was deliberately prose-like (e.g., MOVE x TO y) and self-documenting, and its structure enforced a rigid four-division hierarchy. It was standardized in 1968 and revised multiple times thereafter.

Chapters & takeaways4
  1. 1:05
    A language built for procurement

    COBOL was a Department of Defense–led response to vendor lock-in, not a leap in language design.

  2. 2:35
    Portability, narrowly defined

    Cross-platform compatibility was proven in December 1960—but only between two specific mainframe vendors.

  3. 3:55
    Readability at the cost of expressiveness

    Its prose syntax and rigid divisions made code readable—but also inflexible and verbose.

  4. 5:12
    Accessible, then abandoned

    It succeeded for inexperienced programmers—but failed to evolve with them.

Worth your time?

Yes. Study the whole thing.

3.5/ 5
What works
  • cross-platform compatibility on 1960s mainframes
  • readability for non-specialist staff
  • enforced separation of data, environment, and logic
What does not
  • scale to modern distributed systems
  • support dynamic memory allocation
  • support recursion
  • support modular abstraction
Study it if
  • legacy mainframe maintainers
  • government payroll systems
  • banking transaction processors
Skip it if
  • cloud-native developers
  • AI infrastructure teams
  • mobile application engineers
The written brief1 min read

What it is and the problem it solves

COBOL is a compiled programming language designed for business data processing. It solves the problem of writing portable, readable, and maintainable code for financial and administrative systems on early mainframes.

How it works

COBOL is a compiled, English-like programming language. It uses prose syntax such as MOVE x TO y. Code is split into four rigid divisions: identification, environment, data, and procedure. Each division contains sections, paragraphs, and sentences in fixed hierarchy.

What works

COBOL delivers on portability across 1960s mainframes: one program ran on both RCA and Remington-Rand Univac machines. Its syntax is self-documenting and accessible to non-specialists. Its four-division structure enforces separation of concerns—data definition, system configuration, program logic, and metadata.

What does not

COBOL does not scale to modern distributed systems. It does not support dynamic memory allocation, recursion, or modular abstraction. Its verbosity increases maintenance overhead without improving correctness. Its portability claim applied only to mainframe-era hardware with compatible COBOL compilers—not to later architectures or ecosystems.

What it changes

COBOL changed how business logic was written, deployed, and maintained across government and banking institutions. It entrenched procedural, file-centric data processing for decades. It delayed adoption of higher-level abstractions in enterprise computing by making incremental upgrades easier than redesigns.

Is it worth your time

Yes—if you maintain legacy business systems built on COBOL. No—if you are building new applications. Its value is operational, not architectural. It persists because rewriting is costlier than sustaining.

Same field · Software4 of 114
11:03
Lisp (programming language)John McCarthy · 1958Lisp is the first language to treat code as data—and the first to prove that a small set of primitives plus eval suffices for universal computation. Its cost is runtime overhead; its payoff is programmable programmability.
11:20
FortranJohn Backus · 1957Fortran is the first high-level programming language to achieve broad use. It succeeded not by abstracting away hardware, but by proving abstraction could coexist with assembly-level performance — specifically for numeric computation on the IBM 704. Its compiler introduced the basic block and Monte Carlo–driven memory layout, establishing techniques that remain standard. It made computing accessible to scientists — but only those doing number-crunching, and only on IBM hardware.
8:56
Jenkins (software)2011Jenkins is an open-source automation server that helps automate building, testing, and deploying software, enabling continuous integration and delivery. It originated as Hudson and was renamed in 2011 following a naming dispute with Oracle. The rename followed a community vote on January 29, 2011. Jenkins runs as a server-based system, either in servlet containers like Apache Tomcat or as a stand-alone web application using Eclipse Jetty. It supports multiple version control tools and build systems. The Pipeline plugin, which enables pipeline-as-code using Groovy, was not enabled by default until version 2 in 2016. Jenkins replaced Hudson in Eclipse in 2017.
9:41
BASICJohn Kemeny and Thomas Kurtz · 1964BASIC is a pedagogical tool, not a general-purpose language. It succeeded by narrowing scope — to Dartmouth, to undergraduates, to time-shared interaction, to FORTRAN II’s grammar stripped of complexity. Its value lies in what it excluded.
Up next in Technology

Color photography

1855 · 9:50

Colour photography began not with a picture, but with a constraint: three lights, three cones, and zero images.

9:50